agentleFS
tderousseltderoussel/agent-skills/skills/copywriting/SKILL.md

copywriting

Skill1 starsChanged 24 days agoMITView on GitHub

Write or edit customer-facing copy for landing pages, emails, SMS, ads, listing descriptions, social posts, lead magnets, or sales letters. Use when copy feels generic, salesy, or like ChatGPT, and whenever persuasive writing needs testimonials, statistics, case-study results, or other proof. Research the reader and original examples, ground every specific, and deliver publishable copy with clear evidence gaps.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use paywalls, popups and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 17 projects that use this

  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 16 projects that use this

  • ukunal91appSkill

    revops

    When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.

    Also in 38 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 21 projects that use this

  • timruebenachSkill

    competitor-profiling

    When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitor-alternatives. For sales-specific battle cards, see sales-enablement.

    Also in 25 projects that use this

  • silvainfmSkill

    competitor-alternatives

    When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.

    Also in 33 projects that use this

  • +4 more from Cesarjoquin

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 8

    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:

    Read the actual product, service, listing, or deliverable.

    line 18
  2. Distinctive:

    Verify time-sensitive facts and high-stakes claims with current primary sources.

    line 20
  3. Distinctive:

    Use only tools and material actually accessible in this session.

    line 23
  4. Distinctive:

    Never invent a testimonial, customer name, quote, price, trial period, date, metric, feature, award, research citation, result, scarcity, …

    line 27
  5. Very specific:

    Keep a missing detail explicit inside the working draft, such as {{NEEDS: actual offer terms}}.

    line 35
  6. Distinctive:

    Use traceable proof where it answers a real doubt.

    line 45
  7. Distinctive:

    Email or SMS: use a truthful subject or opening, real relationship context, one purpose, and an appropriate response path.

    line 52
  8. Distinctive:

    Real estate listing: verify property facts and listing status, describe features and experience accurately, and inspect wording, images, …

    line 54
  9. Distinctive:

    Keep the useful tension or uncomfortable fact when evidence supports it.

    line 63

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

Copywriting

Make the reader's decision easier with relevant specifics and traceable proof. Treat voice and factual accuracy as separate editing jobs; better prose does not repair an invented claim.

Establish one reader and one decision

Use the brief, product, permitted customer material, and supplied examples before asking questions. Name the reader, traffic source, what they already know, what they are skeptical about, and the next useful action. Awareness belongs to the incoming audience; cold social and branded search need different opening lines.

Capture the real offer and terms, actual capability, voice, format constraints, objections, and available proof. Keep unknowns visible in a working fact sheet. Do not force a long questionnaire when a useful draft can proceed from verified material.

Research before drafting

  1. Read the actual product, service, listing, or deliverable. Use permitted customer questions, reviews, inquiries, support tickets, or sales notes to identify language and objections. Competitor reviews can suggest a question; they cannot prove this offer delivers.
  2. Study relevant original public examples when research can improve the result. Keep URLs and brief observations about the hook, structure, proof, and action. Study the mechanism without copying prose or treating views, likes, or a self-reported case study as conversion evidence.
  3. Verify time-sensitive facts and high-stakes claims with current primary sources. Inspect the source itself, its scope and date, and whether it actually supports the intended wording. Do not repeat a statistic because many articles cite one another.
  4. Convert the evidence into a short message brief: reader's problem in their language → supported outcome → mechanism → proof → decision. Distinguish verified facts, customer reports, interpretations, and hypotheses.

Use only tools and material actually accessible in this session. If a source is unavailable, label the gap or omit the claim; do not invent what the research would have found.

Ground every specific

Never invent a testimonial, customer name, quote, price, trial period, date, metric, feature, award, research citation, result, scarcity, or deadline. Before including a concrete detail, identify where it came from and whether it may be used in this context.

Maintain a compact claim ledger for proof-heavy work:

ClaimEvidenceStatusAllowed wording
Specific proposed assertionBrief, product observation, permitted customer record, or primary sourceVerified, reported, uncertain, or missingWording justified by the evidence and its limits

Keep a missing detail explicit inside the working draft, such as {{NEEDS: actual offer terms}}. Do not leave placeholders in material presented as ready to publish. If a missing fact is nonessential, remove that claim and finish the copy. Ask for missing load-bearing facts while completing independent work.

Use customer quotes only with traceable wording, identity, context, and appropriate permission. Do not attach an invented quote to a real person, composite persona, or plausible name. Paraphrases must remain faithful and be labeled appropriately. Do not turn a competitor's results into this business's proof.

For advertising claims, reviews, or endorsements, consult current applicable primary guidance before publishing sensitive claims. The FTC advertising guidance and reviews and testimonials guidance are useful starting points for US work, not a substitute for checking the actual jurisdiction and context. Do not assert universal disclosure rules or fixed legal penalties from memory.

Draft the piece as a connected argument

  1. Open with the useful idea or offer suited to the reader's awareness. Use a direct offer for an informed reader; give a skeptical reader enough concrete context to understand the problem.
  2. State the supported benefit in familiar language, then explain how the product or service produces it. Prefer a demonstration or checkable detail to a broad adjective.
  3. Use traceable proof where it answers a real doubt. Match evidence to the claim rather than adding decorative testimonials.
  4. Address only relevant objections, and answer the ones raised. State material terms where the reader needs them.
  5. Give one main decision and a clear next step. Include a lower-commitment route only when it helps someone who is not ready.

Adapt to the channel:

  • Landing page: preserve the incoming promise; make the first screen understandable; connect the action to real fulfillment.
  • Email or SMS: use a truthful subject or opening, real relationship context, one purpose, and an appropriate response path. Drafting does not authorize sending.
  • Social post or video: earn attention with a concrete question, observation, or demonstration; deliver the promised point before the action. Do not infer results from reach alone.
  • Real estate listing: verify property facts and listing status, describe features and experience accurately, and inspect wording, images, and targeting under current applicable housing and brokerage guidance. Avoid protected-class preferences, steering, invented amenities, or guaranteed financial outcomes.
  • Lead magnet: deliver a complete useful result for a narrow question; make the next action naturally related to that result.

Edit for voice and reader comprehension

Replace generalities with supported details. Read the draft aloud and compare it with supplied real voice samples when available. Vary sentence and paragraph length naturally; use uncertainty language where the underlying claim is uncertain.

Cut repeated contrast formulas such as “not X, but Y,” artificial three-item rhythms, empty preambles, hype, and grand concluding uplift when they add no meaning. These are editorial checks, not a detector-avoidance formula. Do not impose a word blacklist or mechanical sentence quota that harms the reader's understanding.

Keep the useful tension or uncomfortable fact when evidence supports it. Do not polish away limitations, hide material terms, or make the copy more certain than the source.

Deliver and improve

Provide finished copy in the requested format, the most important source links or claim notes, and any unresolved facts that prevent publication. Provide alternatives only when they represent materially different angles; recommend one and explain the decision briefly.

For revisions, preserve verified facts and resolve the actual criticism rather than reskinning every sentence. Improve from real replies, customer feedback, calls, or observed funnel events. State sample size and denominator when interpreting results, and do not declare an A/B winner from inadequate evidence. Follow the user's existing authorization for publication or sending; this skill grants neither.

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.