Acquisition Conversion logo

Acquisition Conversion

Community
mia-ppp
acquisition-conversion

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.

Overview

Publishermia-ppp
RepositoryPMM-Skills
Skill nameacquisition-conversion
Stars
76
Forks
2
Bundled files
6
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by mia-ppp on GitHub. Read the source before you install it.

Installation

Install the Acquisition Conversion AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/mia-ppp/PMM-Skills/tree/main/skills/acquisition-conversion
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mia-ppp/PMM-Skills.git /tmp/PMM-Skills
mkdir -p .claude/skills
cp -r /tmp/PMM-Skills/skills/acquisition-conversion .claude/skills/acquisition-conversion
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Acquisition Conversion in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Acquisition Conversion on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Acquisition Conversion is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Acquisition Conversion AI skill do?

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.

Why use Acquisition Conversion on TypingMind?

Because you install it once and use it with any model. Acquisition Conversion is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Acquisition Conversion in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mia-ppp/PMM-Skills/tree/main/skills/acquisition-conversion. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Acquisition Conversion?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Acquisition Conversion?

As many as you like. As long as a model supports skills, you can use Acquisition Conversion with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Acquisition Conversion AI skill free?

Yes. It is published on GitHub by mia-ppp under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇