Agent skill
acquisition-conversion
Diagnose and improve acquisition conversion across landing pages, forms, popups and signup/account creation through registration or qualified handoff.
Filed under Content and SEO.
From mia-ppp/PMM-Skills · 45 skill entries · 71 · pushed 2026-10-16
What it does when it runs
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.
Automated analysis of the skill and the 6 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Ask about acquisition-conversion
Opens your assistant with this page's recorded context. Check the linked sources before relying on it.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/mia-ppp/PMM-Skills.git /tmp/PMM-Skills git -C /tmp/PMM-Skills sparse-checkout set "skills/acquisition-conversion" mkdir -p ~/.claude/skills/acquisition-conversion cp -R "/tmp/PMM-Skills/skills/acquisition-conversion/." ~/.claude/skills/acquisition-conversion/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from mia-ppp/PMM-Skills/blob/5281aa6e55ca12d2ad5f97c3bf45e8cf49488225/skills/acquisition-conversion/SKILL.md, which is licensed MIT (repository). 352 words, 6 headings.
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.
| Mode | Decisions and reference |
|---|---|
| Landing/page | Message match, evaluation needs, proof, CTA hierarchy and traffic intent: page. |
| Forms | Field justification, qualification versus completion, progressive profiling, errors, mobile and demo routing: forms. |
| Popups | Context, offer, trigger, suppression, frequency, dismissal and accessibility: popups. |
| Signup/account creation | Commitment expectations, authentication/SSO, verification, friction and abandonment: signup. |
Workflow and output
- 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.
- 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.
- 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.
- Brief
marketing-copyfor final page/form/offer copy,website-buyer-journeyfor path changes,email-sequencefor nurture/abandonment, andrevopsfor qualified demo routing, SLA and recycling. Web/Product/Design own deployment and accessible interactions. - Define completion, qualification, downstream quality and customer-respect guardrails. Use
analytics-trackingfor measures and instrumentation requirements andmarketing-experimentationfor 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.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- conversion-tracking by coreyhaines31 · 57,918
- conversion-path-analysis by irinabuht12-oss · 6,620
- conversion-ops by ericosiu · 3,766
- meeting-conversion by louisblythe · 195
- conversion-rate-optimization by manojbajaj95 · 109
- trial-poc-conversion by NEON-Rutger · 58
- pilot-to-conversion by zime-ai · 19
- conversion-funnel by sidchaudhary · 6
Need help setting it up?
This page tells you what acquisition-conversion does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.