Marketing
Content Accuracy Editor
Content Accuracy Editor
Start with Website or article archive. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.
- 1/wkEvidence reports
FactoriesStart with your sources
IdleIllustrative runEarlier posts in your CMS list_content
Sources on the web fetch
Draft postIn your voice
Publish to your CMS
upsert_contentPostRelated solutions
See how teams in this category put agents to work.
Integrations
0 integrationsGet started with Content Accuracy Editor
Pick an example, connect your tools, and review the first run.
Set up the Content Accuracy Editor agent template for this project. Follow /SKILL.md for the exact CLI commands.
Goal: Recheck factual claims and references, investigate obsolete sections, and deliver revised copy with source evidence and a history of corrections.
1. Install the CLI if it is not on PATH, check that I am signed in, and select my team and project.
2. List the first-party workflow templates. If `content-accuracy-editor` is listed, instantiate it with `--path.slug content-accuracy-editor` and start the run; otherwise create a project from this template at /new?template=content-accuracy-editor&preset=trial.
3. Share the run id, follow the run until it finishes, and summarize its outputs and changes.
Ask me before spending FTAI or changing anything outside this repository.
Launch from Claude Code, Codex, Cursor, and other agents.