---
name: blog-writer
description: "Write a complete blog post in a casual, conversational, human tone, like a smart friend explaining something clearly and engagingly. Use this skill whenever the user asks to write a blog post, article, or tutorial. Always output a downloadable Markdown file."
---
 
# Blog Writer Skill
 
Write engaging, human-sounding blog posts in the voice of a **smart friend explaining something**, not a textbook, not a corporate blog, not a generic AI article. Think: clear, warm, a little witty, no fluff.
 
## Voice & Tone Rules
 
- **Casual but not sloppy.** Use contractions, short sentences, conversational transitions ("Here's the thing...", "So what does that actually mean?", "Let's be real").
- **No AI clichés.** Never use: "In today's fast-paced world", "It's important to note", "In conclusion", "Dive deep", "Leverage", "Utilize", or hollow openers. Start with something that grabs.
- **Talk to the reader directly.** Use "you" and "i". Make them feel like you're having a conversation, not writing at them.
- **Explain like the reader is smart but new to this topic.** No over-explaining basic concepts.
- **Be concrete.** Use examples, creative analogies, short scenarios.
- **Allow personality.** Light humor, honest admissions ("I'll be upfront, this part is a bit dumb"), rhetorical questions, all fair game.
## Inputs
 
Gather these from the user's message (some may be optional):
 
| Field | Required | Notes |
|---|---|---|
| Topic | ✅ | The subject of the post |
| Target audience | Optional | Default: Mostly non-technical readers |
| Word count / length | Optional | Default: ask or infer from complexity |
| Key points to cover | Optional | If provided, make sure to hit them all |
 
If critical info is missing (e.g. no topic given), ask before writing. For optional fields, use your best judgment.
 
## Structure
 
Adapt structure to the post type, but a solid default for how-to / explainer blogs:
 
1. **Hook** — A question, bold claim, relatable scenario, or surprising fact. 
2. **The Setup** — What problem does this solve? Why does it matter? Keep it tight (1 short paragraph).
3. **The Meat** — Main content. For tutorials: numbered steps with context. For explainers: logical flow with subheadings. Use `##` and `###` for sections.
4. **The Gotchas / Tips** — One section for caveats, common mistakes, or pro tips. Readers love this.
5. **Wrap-up** — Not a summary. A short punchy closing thought, encouragement, or forward-looking statement. 
## Markdown Formatting
 
- Use `##` for main sections, `###` for sub-sections
- Use bullet lists for non-sequential items, numbered lists for steps
- Use **bold** to highlight key terms or important callouts (sparingly)
- Use `code blocks` for any code, commands, file paths, or technical strings
- Use blockquotes (`>`) for tips, warnings, or highlighted insights
- Keep paragraphs short — 2–4 sentences max
## Output Instructions
 
1. Write the complete blog post
2. Save it as a `.md` file in `/mnt/user-data/outputs/` with a slug-style filename based on the title (e.g. `how-to-write-better-hooks.md`)
3. Use `present_files` to deliver it to the user
4. After presenting, add a **one-line summary** of any assumptions made (length, audience, etc.) and offer to revise
## Quality Check (run mentally before saving)
 
- [ ] Does the opening sentence make you want to keep reading?
- [ ] Does it sound like a human wrote it?
- [ ] Are there any hollow filler phrases?
- [ ] Are the examples concrete and relatable?
- [ ] Is the length appropriate for the topic's complexity?