jbaruch/blog-writer
Write developer blog posts from video transcripts, meeting notes, or rough ideas. Extracts narrative from source material, structures content with hooks and technical sections, formats code examples with placeholders, and checks drafts against 18 AI anti-patterns. Includes interactive onboarding to learn the author's voice from writing samples. Use this skill whenever the user wants to write a blog post, draft a blog, turn a transcript into a blog, work on blog content, or mentions "blog" in the context of content creation. Also trigger when the user provides a video transcript and wants written content derived from it, or when continuing work on a blog series.
Overall
score
100%
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that excels across all dimensions. It provides specific concrete actions, comprehensive trigger terms that users would naturally say, explicit 'Use when' guidance with multiple scenarios, and a clear niche that distinguishes it from general content writing skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Extracts narrative from source material, structures content with hooks and technical sections, formats code examples with placeholders, and checks drafts against 18 AI anti-patterns.' | 3 / 3 |
Completeness | Clearly answers both what (write blog posts, extract narrative, structure content, format code, check against anti-patterns) AND when with explicit 'Use this skill whenever...' clause listing multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'blog post', 'draft a blog', 'transcript into a blog', 'blog content', 'blog', 'video transcript', 'blog series' - these are all phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on developer blog posts from transcripts/notes with distinct triggers like 'blog', 'transcript into a blog', and the specific '18 AI anti-patterns' check makes it highly distinguishable from general writing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates excellent structure, actionability, and progressive disclosure. It provides a complete workflow with clear phases and gates, concrete examples for placeholders and formatting, and appropriately delegates detailed content to reference files. The content respects Claude's intelligence while providing the specific, non-obvious guidance needed for this complex creative task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence throughout. No unnecessary explanations of what blogs are or how writing works—it jumps straight into actionable structure and process. | 3 / 3 |
Actionability | Highly concrete with specific file paths to read, a clear phase table with gates, exact placeholder syntax with examples, and a detailed blog anatomy breakdown. The screenshot/code handling section provides copy-paste-ready placeholder formats. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit phases (0-4), clear gates for each phase, and explicit validation points ('Do not skip phases. Do not write prose before Phase 3.'). The persona check at the start provides a clear decision tree. | 3 / 3 |
Progressive Disclosure | Well-structured with clear references to external files (persona/voice.md, references/tone-guide.md, etc.) that are one level deep. The main skill provides an overview while pointing to detailed materials for specifics like anti-patterns and process details. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Install with Tessl CLI
npx tessl i jbaruch/blog-writerReviewed
Table of Contents