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.

96

1.56x
Quality

94%

Does it follow best practices?

Impact

97%

1.56x

Average score across 9 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

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 an excellent skill description that clearly communicates specific capabilities, provides comprehensive trigger guidance, and occupies a distinct niche. It uses third person voice consistently, lists concrete actions, and includes an explicit 'Use this skill whenever...' clause with multiple natural trigger scenarios. The mention of '37 AI anti-patterns' adds a unique differentiator that further reduces conflict risk.

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 actionable capabilities.

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 including blog mentions, transcript conversion, and blog series continuation).

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 when requesting this kind of work.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: developer blog posts specifically from video transcripts/meeting notes, with the unique differentiator of checking against 37 AI anti-patterns. The combination of 'blog' + 'developer' + 'transcript' + 'anti-patterns' makes this unlikely to conflict with general writing or content skills.

3 / 3

Total

12

/

12

Passed

Implementation

85%

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 skill that provides clear, actionable guidance for a complex multi-phase blog writing workflow. Its strengths are excellent workflow clarity with explicit gates and validation steps, strong progressive disclosure through well-organized reference files, and highly specific instructions. The main weakness is moderate verbosity in some sections — particularly the blog anatomy and placeholder numbering examples — where Claude's existing knowledge could be leveraged more.

Suggestions

Tighten the 'Blog Anatomy' section — Claude understands blog structure; focus only on the author-specific constraints (e.g., 'TLDR: bullets not prose, written last placed first') rather than explaining what an opening hook or CTA is.

Condense the placeholder numbering examples from 7 to 3-4, since the independent-numbering rule is the key insight and doesn't need that many examples to convey.

DimensionReasoningScore

Conciseness

The skill is fairly well-written but includes some unnecessary verbosity — e.g., the detailed explanation of placeholder numbering with 7 examples could be tighter, and some sections like 'Blog Anatomy' explain concepts Claude already understands about blog structure. However, most content is domain-specific configuration that Claude wouldn't know.

2 / 3

Actionability

The skill provides highly concrete, executable guidance: specific file paths, exact curl commands, clear placeholder formats with examples, a defined phase-gate workflow, and precise rules (e.g., 're-read persona/voice.md before every writing action'). The instructions are specific enough to follow without ambiguity.

3 / 3

Workflow Clarity

The workflow is clearly sequenced across 5 phases (0-4) with explicit gates for each phase. The anti-pattern check has a defined three-pass procedure with specific ordering constraints. The bootstrap section has a clear decision table. Validation checkpoints are explicit ('Do not skip phases. Do not write prose before Phase 3.').

3 / 3

Progressive Disclosure

Content is well-structured with clear references to external files (persona/voice.md, references/process.md, references/ai-anti-patterns.md, etc.) that are one level deep and clearly signaled. The SKILL.md serves as an overview and orchestrator, delegating detailed content to reference files while providing enough context to understand the workflow.

3 / 3

Total

11

/

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