agentleFS
Sign inStart free
mia-pppmia-ppp/PMM-Skills/skills/acquisition-conversion/SKILL.md

acquisition-conversion

Skill2 starsChanged 28 days agoMITView on GitHub

Diagnose and improve acquisition conversion across landing pages, forms, popups and signup/account creation through registration or qualified handoff. Use for CRO, abandonment, demo requests and signup friction. Product activation and upgrades have separate owners.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ../_shared/evidence-gaps.md and ../_shared/ssot-consumption.md.

    line 12
  2. Very specific:

    Read ../_shared/segment-selection.md when an audience decision is needed.

    line 14
  3. Very specific:

    Do not edit SSOT. Route proposed canon changes to ssot-context-loop for human review and approval.

    line 16
  4. Very specific:

    Do not introduce deceptive urgency, impossible promises, involuntary opt-ins or blocked dismissal.

    line 40

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

Acquisition Conversion

Approved context and evidence

Read ../_shared/evidence-gaps.md and ../_shared/ssot-consumption.md. Load only relevant approved manifest context and record sources in Inputs and assumptions. Read ../_shared/segment-selection.md when an audience decision is needed; inherit accepted segments and ICP. Separate sources, interpretation, and proposals. Missing evidence remains Assumed or Gap. Do not edit SSOT. Route proposed canon changes to ssot-context-loop for human review and approval.

Modes

Choose the journey bottleneck and load the relevant reference. Combine modes when the evidence spans steps.

ModeDecisions and reference
Landing/pageMessage match, evaluation needs, proof, CTA hierarchy and traffic intent: page.
FormsField justification, qualification versus completion, progressive profiling, errors, mobile and demo routing: forms.
PopupsContext, offer, trigger, suppression, frequency, dismissal and accessibility: popups.
Signup/account creationCommitment expectations, authentication/SSO, verification, friction and abandonment: signup.

Workflow and output

  1. Define the acquisition start, successful registration or qualified-handoff endpoint, audience, traffic source and denominator. Map each step and distinguish missing data from observed loss.
  2. Diagnose message match, offer fit, buyer questions, trust and interaction friction. Justify every requested field and commitment. Do not optimize completion at the expense of qualified demand without showing the trade-off.
  3. Produce Inputs and assumptions, journey/bottleneck diagnosis, Quick Wins, High-Impact Changes, prioritized Test Ideas, implementation acceptance criteria, and ranked Evidence gaps. Treat copy alternatives as proposals pending proof and canon checks.
  4. Brief marketing-copy for final page/form/offer copy, website-buyer-journey for path changes, email-sequence for nurture/abandonment, and revops for qualified demo routing, SLA and recycling. Web/Product/Design own deployment and accessible interactions.
  5. Define completion, qualification, downstream quality and customer-respect guardrails. Use analytics-tracking for measures and instrumentation requirements and marketing-experimentation for test design.

Endpoint boundaries

Successful signup is the endpoint here. First value and stalled-user recovery route to product-activation; upgrade eligibility, timing and conversion route to upgrade-conversion. Do not introduce deceptive urgency, impossible promises, involuntary opt-ins or blocked dismissal. output-quality-check verifies the brief; messaging-consistency-audit independently reviews market-facing meaning. Launch clearance belongs to launch-readiness-check.

Related skills

marketing-copy, website-buyer-journey, product-activation, upgrade-conversion, revops, email-sequence, analytics-tracking, marketing-experimentation.

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