CtrlK
BlogDocsLog inGet started
Tessl Logo

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 37 AI anti-patterns with structural variant detection, three-pass scanning (surface, skeleton, soul check), craft sweep, and rewrite auditing. Enforces sentence/paragraph craft rules, facts-over-assessments principles, and honest limitations. Includes interactive onboarding to learn the author's voice from writing samples. Persona files live at ~/.claude/blog-writer-persona/ by default, with symlink support for custom locations (e.g. Google Drive for backup). Optional global voice saves your voice profile to Claude Code user memory so it applies across all projects. 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.

92

1.51x
Quality

90%

Does it follow best practices?

Impact

94%

1.51x

Average score across 6 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

77%

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

This is a well-crafted, highly actionable skill with excellent workflow clarity and strong phase-gated processes. Its main weakness is moderate verbosity — the Blog Anatomy fallback section and some repeated instructions could be tightened or moved to reference files. The progressive disclosure structure is reasonable but would benefit from the bundle files being available to verify the reference architecture works as described.

Suggestions

Consider moving the 'Blog Anatomy' section entirely to a reference file (e.g., references/blog-anatomy.md) since it's already a fallback that gets overridden by persona/framework.md, reducing the main skill's length.

Trim the 'Anti-Pattern Check Adherence' section — points like 'do not invent patterns not in the file' and the detailed pass descriptions duplicate what should already be in references/process.md, which is read during the workflow.

DimensionReasoningScore

Conciseness

The skill is fairly long (~200 lines) and includes some sections that explain things Claude would already understand (e.g., what blog posts are, general writing advice like 'stories about real problems'). However, most content is specific configuration, workflow rules, and constraints that Claude genuinely needs. The Blog Anatomy section is somewhat verbose for a fallback section, and some instructions are repeated (anti-pattern adherence restates what's in process.md). Could be tightened but isn't egregiously padded.

2 / 3

Actionability

The skill provides highly concrete, executable guidance: specific file paths, exact bash commands (curl for Wikipedia), precise placeholder formatting with independent numbering examples, a clear bootstrap decision table, and specific phase gates. The workflow is prescriptive with copy-paste-ready patterns for placeholders, symlink creation, and file operations.

3 / 3

Workflow Clarity

The workflow is exceptionally well-structured with a clear phase table (0-4), explicit gates for each phase, and strong validation checkpoints. The anti-pattern check has a defined three-pass procedure with explicit ordering constraints ('do not skip passes, do not merge them'). The bootstrap section uses a decision table for state handling. Feedback loops are present (Phase 4 revision cycle, re-run checks after changes, anti-pattern freshness check). The instruction 'Do not skip phases. Do not write prose before Phase 3' provides clear guardrails.

3 / 3

Progressive Disclosure

The skill references multiple external files (persona/voice.md, references/process.md, references/tone-guide.md, references/ai-anti-patterns.md, etc.) with clear navigation signals and reading order. However, no bundle files were provided, making it impossible to verify these references resolve correctly. The Blog Anatomy section is inline content that could arguably live in a reference file (and partially does via persona/framework.md override). The skill itself is somewhat long for an overview document, with the Blog Anatomy and Screenshot Handling sections being substantial inline content rather than references.

2 / 3

Total

10

/

12

Passed

Description

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 covering multiple user phrasings, explicit 'Use this skill whenever...' guidance, and a distinctive niche that combines developer blogging with transcript processing and AI anti-pattern checking. The description is well-structured and informative without being unnecessarily verbose.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: extracting narrative from source material, structuring content with hooks and technical sections, formatting code examples with placeholders, and checking drafts against 37 AI anti-patterns. These are detailed and concrete.

3 / 3

Completeness

Clearly answers both 'what' (write developer blog posts from various sources, extract narrative, structure content, format code, check against anti-patterns) and 'when' (explicit 'Use this skill whenever...' clause with multiple trigger scenarios).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms: 'blog post', 'draft a blog', 'transcript into a blog', 'blog content', 'blog', 'content creation', 'video transcript', 'blog series'. These are terms users would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche: developer blog posts specifically from transcripts/notes, with the unique differentiator of 37 AI anti-pattern checks. The combination of 'blog' + 'developer' + 'transcript' + 'anti-patterns' makes it clearly distinguishable from general writing or content creation skills.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents