Write developer blog posts from video transcripts, meeting notes, or rough ideas — extracting narrative, structuring hooks and technical sections, formatting code placeholders, learning the author's voice through interactive onboarding, and checking drafts against 38 AI anti-patterns with three-pass scanning, craft sweep, and rewrite auditing — whenever the user wants to write a blog post, draft a blog, turn a transcript into a blog, work on blog content, or continue a blog series.
—
—
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
This file maps Tessl product topics to their authoritative sources. During Phase 0, identify which topics the post covers and use WebFetch to pull the relevant pages directly. Don't fetch everything, but don't ration either — the context window can handle it. The goal is accurate product claims, not minimal token usage.
The docs are the source of truth for how the product works today. Fetch specific pages by topic — never crawl the whole site.
Use for roadmap status, upcoming features, and product direction. Only fetch when the post discusses planned features, product maturity, or forward-looking statements.