CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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-authored content is reaching publish unaudited, when a QA process burns reviewers out, or when a programmatic SEO set needs sampling discipline. On a voice consistency check, this skill owns checking a draft against an existing voice system at the publish gate; use `brand-voice` when the voice system itself needs defining or documenting.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-executed instruction-only skill: concrete thresholds, an explicit gate sequence with halt/flag/auto-fix decision rules, feedback loops via threshold gating, and a clean one-level-deep reference architecture where every pointer resolves to a real, substantive file. The only deductible issue is redundancy — the keystone thesis and voice-drift guidance each appear multiple times. No dimension falls below 4.

Suggestions

Trim one of the three restatements of the catch-problems-vs-checkbox thesis (intro paragraphs, the dedicated section, or the closing) — the dedicated section carries the full argument, so the intro and closing versions can be single sentences.

Consolidate voice-drift coverage: it appears under both 'Voice consistency check' and 'AI-content audit'; have the AI-audit section cross-reference the voice section instead of restating the drift pattern.

DimensionReasoningScore

Conciseness

The body is dense and specific with no padding of concepts Claude already knows (no 'what is SEO' explanations), and every section carries concrete checks. It falls short of anchor 5 because the catch-problems-vs-checkbox thesis is restated in the intro, its dedicated section, framework consideration #1, and the closing — reinforcement that costs tokens — and voice drift is covered twice (voice section and AI-audit section). Not 3: these are trims, not blocks of unnecessary explanation; the bulk of the body earns its place.

4 / 5

Actionability

Concrete, executable guidance throughout with specific thresholds: "40 to 60 word answer paragraph immediately following each H2 question", "If more than 5% of sampled pages fail the manual review, halt new generation", "3 to 7 for typical 1,500-word piece, 8 to 15 for pillars", "sources older than 3 years for fast-moving topics need refresh". Per the scoring note for instruction-only skills, absence of code is not penalized; the check lists are directly runnable as a QA procedure with named halt conditions. Not 4: there are no missing key details — deferred specifics (sample-size schedule, gate order) are explicitly assigned to named reference files.

5 / 5

Workflow Clarity

The full gate sequence is given inline ("Brief-adherence to fact-accuracy to structure to AI-audit to voice to SEO/AEO to linking to schema" plus "Brief-adherence runs first" rationale), ownership is explicit ("Single QA owner per piece"), and decision rules are classified (halt vs flag vs auto-fix). Feedback loops are present: threshold gating halts generation, fixes the template/data issue, and resumes with documented breaches; escalation fires on repeated patterns. This matches anchor 5 (explicit validation steps, feedback loops, checklists — the 12-consideration framework); not 4 because no checkpoints are missing.

5 / 5

Progressive Disclosure

Each section is a self-contained overview ending in "Detail in [references/...]", all ten referenced files exist in the bundle and are one level deep with substantive content (108–184 lines each), and a consolidated annotated "Reference files" index closes the body. Cross-file ownership of numbers is explicitly delegated ("the sample-size schedule in references/qa-at-scale-patterns.md, which owns the numbers"). Matches anchor 5 (well-signaled, one-level-deep, easy navigation); not 4 because there are no organization gaps.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: it states a concrete capability list, gives an extensive set of natural trigger terms plus situational triggers, and closes with an explicit boundary against the adjacent brand-voice skill. It uses third person throughout and every clause carries retrieval-relevant signal rather than padding. No weaknesses found against any anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "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" — covering every section of the skill with no visible gaps. Anchor 4 ("minor gaps in coverage") is a worse fit because the capability list maps one-to-one onto the body's ten check areas.

5 / 5

Completeness

Explicitly answers both what ("Pre-publish QA framework for content" with the named checks) and when ("Triggers on editorial QA..." and "Also triggers when a content team is shipping sloppy work...") with concrete trigger phrases. This matches the anchor-5 example pattern exactly; not 4 because the 'when' is explicit and multi-branch rather than improvable.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage: "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" plus situational phrasings a user would actually say ("when a QA process burns reviewers out", "when AI-co-authored content is reaching publish unaudited"). Includes synonyms and situational variants, matching the anchor-5 bar; anchor 4 ("a few natural terms missing") understates the coverage.

5 / 5

Distinctiveness Conflict Risk

Clear niche (pre-publish QA gate at the end of the content pipeline) with distinct triggers and an explicit boundary against the nearest neighbor: "use `brand-voice` when the voice system itself needs defining or documenting." Minimal conflict risk; not 4 because the disambiguation is already stated rather than merely implied.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

skills/editorial-qa/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.