editorial-agent

Audits published articles against editorial benchmarks and rewrites HTML variants in KV storage.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/techfundoffice/cats-seo-aiagent-staging --skill editorial-agent-techfundoffice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: editorial-agent
Source: https://github.com/techfundoffice/cats-seo-aiagent-staging/tree/main/.claude/skills/editorial-agent
Command: npx skills add https://github.com/techfundoffice/cats-seo-aiagent-staging --skill editorial-agent-techfundoffice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Published SEO articles often fall short of top-tier editorial benchmarks, and manually auditing text, layout, and CTAs against reference sites like NYT Wirecutter is slow and inconsistent. This Skill automates a post-publish editorial loop that audits, reports, and rewrites articles without human intervention. ## Core Features & Use Cases - Autonomous post-publish audit: Fires after every successful publish via ctx.waitUntil, reading article HTML from KV and running a Kimi-based text audit against a per-category reference URL. - Visual screenshot analysis: Drives Composio's BROWSER_TOOL to load, scroll, and screenshot the live page, then audits layout, density, and CTA issues from the screenshots. - A/B-safe rewrite and republish: Writes an improved HTML variant to a -b KV key (preserving affiliate links and product-pick blocks) so a split-tester can compare variants without touching the live article. - Use Case: After the SEO pipeline publishes a new cat litter box roundup, the agent automatically compares it to Wirecutter's benchmark, logs an EditorialReport to KV, and produces a rewritten variant for A/B testing. ## Quick Start Run an editorial audit on the published article at a given KV key by posting to the /api/admin/editorial-review endpoint with the kvKey and an optional reference URL.

Frequently Asked Questions about editorial-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically audit published articles against a benchmark?

Trigger the editorial audit after publish by wiring it into the publish success block with ctx.waitUntil, or call POST /api/admin/editorial-review with a kvKey. The agent reads the KV HTML, audits text and screenshots against a reference URL, and writes an EditorialReport to KV.

How to screenshot a live page for visual editorial review?

Use Composio's BROWSER_TOOL_CREATE_TASK with the article URL to load, scroll, and capture full-page screenshots, then poll BROWSER_TOOL_WATCH_TASK every 5 seconds for up to 3 minutes. The screenshot URLs feed into a visual audit of layout, density, and CTAs.

Does the editorial rewrite overwrite the live article?

No. Since v2.1 the rewrite is written to a variant B KV key (kvKey-b) while the original stays live. A downstream split-tester compares variants on SEO and traffic metrics before swapping the winner into the live slot.

What guardrails prevent bad rewrites from being published?

The rewrite is rejected if it is shorter than 80% of the original length or lacks basic HTML structure tags like article, section, div, p, or headings. On any step failure the original KV value is left untouched.

Can I change the benchmark reference URL per article category?

Yes. Edit the EDITORIAL_REFERENCE_URLS object in src/server.ts to map category slugs to reference URLs. Unmapped categories fall back to the default NYT Wirecutter automatic cat litter box roundup.