agentleFS
Sign inStart free
gongyijie85gongyijie85/dsh-ecc/skills/article-writing/SKILL.md

article-writing

Skill8 starsChanged 3 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

16 rules. 4 are common, 11 are distinctive, and 1 is very specific to this project.

  • 4

    Common

    Most of the 42 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 1

    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 an actual person with a point of view, not an LLM smoothing itself into paste.

    line 10
  2. Distinctive:

    Keep sentences tight unless the source voice is intentionally expansive.

    line 23
  3. Distinctive:

    Use proof instead of adjectives.

    line 24
  4. Common:

    Never invent facts, credibility, or customer evidence.

    line 25
  5. Very specific:

    If the user wants a specific voice, run brand-voice first and reuse its VOICE PROFILE.

    line 29
  6. Distinctive:

    Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.

    line 30
  7. Distinctive:

    If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.

    line 32
  8. Common:

    Delete and rewrite any of these:

    line 36
  9. Distinctive:

    Start sections with proof, artifact, conflict, or example.

    line 49
  10. Distinctive:

    use code, commands, screenshots, or concrete output in major sections

    line 58
  11. Common:

    start with tension, contradiction, or a specific observation

    line 63
  12. Common:

    keep one argument thread per section

    line 64
  13. Distinctive:

    keep the first screen doing real work

    line 69
  14. Distinctive:

    do not front-load diary filler

    line 70
  15. Distinctive:

    use section labels only when they improve scanability

    line 71
  16. Distinctive:

    every section adds something new

    line 79

“Common” is measured: kept by at least 6 in 10 of the 42 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 an actual person with a point of view, not an LLM smoothing itself into paste.

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: artifact, example, output, anecdote, number, screenshot, or code.
  2. Explain after the example, not before.
  3. Keep sentences tight unless the source voice is intentionally expansive.
  4. Use proof instead of adjectives.
  5. Never invent facts, credibility, or customer evidence.

Voice Handling

If the user wants a specific voice, run brand-voice first and reuse its VOICE PROFILE. Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.

If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.

Banned Patterns

Delete and rewrite any of these:

  • "In today's rapidly evolving landscape"
  • "game-changer", "cutting-edge", "revolutionary"
  • "here's why this matters" as a standalone bridge
  • fake vulnerability arcs
  • a closing question added only to juice engagement
  • biography padding that does not move the argument
  • generic AI throat-clearing that delays the point

Writing Process

  1. Clarify the audience and purpose.
  2. Build a hard outline with one job per section.
  3. Start sections with proof, artifact, conflict, or example.
  4. Expand only where the next sentence earns space.
  5. Cut anything that sounds templated, overexplained, or self-congratulatory.

Structure Guidance

Technical Guides

  • open with what the reader gets
  • use code, commands, screenshots, or concrete output in major sections
  • end with actionable takeaways, not a soft recap

Essays / Opinion

  • start with tension, contradiction, or a specific observation
  • keep one argument thread per section
  • make opinions answer to evidence

Newsletters

  • keep the first screen doing real work
  • do not front-load diary filler
  • use section labels only when they improve scanability

Quality Gate

Before delivering:

  • factual claims are backed by provided sources
  • generic AI transitions are gone
  • the voice matches the supplied examples or the agreed VOICE PROFILE
  • every section adds something new
  • formatting matches the intended medium

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.

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