← ClaudeAtlas

cluster-quality-checkerlisted

Audits cluster posts against the 13 strict PostHog template rules and outputs a pass/fail report with specific corrections. Use this skill after the writer hands off a draft and before the post goes to publish. Trigger on phrases like "QA this post", "quality check the pillar", "audit the listicle", "did the writer follow the rules", "run the checklist on these posts", or any handoff from the writer or orchestrator that asks for verification before publish. This skill does not rewrite content. It produces a structured report that the writer or human editor uses to fix issues. Trigger aggressively on any cluster post entering the QA stage.
rohitabrahamgeorge/seo-content-team · ★ 0 · Data & Documents · score 72
Install: claude install-skill rohitabrahamgeorge/seo-content-team
# Cluster Quality Checker This skill is the auditor that sits between the writer and the publish step. It reads draft posts and grades them against the strict rules codified in the writer skill (`cluster-writer/SKILL.md`). Every claim about the product is checked against `product-context.md`, the filled product context file at the root of the working folder (next to `clusters/`). Output is a structured report listing every violation with the exact line number and a recommended fix. The skill never rewrites content — that's the writer's job on the next pass. ## When to use this skill Trigger when: - The writer skill has just finished a post (the orchestrator should call QA automatically) - A user says "QA this", "audit this", "check this against the rules", "run the checklist" - A post is being prepared for publish and needs a final gate - A revision cycle is happening (re-QA after the writer fixes issues) Required inputs: - One or more `.md` post files at known paths - The writer skill's rule reference (`cluster-writer/SKILL.md`) - The filled product context file (`product-context.md` at the working-folder root, next to `clusters/`) If the writer skill or `product-context.md` aren't accessible, halt and ask the orchestrator to provide them. Do not invent rules from memory. ## What the QA report looks like Output is a single markdown file at `qa-reports/[slug]-qa-report.md` with this structure: ```markdown # QA Report: [post title] **Post:** [slug] **Audited:** [date]