agentleFS
forsvn-labsforsvn-labs/meta-skills/skills/improve-conversion/SKILL.md

improve-conversion

Skill14 starsChanged 3 months agoMITView on GitHub

Diagnose and improve a landing page, funnel, campaign, ad, message, content asset, or outreach flow. Use for conversion audits, teardown requests, campaign or creative evaluation, funnel diagnosis, prioritizing growth opportunities, proposing controlled experiments, or revising weak marketing work into a stronger ready-to-use version.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    keep, revise, or kill rule.

    line 51
  2. Distinctive:

    Keep deployments, experiment activation, spend, publishing, and other external writes behind explicit approval.

    line 68

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

Improve conversion performance

Return a diagnosis, revised work, and one discriminating test—not a decorative scorecard.

Establish the intended path

Identify:

  • intended audience and costly moment;
  • promise, mechanism, proof, and objection;
  • acquisition source and message expectation;
  • primary action and downstream value;
  • available exposure, behavior, conversion, revenue, retention, and qualitative evidence.

Separate missing data from zero. Treat vanity engagement as diagnostic, not business performance.

Locate the first meaningful break

  1. Reach: the right people did not encounter it.
  2. Attention: they encountered it but did not stop.
  3. Comprehension: they stopped but did not understand.
  4. Belief: they understood but did not trust the promise.
  5. Motivation: they believed it but did not care enough now.
  6. Friction: they wanted it but the next step was costly or broken.
  7. Value: they acted but the product or offer did not deliver.

Inspect audience, channel, device, geography, and customer mix before aggregating. Treat co-timed movement as correlation until evidence distinguishes causes. State the mechanism connecting each proposed cause to the observed behavior.

Prioritize a discriminating test

Name plausible alternative explanations. Choose the smallest change that produces different predictions for the leading explanations.

Define:

  • hypothesis and causal mechanism;
  • one intentional change;
  • target segment and surface;
  • primary outcome and guardrails;
  • observation window;
  • keep, revise, or kill rule.

Accept “inconclusive” when evidence cannot discriminate.

Deliver

Lead with:

  • Keep: what evidence supports retaining.
  • Drop: what is weak, harmful, or unnecessary.
  • Change: the revised message, structure, or experience.
  • Test: the highest-value uncertainty and controlled experiment.

Include the ready-to-use revision whenever the medium permits. Tie every recommendation to observed evidence, an explicit inference, or a labeled assumption. Do not claim causality or conversion lift without evidence.

Keep deployments, experiment activation, spend, publishing, and other external writes behind explicit approval.

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.