agentleFS
kynn-devkynn-dev/agent-skills/.agents/skills/human-copywriting/SKILL.md

human-copywriting

Skill1 starsChanged 46 days agoMITView on GitHub

Write or edit clear, human copy while preserving facts, voice, and intent. Use for new copy and focused edits; request sources for factual claims and never fabricate proof. Exclude legal advice, unsupported brand positioning, and copy-free engineering work.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    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:

    Write copy that sounds like a person with a reason to speak, not a template with adjectives.

    line 8
  2. Distinctive:

    Use the source text or brief, objective, audience, channel, language, format/length constraints, desired action, approved facts, material …

    line 18
  3. Distinctive:

    Use this skill for:

    line 30
  4. Distinctive:

    Do not use it for:

    line 37
  5. Distinctive:

    If the request mixes copy with design or product decisions, separate the copy work from those decisions and route each part to the …

    line 44
  6. Distinctive:

    Keep a small claim ledger before drafting:

    line 48
  7. Distinctive:

    Run a claim pass, a voice pass, a clarity pass, and a channel pass.

    line 78
  8. Distinctive:

    Use judgment about how much process to show.

    line 88
  9. Distinctive:

    Prefer plain, concrete language over hype, filler, and stacked adjectives.

    line 92
  10. Distinctive:

    Keep the user's language and regional conventions unless asked to translate or normalize them.

    line 93
  11. Distinctive:

    Avoid fake intimacy, invented urgency, empty superlatives, and claims that only sound true because they are familiar.

    line 94
  12. Distinctive:

    Do not add social proof, scarcity, guarantees, quantified outcomes, or authority signals without evidence.

    line 95
  13. Distinctive:

    Do not use a brand name as evidence of audience, values, market, or promise.

    line 96
  14. Distinctive:

    Ask before changing a material promise, target audience, positioning, or point of view.

    line 97
  15. Distinctive:

    Before delivery, report only checks actually made:

    line 101
  16. Distinctive:

    Never claim that copy is compliant, approved, factual, or on-brand without identifying the evidence and approval boundary.

    line 109

≈ “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

Human copywriting

Write copy that sounds like a person with a reason to speak, not a template with adjectives. Preserve the author's facts and voice, make the requested change visible, and keep every material claim traceable to a supplied source or an explicitly marked placeholder.

Operational contract

Objective

Produce or edit copy that remains specific, natural, and useful while preserving factual boundaries, voice, intent, and required qualifiers. Creative language may improve rhythm and framing, but it must never create evidence, social proof, authority, urgency, or product capabilities that were not supplied.

Expected inputs

Use the source text or brief, objective, audience, channel, language, format/length constraints, desired action, approved facts, material claim sources, tone/voice evidence, non-negotiable phrases, and any legal or regulatory qualifiers the user has supplied. Missing evidence must remain visible as a gap.

Required outputs

Return the requested copy in the requested form, plus only the supporting process that is useful for the task: preserved facts/voice, material source gaps, [SOURCE NEEDED] or unknown markers, significant meaning changes, and optional variants with their trade-offs when appropriate.

Definition of done

The copy is done when every changed material claim is traceable or explicitly provisional, the requested voice and meaning are preserved or intentionally changed, channel/length/format constraints are satisfied, unsupported claims have not been smuggled in through persuasive wording, and any domain approval that did not occur remains NOT_RUN rather than being implied.

Trigger and exclusion boundary

Use this skill for:

  • editing existing headlines, body copy, product text, landing pages, emails, scripts, case studies, microcopy, or UX content;
  • creating new copy from a brief, outline, source material, or approved product facts;
  • adapting an approved message to a channel, audience, language, or length while preserving its meaning;
  • improving clarity, rhythm, specificity, hierarchy, or conversion without inventing evidence.

Do not use it for:

  • legal, medical, regulatory, financial, or safety advice;
  • deciding brand positioning, naming, identity, or visual direction without relevant brand evidence;
  • making up testimonials, metrics, awards, certifications, clients, dates, product capabilities, research findings, or competitive claims;
  • copy-free code, architecture, database, or infrastructure work.

If the request mixes copy with design or product decisions, separate the copy work from those decisions and route each part to the appropriate skill.

Truth and source discipline

Keep a small claim ledger before drafting:

ClassTreatment
CONFIRMEDUse only when supplied by the user or supported by an identified source. Preserve the scope and qualifiers.
VOICE / INTENTPreserve the speaker, audience, promise, emotional register, and words that carry identity unless the user asks to change them.
CREATIVE LANGUAGEMetaphor, rhythm, framing, and non-factual emphasis may be proposed, but must not imply unsupported proof.
SOURCE NEEDEDAsk for the source or use a visible placeholder such as [SOURCE NEEDED].
UNKNOWNDo not fill the gap from convention, memory, a company name, or a plausible assumption.

Material claims include outcomes, numbers, comparisons, superiority, guarantees, expertise, availability, safety, sustainability, social proof, and statements about what a product or service does. A polished sentence is not evidence. Do not turn an inference into a fact by removing words such as may, can, or intended to.

When a claim is necessary but its source is missing, ask a targeted question: what is the claim, which source approves it, what date or scope applies, and whether qualifiers are mandatory. If the user wants a draft before answering, keep the claim explicitly provisional or use a placeholder. Never hide the gap in confident prose.

Editing workflow

  1. Identify the source text, requested intervention, audience, channel, language, length, and non-negotiables.
  2. Mark what must remain: facts, names, numbers, promises, legal qualifiers, voice markers, and call to action.
  3. Make the smallest edit that solves the stated problem. For a structural or conversion rewrite, say what changed and what meaning was preserved.
  4. Re-check every changed claim against the supplied source. Do not introduce a new promise while improving flow.
  5. Return the edited copy and, when useful, a short note listing source gaps, significant changes, and alternatives.

Editing is not permission to sanitize personality. Retain useful irregularity, cultural context, directness, and point of view when they belong to the voice. Do not flatten a specific voice into generic professional, luxury, playful, or sales language.

New-copy workflow

  1. Confirm the brief: objective, audience, offer or subject, channel, format, language, desired action, tone, constraints, and available evidence.
  2. Build the claim ledger. If a required input is missing, ask for it or mark the exact gap before writing.
  3. Draft with concrete nouns, active verbs, honest qualifiers, and a rhythm appropriate to the channel. Prefer specificity that can be defended over intensity that merely sounds persuasive.
  4. Separate factual copy from optional creative routes. Label alternatives as options, not approved positioning.
  5. Run a claim pass, a voice pass, a clarity pass, and a channel pass. Check headings, CTA, links, character limits, accessibility, and translation implications when relevant.

For a new draft, a useful output is:

  • brief and assumptions;
  • facts used and sources;
  • copy draft;
  • open questions or [SOURCE NEEDED] markers;
  • optional variants with the trade-off for each.

Use judgment about how much process to show. Do not bury a short requested line under a giant methodology report.

Human voice and claims

  • Prefer plain, concrete language over hype, filler, and stacked adjectives.
  • Keep the user's language and regional conventions unless asked to translate or normalize them.
  • Avoid fake intimacy, invented urgency, empty superlatives, and claims that only sound true because they are familiar.
  • Do not add social proof, scarcity, guarantees, quantified outcomes, or authority signals without evidence.
  • Do not use a brand name as evidence of audience, values, market, or promise.
  • Ask before changing a material promise, target audience, positioning, or point of view.

Verification and handoff

Before delivery, report only checks actually made:

  • factual claims reconciled to supplied sources;
  • voice and meaning preserved or intentionally changed;
  • channel, length, links, formatting, and accessibility checked where applicable;
  • unknowns and requested sources listed;
  • legal, regulatory, medical, or safety review marked NOT_RUN unless an authorized reviewer or source was provided.

Never claim that copy is compliant, approved, factual, or on-brand without identifying the evidence and approval boundary.

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.