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
bio.mdexample-persona/
Author Bio: Baruch Sadogursky
Bio Schema
[Name] is a Developer Advocate at Tessl, where [current focus, tied to post topic].
Previously, [one-line career context]. [Dry kicker that callbacks to something in the post.]Examples
From the airline loyalty post:
Baruch Sadogursky is a Developer Advocate at Tessl, where he helps developers stop vibecoding and start spec-driven development. Previously, he spent years at JFrog convincing people that artifact repositories matter. He was right about that, too.
From the smart bulb post:
Baruch Sadogursky is a Developer Advocate at Tessl, where he helps developers stop vibecoding and start spec-driven development. Previously, he spent years at JFrog convincing people that artifact repositories matter. He was right about that, too.
Kicker Notes
The kicker "He was right about that, too" does double duty — it's self-deprecating (implying nobody believed him) and quietly confident (he was right). The "where he helps" clause can shift per post to match the topic. The kicker MUST change when it can land better with a post-specific callback. Propose a kicker and confirm with the author.