agentleFS
Sign inStart free
HybridAIOneHybridAIOne/hybridclaw/skills/write-blog-post/SKILL.md

write-blog-post

Skill159 starsChanged 6 months agoMITView on GitHub

Draft outlines and publish-ready blog posts tailored to audience, sources, and voice.

We split this skill into the rules it gives an agent

13 rules. 0 are common, 13 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 13

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 19
  2. Distinctive:

    Write a clean first draft with a strong opening and scannable sections.

    line 27
  3. Distinctive:

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

    line 32
  4. Distinctive:

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

    line 43
  5. Distinctive:

    Keep paragraphs short and easy to scan.

    line 64
  6. Distinctive:

    Prefer concrete claims, examples, and numbers over generic adjectives.

    line 65
  7. Distinctive:

    If a source is partial or uncertain, say so instead of filling the gap with confident prose.

    line 67
  8. Distinctive:

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

    line 80
  9. Distinctive:

    Use whichever artifact the user asks for:

    line 95
  10. Distinctive:

    Do not turn a narrow topic into a vague general essay.

    line 106
  11. Distinctive:

    Do not pad the post with repeated points.

    line 107
  12. Distinctive:

    Do not overuse hype language when the evidence is thin.

    line 108
  13. Distinctive:

    Do not force SEO phrasing if it makes the prose worse.

    line 109

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free