agentleFS
getedgehqgetedgehq/skills/handley-everybody-writes/SKILL.md

handley-everybody-writes

Skill5 starsChanged 12 days agoApache-2.0View on GitHub

Draft and revise reader-centered marketing writing using Ann Handley's public method. Use for emails, articles, landing pages, brand stories, and microcopy that need a clear purpose, useful evidence, and a distinctive voice.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Assemble support: Use the evidence rules to match claims to facts, examples, and authorized customer material.

    line 26
  2. Distinctive:

    Choose the structure: Follow the structure and story rules to arrange material around the reader's question.

    line 28
  3. Distinctive:

    Draft toward one person: Use the drafting rules to write through the outline without premature polishing.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Everybody Writes in Practice

Based on Ann Handley's public method. Not affiliated with or endorsed by Ann Handley.

When to use

Use this skill when turning a brief, notes, or an existing draft into marketing writing that helps a particular reader understand something or make a decision. It supports emails, articles, landing pages, customer stories, and smaller surfaces such as FAQs and subscription confirmations. Small surfaces deserve the same recognizable voice as prominent campaigns. [S1] [S4]

The deliverable is the requested copy, with a title or subject line when appropriate, a useful next action, and concise review notes for unresolved evidence or permissions. Preserve the user's format, length, audience, and voice constraints. Do not turn every assignment into an article or personal story. The method is a revision framework, not a requirement to reproduce Handley's prose. [S2] [S6]

Use the public method to guide judgment rather than claiming access to the book. Read the relevant sections of the method as each decision arises; consult the examples when the difference between fluent copy and useful copy is unclear. Source citations support these instructions, not an obligation to put method citations into customer-facing writing.

Procedure

  1. Frame the assignment. Record the business purpose, delivery surface, reader's situation, and desired decision in the output template. If revising, keep the author's central thought and distinctive observations available before changing sentences. Ask only for missing information that materially changes the result. [S1] [S7]
  2. Protect the human contribution. Identify supplied experience, opinion, and evidence. Follow the authorship rules: work from those inputs, distinguish proposed language from real experience, and flag missing personal details. Handley's caution about AI first drafts should remain visible rather than being recast as an endorsement of automated authorship. [S7]
  3. Find the reader consequence. Apply the reframing test until the benefit is concrete and relevant. Record one guiding sentence. Stop before the chain becomes circular or speculative; a persuasive consequence must still fit the available facts. [S1] [S3]
  4. Assemble support. Use the evidence rules to match claims to facts, examples, and authorized customer material. Narrow unsupported promises. Keep evidence gaps in working notes so they cannot accidentally become assertions in the final copy. [S1] [S5]
  5. Choose the structure. Follow the structure and story rules to arrange material around the reader's question. Use explanation, instructions, or a case story as needed. For narrative work, balance what it reveals about the writer, reader, and idea. [S1] [S6]
  6. Draft toward one person. Use the drafting rules to write through the outline without premature polishing. Address the imagined reader directly when appropriate. Explain unfamiliar ideas without condescension; retain specialist vocabulary when it clarifies. [S1] [S2] [S4]
  7. Rewrite for comprehension. Revisit the purpose and reader situation in a separate pass using the revision rules. Move useful answers forward, repair missing connections, and remove self-serving tangents. Review the worked examples if the draft still centers the business. [S1] [S2]
  8. Make voice specific. Apply the voice rules. Follow an existing voice guide or propose three concrete attributes with sentence-level implications. Check pronouns, jargon, and small supporting text. Remove interchangeable marketing language while preserving expressive choices that serve the reader. [S4] [S8]
  9. Revise the headline separately. Compare candidate titles or subject lines against the headline rules. Choose one that accurately promises the benefit the body delivers. For tiny interface copy, use the actual label or message instead of adding an unnecessary title. [S1] [S3]
  10. Edit and inspect the surface. Review mechanics, cadence, paragraphing, subheads, and scanability using the review checklist. Seek another editor when available; label self-review honestly. Fix clarity failures before cosmetic polish and keep enough explanation for understanding. [S1] [S2] [S8]
  11. Close and deliver. Confirm the next action, resolve checklist failures, and use the output template to present finished copy separately from review notes. Name any remaining blockers precisely. Preparing copy does not itself authorize publication or contacting contributors. [S1] [S5]

Files in this skill

  • SKILL.md: Entry point, usage scope, and the agent's writing loop.
  • references/method.md: Detailed principles, decisions, warnings, and agent adaptations.
  • references/sources.md: Fetched public sources and their contributions, indexed by citation.
  • examples/worked-examples.md: Invented before-and-after illustrations with revision notes.
  • templates/output-template.md: Fill-in working brief, copy deliverable, and review notes.
  • checklists/review-checklist.md: Pass/fail review criteria and common repairs.

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.