editorial-qa
Pre-publish QA framework for content. Brief adherence, voice consistency, fact accuracy, structure and clarity, AI-content audit, SEO and AEO compliance, internal linking and schema validation, QA at scale via sampling, the QA workflow, and the discipline that distinguishes catch-problems QA from checkbox QA. Triggers on editorial QA, content review, pre-publish review, content audit, content QA process, AI-content audit, hallucination check, content sampling, programmatic QA, voice consistency check, brief adherence check. Also triggers when a content team is shipping sloppy work, when AI-co-
Profile →npx skills add rampstackco/claude-skills --skill editorial-qa --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Pre-publish QA framework that plugs in at the END of every content skill's output to ensure quality before publish. It addresses brief adherence, voice consistency, fact accuracy, structure and clarity, AI-content audit, SEO and AEO compliance, internal linking and schema validation, and QA at scale via sampling. It distinguishes catch-problems QA from checkbox QA and defines a gate to move drafts to publishable status. The audience includes editorial leads, content directors, in-house QA, and content ops managers; the voice targets editors with concrete, opinionated guidance.
How it works
The skill prescribes a sequencing for QA checks: Brief-adherence, then fact-accuracy, then structure, then AI-content audit, then voice, then SEO/AEO, then internal linking, then schema. It describes two QA modes (catch-problems QA vs checkbox QA) and emphasizes sampling over full audits for scalability. It introduces a six-skill content suite and positions this skill as the gate that enforces quality, with escalation rules and threshold gating for scale applications. It also details the types of checks within each area (e.g., brief-adherence specifics, internal linking rules, schema validation). The checks are framed as concrete gates that can halt or require edits, or auto-fix certain mechanical aspects.
When to use it
Use when building a content QA process from scratch, auditing an existing QA process that ships sloppy work or burns out the team, designing QA gates for an AI-assisted workflow, or building sampling discipline for programmatic SEO sets.
What it can touch
Not specified in this excerpt. The skill references interactions with pre-publish outputs and QA workflows, but no explicit tool commands or touched artifacts are enumerated here.
Caveats
The material outlines a philosophy and workflow for QA at publish-time, with emphasis on avoiding process theater and ensuring checks actually catch real problems. It notes that full-audit QA is infeasible at scale and promotes sampling discipline and threshold gating. No licensing or risk notes beyond the general scope of QA practices are provided in this excerpt.
# Editorial QA A senior editor's playbook for pre-publish content QA. The discipline that catches problems BEFORE content ships, not after. Most content QA is broken in one of two directions. The thin version is "did I read it once and is the spelling OK," which catches typos but misses brief drift, voice inconsistency, hallucinated facts, AI tells, and structural problems that reach readers as "t
What does the editorial-qa skill do?
Pre-publish QA framework for content. Brief adherence, voice consistency, fact accuracy, structure and clarity, AI-content audit, SEO and AEO compliance, internal linking and schema validation, QA at scale via sampling, the QA workflow, and the discipline that distinguishes catch-problems QA from checkbox QA. Triggers on editorial QA, content review, pre-publish review, content audit, content QA process, AI-content audit, hallucination check, content sampling, programmatic QA, voice consistency check, brief adherence check. Also triggers when a content team is shipping sloppy work, when AI-co-
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill editorial-qa --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.