agentleFS
Sign inStart free
witi-projectswiti-projects/Skills/writing-copy/SKILL.md

writing-copy

Skill2 starsChanged 7 months agoMITView on GitHub

Write marketing copy for landing pages, product descriptions, CTAs, emails, and app UI text. Use when the user says "/writing-copy", "writing copy", or asks about writing copy.

4 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    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 clear, compelling copy for products and marketing.

    line 9
  2. Distinctive:

    P.S: Use for urgency or a secondary point (highest-read part after the subject)

    line 85
  3. Distinctive:

    Read your copy out loud — if it sounds awkward, rewrite it

    line 89
  4. Distinctive:

    Use the "so what?" test: after every sentence, ask "so what?" — the answer should be obvious

    line 91

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

Writing Copy

Write clear, compelling copy for products and marketing.

Principles

  1. Clarity over cleverness — users should instantly understand what you're saying
  2. Benefits over features — "Save 2 hours a day" beats "AI-powered automation"
  3. One idea per section — don't overload the reader
  4. Active voice — "We send your report" not "Your report will be sent"
  5. Short sentences — aim for 15-20 words per sentence

Landing Page Structure

Hero Section

  • Headline: One sentence, states the core value (8-12 words)
  • Subheadline: Expands on the headline, addresses who it's for (15-25 words)
  • CTA: Clear action verb ("Start free trial", "Get started", "Try for free")
Headline:    Ship faster with AI-powered code review
Subheadline: Catch bugs, enforce standards, and merge with confidence — 
             built for teams that move fast.
CTA:         Start free trial →

Features Section

For each feature:

  • Short title (3-5 words)
  • One sentence explaining the benefit
  • Optional: icon or screenshot

Social Proof

  • Customer logos, testimonials, metrics
  • Specific numbers: "Used by 10,000+ teams" not "Used by many teams"
  • Quotes with name, title, company

CTA Section

  • Repeat the primary CTA
  • Address objections: "No credit card required", "Free for up to 5 users"

Button & CTA Copy

Good:

  • "Start free trial"
  • "Get started — it's free"
  • "Download the app"
  • "See pricing"
  • "Book a demo"

Bad:

  • "Submit"
  • "Click here"
  • "Learn more" (too vague as a primary CTA)
  • "Get started now for free today!" (too long)

Microcopy (UI Text)

Error messages:

  • Say what happened and what to do: "Payment failed. Please check your card details and try again."
  • Not: "Error 422" or "Something went wrong"

Empty states:

  • Guide the user: "No projects yet. Create your first project to get started."
  • Not: "No data"

Confirmation dialogs:

  • Be specific: "Delete this project? This will remove all tasks and cannot be undone."
  • Button: "Delete project" (not "OK")

Loading states:

  • "Setting up your workspace..." (not "Loading...")

Email Copy

  • Subject line: 6-10 words, specific, no ALL CAPS
  • First line: Get to the point — why should they care?
  • Body: One CTA, not three
  • P.S.: Use for urgency or a secondary point (highest-read part after the subject)

Tips

  • Read your copy out loud — if it sounds awkward, rewrite it
  • Cut every word that isn't doing work
  • Use the "so what?" test: after every sentence, ask "so what?" — the answer should be obvious
  • A/B test headlines and CTAs when possible
  • Match the tone to your audience (developer docs ≠ consumer marketing)

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.

Check your setup, free