blog-writer_skill

Overview

This skill transforms scattered notes, code snippets, and rough ideas into polished technical blog posts tailored for developer audiences. It focuses on narrative-driven, first-person writing that shows the journey, practical details, and reproducible code. Use it only for blog-style articles, not for formal documentation, specs, or talks.

How this skill works

It ingests raw brain dumps—notes, commands, code, and conclusions—without requiring prior organization, then identifies the best post type (tutorial, showcase, opinion, TIL, or comparison). The skill applies a developer-focused voice guide and a story framework to surface conflict, learning, and takeaways. Finally it generates a structured draft with a strong opening hook, practical body containing runnable code, and a concise, actionable ending, plus basic SEO suggestions.

When to use it

• You have scattered ideas, terminal commands, or half-written notes for a blog post.
• You want a narrative-focused technical article that shows how you solved a problem.
• You need a draft that includes runnable code examples and honest post-mortems.
• You want a quick conversion of a brain dump into a publishable outline or first draft.
• You need SEO-aware blog content (title, slug, meta description) for a technical audience.

Best practices

• Provide raw inputs: logs, commands, snippets, and short notes—no need to pre-organize.
• Specify desired post type (tutorial, showcase, opinion, TIL, comparison) if you have one.
• Point out any must-cover details (libraries, versions, constraints, audience level).
• Ask for draft iterations: outline → full draft → SEO polish for best results.
• Keep expectations clear: this produces a blog draft, not formal docs or slides.

Example use cases

• Turn a weekend hack’s notes and terminal history into a project showcase post with setup and lessons learned.
• Convert a troubleshooting session into a tutorial with step-by-step repro and fixes.
• Draft an opinion piece from a set of bullet points and references arguing for a tooling choice.
• Produce a short TIL entry from a single insight and minimal context.
• Create a comparison post scaffold when you list pros/cons and a few benchmark notes.