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 22 AI anti-patterns with structural variant detection, two-pass scanning, and rewrite auditing. Auto-updates anti-pattern list from Wikipedia before each session. 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.

94

Does it follow best practices?

Validation for skill structure

Overview
Skills
Evals
Files

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.

DimensionReasoningScore

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 22 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 '22 AI anti-patterns' check makes it highly distinguishable from general writing 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-structured skill with excellent workflow clarity and progressive disclosure. The actionability is strong with specific placeholder formats and clear phase gates. The main weakness is some verbosity in explaining writing concepts (blog anatomy, what makes a good hook) that Claude already understands, though this doesn't severely impact usability.

Suggestions

Trim the 'Quick Reference: Blog Anatomy' section - Claude understands writing structure; focus on author-specific preferences rather than explaining what a TLDR or opening hook is

Consider moving the detailed blog anatomy guidance to a reference file, keeping only the structural outline in the main skill

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some verbose explanations (e.g., the detailed blog anatomy section explaining what a TLDR is, what an opening hook should be). Some sections like 'Quick Reference: Blog Anatomy' explain writing concepts Claude already understands.

2 / 3

Actionability

Provides concrete, specific guidance throughout: exact placeholder formats with numbering rules, specific file paths to check, clear phase gates, and detailed examples of what to do (e.g., the screenshot/code placeholder syntax with correct vs incorrect examples).

3 / 3

Workflow Clarity

Excellent multi-step workflow with clear phases, explicit gates between each phase, and validation checkpoints (anti-pattern check, accuracy check, tightening checks). The 'Do not skip phases. Do not write prose before Phase 3' instruction provides clear guardrails.

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 skill serves as an overview pointing to detailed materials with clear navigation and explicit reading order.

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.

Install with Tessl CLI

npx tessl i jbaruch/blog-writer@0.6.0

Reviewed

Table of Contents