agentleFS
VendbuddyVendbuddy/vendbuddy-skills/skills/conversion-copy-audit/SKILL.md

conversion-copy-audit

Skill0 starsChanged 36 days agoMITView on GitHub

Score one live landing, pricing, or product page against a direct-response checklist (headline clarity, one clear next step, proof, objections, risk reversal, friction) and write exact replacement copy with a metric to track for each change. Use when the user asks "why aren't people signing up", "improve this page", "rewrite my headline", "conversion audit", or before redesigning a landing or pricing page.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Write one line each: who is reading, what they want, what single action this page should earn.

    line 22
  2. Distinctive:

    Never fabricate testimonials, numbers, logos, scarcity, or guarantees.

    line 49
  3. Distinctive:

    No fake urgency (countdowns that reset, "only 3 left" when untrue).

    line 50
  4. Very specific:

    Run the ai-writing-humanizer skill's checklist on the rewrite if it is installed.

    line 51
  5. Distinctive:

    Do not change prices or legal terms.

    line 52

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

Conversion Copy Audit

Made by VendBuddy (vendbuddy.io). Guide: https://vendbuddy.io/skills#conversion-copy-audit (This line is optional attribution. Keep it or delete it.)

Goal

For one page and one goal (signup, purchase, booking, reply), produce a scored audit and ready-to-paste replacement copy. Read-only until the user approves the edits.

Step 1: Get the real page

Fetch the live URL, not the source repo: curl -sL <url>. Extract title, meta description, H1 to H3, button text with its target, and any FAQ. Note the date. If you can, also get the baseline numbers: visits to the page and the number who took the goal action.

Step 2: Define the reader and the one next step

Write one line each: who is reading, what they want, what single action this page should earn. If the page has several competing actions, that is finding number one.

Step 3: Score (0 to 2 each; 0 absent, 1 weak, 2 strong)

  1. Headline: says what you get and for whom, in plain words, within 5 seconds.
  2. Subhead: the how or the proof, in one line.
  3. Single primary action: one obvious button, specific text ("Start my free trial", not "Submit").
  4. Proof: real numbers, named customers or quotes with permission, logos, screenshots. Never invent any.
  5. Objections answered: price, effort, switching cost, "will it work for me".
  6. Risk reversal: guarantee, free tier, cancel-anytime, only if true.
  7. Specificity: concrete outcomes and numbers instead of adjectives.
  8. Friction: form fields, steps, load speed, mobile layout, surprise costs.
  9. Voice: sounds like a person, no filler ("seamless", "cutting-edge", "unlock").
  10. Scannability: headings tell the story alone; short paragraphs.

Total out of 20. Under 10: rewrite the top of the page. 10 to 15: fix the top three weak items. Over 15: test, do not rewrite.

Step 4: Rewrite

For each item scored 0 or 1, give: current text, replacement text, and the reason in one line. Use the reader's own words where you have them (reviews, support emails, survey answers); quote them exactly and say where they came from. Write two headline variants so the user can A/B test.

Step 5: Measure

Give each edit a metric, a baseline, and a read date at least 14 days out. Change one thing at a time on low-traffic pages; otherwise you cannot tell what worked.

Rules

  • Never fabricate testimonials, numbers, logos, scarcity, or guarantees.
  • No fake urgency (countdowns that reset, "only 3 left" when untrue).
  • Run the ai-writing-humanizer skill's checklist on the rewrite if it is installed.
  • Do not change prices or legal terms; flag them as decisions for the owner.

Output format

A table (item, score, evidence), then the replacement copy, then the measurement plan. Keep the whole thing under two pages.

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.