write-copy
Skill15 starsChanged 14 days agoApache-2.0View on GitHub
Route promotional copy to a topic specialization. Use /write-copy, "write campaign copy", or "write event copy". For a known event video use write-copy-event-video directly; for faithful prose repair use human-rewrite.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- forsvn-labs/meta-skillstheir own version, first seen Aug 11, 2026
- sivi/skillstheir own version, first seen Jul 30, 2026
- Zenobia0000/dtc-copywriting-skillstheir own version, first seen Mar 20, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- forsvn-labs/meta-skills★ 14same name
- Zenobia0000/dtc-copywriting-skills★ 4same name
- sivi/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository95 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- agent-mailboxSkill
- agent-outputSkill
- ask-gateSkill
- ask-meSkill
- audit-coupled-constantSkill
- budget-checkSkill
- build-prototypeSkill
- caller-optionsSkill
- cold-reviewSkill
- debug-taskSkill
- define-termsSkill
- defuddleSkill
- design-an-interfaceSkill
- diff-recapSkill
- directives-auditSkill
- domain-checkSkill
- double-checkSkill
- extract-signalSkill
- freshness-contractSkill
- github-syncSkill
- handoff-executeSkill
- handoffSkill
- headless-claudeSkill
- headless-codexSkill
- headless-geminiSkill
- headless-grokSkill
- headless-modelsSkill
- headless-update-modelsSkill
- headless-usageSkill
- human-drawSkill
- human-mergeSkill
- human-outputSkill
- human-rewriteSkill
- implement-taskSkill
- improve-codebase-architectureSkill
- insight-adversarialSkill
- insight-anglesSkill
- insight-assessSkill
- insight-critiqueSkill
- insight-cross-examineSkill
- insight-exploreSkill
- insight-premortemSkill
- insight-reference-classSkill
- insight-retroSkill
- insight-root-causeSkill
- insight-skill-gapSkill
- insight-test-assumptionSkill
- insight-value-of-informationSkill
- investigateSkill
- json-canvasSkill
- map-checkSkill
- map-initSkill
- map-maintainSkill
- map-rulesSkill
- map-thisSkill
- monorepo-depsSkill
- multi-agent-modeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
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
- Distinctive: line 16
Write promotional copy from verified facts and a clear audience need.
- Distinctive: line 29
If the event specialist is absent, identify the missing dependency.
- Distinctive: line 36
Keep spoken words, on-screen words, delivery directions, and publishing captions distinguishable.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
/write-copy
Write promotional copy from verified facts and a clear audience need. This is the family entry point. Drafting does not authorize publishing, media generation, purchases, or changes to accounts.
Route by subject and purpose
Use the existing conversation before asking for missing information. Identify the subject being promoted, audience, desired action, language, and delivery medium. Topic and medium are separate: an event is a topic; a video is a medium. Do not turn every writing task into an event advertisement.
| Requested work | Route |
| Course, workshop, session, conference, or other event promoted through a campaign video, including its narration and post caption | Read and follow write-copy-event-video |
| Event video already has an approved message and needs a copy revision | Same specialist; preserve the approved promise, facts, tone, and scope |
| News, product launch, service campaign, fundraising, or another topic | No specialization is implemented yet. Say so; offer an ordinary copy draft scoped to that topic, without claiming a tested family recipe |
| Prose cleanup with no promotional strategy request | Use human-rewrite if installed; otherwise perform the requested faithful edit directly |
If the event specialist is absent, identify the missing dependency. Do not silently invent its workflow. The prose-repair sibling is optional and is not required for event copy.
Family contract
- Preserve the requested audience, language, register, and commercial intent. Do not infer the output language from the language of the conversation alone.
- Separate facts, promised outcomes, and creative hypotheses. Unknowns remain visible in a draft.
- Deliver usable text with a single primary action, not a catalogue of marketing techniques.
- Keep spoken words, on-screen words, delivery directions, and publishing captions distinguishable.
- Design variations follow an agreed copy direction; drafting does not start production automatically.
- The event-video specialization normally commissions three independent complete copy variants, cross-examines them, then presents a fourth recommended synthesis first. Three means three total initial copies, not three per writer. An explicitly narrower revision may keep its requested scope.
Extending the family
Add a specialization only when a repeatable topic or purpose requires distinct inputs, evidence, techniques, or output checks. Name it write-copy-<specialization>, declare its trigger boundary, and add one explicit route here plus a taxonomy assignment. A medium-specific adapter belongs inside a specialization until it warrants a separate reusable workflow. Do not advertise planned specializations as available.
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
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.

