agentleFS
Sign inStart free
ysyecustysyecust/everything-claude-code/.cursor/skills/article-writing/SKILL.md

article-writing

Skill44 starsChanged 5 months agoMITView on GitHub

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

We split this skill into the rules it gives an agent

19 rules. 4 are common, 15 are distinctive, and 0 are very specific to this project.

  • 4

    Common

    Most of the 20 edited versions we read keep these.

  • 15

    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:

    Write long-form content that sounds like a real person or brand, not generic AI output.

    line 9
  2. Distinctive:

    Prefer short, direct sentences over padded ones.

    line 22
  3. Distinctive:

    Use specific numbers when available and sourced.

    line 23
  4. Common:

    Never invent biographical facts, company metrics, or customer evidence.

    line 24
  5. Distinctive:

    If the user wants a specific voice, collect one or more of:

    line 28
  6. Distinctive:

    If no voice references are given, default to a direct, operator-style voice: concrete, practical, and low on hype.

    line 42
  7. Common:

    Delete and rewrite any of these:

    line 46
  8. Distinctive:

    Start each section with evidence, example, or scene.

    line 57
  9. Distinctive:

    Remove anything that sounds templated or self-congratulatory.

    line 59
  10. Distinctive:

    use code or terminal examples in every major section

    line 65
  11. Common:

    start with tension, contradiction, or a sharp observation

    line 69
  12. Common:

    keep one argument thread per section

    line 70
  13. Distinctive:

    use examples that earn the opinion

    line 71
  14. Distinctive:

    keep the first screen strong

    line 74
  15. Distinctive:

    use clear section labels and easy skim structure

    line 76
  16. Distinctive:

    verify factual claims against provided sources

    line 81
  17. Distinctive:

    remove filler and corporate language

    line 82
  18. Distinctive:

    ensure every section adds new information

    line 84
  19. Distinctive:

    check formatting for the intended platform

    line 85

“Common” is measured: kept by at least 6 in 10 of the 20 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

Article Writing

Write long-form content that sounds like a real person or brand, not generic AI output.

When to Activate

  • drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues
  • turning notes, transcripts, or research into polished articles
  • matching an existing founder, operator, or brand voice from examples
  • tightening structure, pacing, and evidence in already-written long-form copy

Core Rules

  1. Lead with the concrete thing: example, output, anecdote, number, screenshot description, or code block.
  2. Explain after the example, not before.
  3. Prefer short, direct sentences over padded ones.
  4. Use specific numbers when available and sourced.
  5. Never invent biographical facts, company metrics, or customer evidence.

Voice Capture Workflow

If the user wants a specific voice, collect one or more of:

  • published articles
  • newsletters
  • X / LinkedIn posts
  • docs or memos
  • a short style guide

Then extract:

  • sentence length and rhythm
  • whether the voice is formal, conversational, or sharp
  • favored rhetorical devices such as parentheses, lists, fragments, or questions
  • tolerance for humor, opinion, and contrarian framing
  • formatting habits such as headers, bullets, code blocks, and pull quotes

If no voice references are given, default to a direct, operator-style voice: concrete, practical, and low on hype.

Banned Patterns

Delete and rewrite any of these:

  • generic openings like "In today's rapidly evolving landscape"
  • filler transitions such as "Moreover" and "Furthermore"
  • hype phrases like "game-changer", "cutting-edge", or "revolutionary"
  • vague claims without evidence
  • biography or credibility claims not backed by provided context

Writing Process

  1. Clarify the audience and purpose.
  2. Build a skeletal outline with one purpose per section.
  3. Start each section with evidence, example, or scene.
  4. Expand only where the next sentence earns its place.
  5. Remove anything that sounds templated or self-congratulatory.

Structure Guidance

Technical Guides

  • open with what the reader gets
  • use code or terminal examples in every major section
  • end with concrete takeaways, not a soft summary

Essays / Opinion Pieces

  • start with tension, contradiction, or a sharp observation
  • keep one argument thread per section
  • use examples that earn the opinion

Newsletters

  • keep the first screen strong
  • mix insight with updates, not diary filler
  • use clear section labels and easy skim structure

Quality Gate

Before delivering:

  • verify factual claims against provided sources
  • remove filler and corporate language
  • confirm the voice matches the supplied examples
  • ensure every section adds new information
  • check formatting for the intended platform

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Does it work?

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

Reviews can't be read right now.

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