write-blog-post

name	write-blog-post
description	Draft outlines and publish-ready blog posts tailored to audience, sources, and voice.
user-invocable	true
metadata	{"hybridclaw":{"category":"publishing","short_description":"Blog post drafting.","tags":["writing","content","blog","communication"],"related_skills":["feature-planning"]}}

Write Blog Post

Use this skill to turn a topic, brief, transcript, notes, or source material into a clear blog post draft.

Default Workflow

1. Confirm the audience, goal, and core takeaway.
2. Identify the strongest angle instead of covering everything.
3. Build a short outline before drafting.
4. Write a clean first draft with a strong opening and scannable sections.
5. Tighten for clarity, evidence, and flow.

What to Ask or Infer

If the user does not specify them, infer the most likely defaults and state them briefly:

• audience
• desired tone
• target length
• primary call to action
• whether the post should be source-grounded or opinion-led

Default Structure

When the user asks for a full post and gives no format, use:

1. Title
2. One-sentence subtitle or hook
3. Introduction
4. 3 to 5 body sections with clear headings
5. Conclusion
6. Optional call to action

For technical posts, prefer:

1. Problem
2. Why it matters
3. Approach
4. Example or walkthrough
5. Tradeoffs or lessons learned
6. Conclusion

Writing Rules

• Lead with the most important point early.
• Keep paragraphs short and easy to scan.
• Prefer concrete claims, examples, and numbers over generic adjectives.
• Preserve the user's source material meaning; do not invent facts.
• If a source is partial or uncertain, say so instead of filling the gap with confident prose.
• Respect the requested tone, but keep the writing direct.

Strong Openings

Good openings usually do one of these:

• name a problem the reader recognizes
• state a surprising insight
• frame a clear before-and-after
• present one strong claim that the post will support

Avoid soft openings that spend multiple paragraphs warming up without saying why the piece matters.

Revision Pass

Before finalizing, check:

• does the title match the actual argument
• does each section earn its place
• are transitions clear
• are weak filler words removable
• is the ending more than a summary line

Common Outputs

Use whichever artifact the user asks for:

• outline only
• rough draft
• publish-ready draft
• headline options
• intro rewrites
• shortened or expanded version

Pitfalls

• Do not turn a narrow topic into a vague general essay.
• Do not pad the post with repeated points.
• Do not overuse hype language when the evidence is thin.
• Do not force SEO phrasing if it makes the prose worse.