blog-post-validator
Validate blog posts for quality, consistency, en-GB spelling, and ScottInk style. Use when reviewing posts before publication.
When & Why to Use This Skill
The Blog Post Validator is a specialized Claude skill designed to automate the editorial review process and ensure content excellence. It performs comprehensive quality checks on blog drafts, enforcing strict adherence to the ScottInk style guide, en-GB spelling conventions, and specific structural requirements. By validating frontmatter, conversational voice, and technical code block accuracy, this tool helps content teams maintain professional publication standards and brand consistency efficiently.
Use Cases
- Pre-publication Editorial Review: Automatically audit draft blog posts for structural integrity (Hook → Problem → Solution) and ensure they meet all 'Must Have' quality benchmarks before going live.
- Brand Voice & Style Enforcement: Maintain a consistent first-person, conversational tone across all contributors while strictly enforcing the ScottInk style guide and avoiding corporate buzzwords.
- Localization and Spelling Standardization: Ensure all content strictly follows British English (en-GB) spelling (e.g., 'colour', 'organisation') to maintain regional linguistic consistency.
- Technical Content Validation: Verify that technical articles include properly formatted code blocks with correct language identifiers and working examples, ensuring a high-quality reader experience.
| name | blog-post-validator |
|---|---|
| description | Validate blog posts for quality, consistency, en-GB spelling, and ScottInk style. Use when reviewing posts before publication. |
| allowed-tools | Read, Grep, Glob |
Blog Post Validator
Perform comprehensive quality checks on blog posts to ensure they meet publication standards.
Quick Start
Validate a post by checking:
- Frontmatter - Has
title,date,published: false - Structure - Hook → Problem → Investigation → Solution → Results
- Voice - First-person, conversational, British English
- Code - Working examples with language identifiers
- Spelling - en-GB (colour, organisation, behaviour)
Critical Checks
Must Have
- ✅ First-person perspective ("I did...", not "One might...")
- ✅ en-GB spelling throughout
- ✅ Code blocks with language identifiers
- ✅ H2 headings only (no H1)
- ✅ Working code examples
Must Not Have
- ❌ Third-person narrative
- ❌ en-US spelling (color, organization)
- ❌ Corporate speak or buzzwords
- ❌ Vague conclusions
Reporting
Provide feedback as:
Overall: [Pass/Needs Changes/Hold]
Issues to Address:
- High priority items
- Medium priority items
Ready to Publish: Yes/No
References
For complete checklists and detailed guidelines: