Mmcp.market

one-page-marketing skill

by wondelai·wondelai/skills·2.3k stars·MIT

Build a complete marketing plan covering the full customer journey from stranger to raving fan. Use when the user mentions "marketing plan", "marketing strategy", "target market", "USP", "lead nurture", "customer lifetime value", "PVP Index", or "I dont know where to start with marketing". Also trigger when building a marketing plan from scratch, choosing acquisition channels, or designing end-to-end customer-lifecycle campaigns. Covers the PVP Index, channel selection, and advocacy systems. For brand messaging, see storybrand-messaging. For conversion optimization, see cro-methodology.

A100/100content scan

Is the one-page-marketing skill safe?

Clean: nothing in its files matched our rules. We read 11 files in the folder on 2026-09-28.

No findings.

Install the one-page-marketing skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/wondelai/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/plugins/marketing-cro/skills/one-page-marketing ~/.claude/skills/one-page-marketing
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

The 1-Page Marketing Plan Framework

A complete marketing system captured on a single page: a 3x3 grid of nine squares, each a critical stage in turning a stranger into a raving fan. Fill in all nine and you have a living marketing engine instead of a 50-page plan that never gets executed.

Core Principle

"Marketing is not an event — it is a process."

Most businesses treat marketing as disconnected tactics: an ad here, a social post there, a trade show when budget allows. The 1-Page Marketing Plan replaces that randomness with a sequential process across three phases of the customer journey -- BEFORE (identify exactly who the prospect is, craft a message that resonates, place it in the media they consume), DURING (capture leads, nurture the relationship, convert to paying customers), and AFTER (deliver a world-class experience, maximize lifetime value, turn customers into referral sources). When all nine squares work together, you have a marketing machine, not a collection of tactics.

Scoring

Goal: 10/10. Score by counting how many of the nine squares are filled in specifically and measurably -- a square counts only when it would pass its row in the Quick Diagnostic (e.g. square 1 counts only if you can describe the ideal customer in one specific paragraph; square 2 only if you can complete "We are the only that "). Map the count to the band below. Always state the current score and the specific improvements needed to reach 10/10.

The 9-Square Grid

See references/one-page-plan-template.md when filling the grid -- it has the blank 9-square template with per-square prompts plus two fully worked examples.

BEFORE Phase (Prospect to Lead)

1. Target Market

Core concept: Use the PVP Index (Personal fulfillment, Value to marketplace, Profitability) to select a niche you can dominate. Stop trying to sell to everyone -- the riches are in the niches.

Why it works: Narrow focus makes your message more specific, your offer more relevant, and your acquisition cost lower. A specialist commands higher fees and deeper trust than a generalist.

Key insights:

  • Score niches on three dimensions: Personal fulfillment (do you enjoy serving them?), Value to marketplace (do they urgently need it?), Profitability (can and will they pay enough?)
  • Build a detailed ideal customer avatar: demographics, psychographics, pain points, desires, watering holes
  • Go narrow enough that the target feels you are speaking directly to them -- "if you speak to everyone, you speak to no one"
  • One niche means one marketing message to one audience, not one product

Product applications:

Copy patterns:

  • "We work exclusively with [niche] who struggle with [specific problem]"
  • "The only [product/service] designed specifically for [target market]"
  • "Unlike generic solutions, this was built from the ground up for [niche]"

See references/target-market.md when selecting the niche -- it has the anchored PVP scoring rubric and the fillable avatar worksheet.

2. Craft Your Message

Core concept: Your message must answer one question: "Why should I buy from you rather than your nearest competitor?" That answer is your Unique Selling Proposition (USP) -- without it you are a commodity competing on price.

Key insights:

  • A USP is not a slogan -- it is a defensible, provable market position
  • Build it around specialization, a unique mechanism, a bold guarantee, a proprietary process, or an underserved niche
  • Elevator pitch in under 30 seconds: "You know how [target market] struggles with [problem]? What we do is [solution], so that [outcome]."
  • Swap test: if a competitor's name fits your message, it is too generic

Product applications:

Copy patterns:

  • "You know how [target] struggles with [pain]? We [solution] so they can [outcome]."
  • "The only [category] that [unique differentiator]"
  • "We guarantee [specific result] or [risk reversal]"

See references/craft-message.md when drafting the USP -- it has the five USP strategies, the creation process, and the commodity-trap escapes.

3. Advertising Media

Core concept: Apply direct response principles to every advertising dollar: trackable, measurable, and designed to provoke a specific action -- never vague "brand awareness." Choose channels where your target market actually spends time.

Key insights:

  • Pick channels by where the target market actually is, not what is trendy
  • Master one channel before adding another -- never spread thin across five platforms
  • Track Customer Acquisition Cost (CAC) per channel and compare to Customer Lifetime Value (LTV)
  • Organic builds authority, paid buys speed -- they work together

Product applications:

Copy patterns:

  • Every ad needs: a headline that calls out the target, a compelling offer, a clear call to action, a tracking mechanism
  • "Attention [target market]: [headline about their pain/desire]"
  • "Call [tracked number] / Visit [tracked URL] to claim your [specific offer]"

See references/advertising-media.md when choosing channels -- it has the selection matrix, CAC-vs-LTV tracking, and attribution.

DURING Phase (Lead to Customer)

4. Capture Leads

Core concept: The goal of marketing is not the immediate sale -- it is building a database of interested prospects by exchanging genuine value (lead magnets) for contact information. Your database is the most valuable asset in your business.

Why it works: Only about 3% of any market is ready to buy right now. Capturing leads keeps you in contact with the other 97% so you can sell when they are ready.

Key insights:

  • The best lead magnets solve a specific, immediate problem for your target market
  • Speed-to-lead is critical: respond within 5 minutes and conversion skyrockets
  • Use a CRM from day one -- never memory, spreadsheets, or sticky notes
  • Your opt-in page has one job: exchange contact info for the lead magnet
  • Score leads so you prioritize the hottest first

Product applications:

Copy patterns:

  • "Download the free [resource] that shows you how to [desired result]"
  • "Take the free [quiz/assessment] and discover your [score/type/result]"
  • "Get instant access to [resource] — no credit card required"

Ethical boundary: Collect only data you will use, and never sell or share contact data without explicit opt-in consent.

See references/capture-leads.md when designing the lead magnet and opt-in -- it has lead-magnet types, opt-in page design, and lead scoring.

5. Nurture Leads

Core concept: Most leads are not ready to buy immediately -- nurturing builds the relationship through consistent value delivery, education, and trust until they are.

Why it works: People buy from those they know, like, and trust. Nurturing positions you as a helpful authority and keeps you top-of-mind, so when the prospect is finally ready, you are the obvious choice.

Key insights:

  • The welcome sequence matters most: it sets expectations and builds the initial relationship
  • Cadence: educate, entertain, inspire, then offer -- roughly a 3:1 value-to-ask ratio
  • Email is the backbone; reinforce with retargeting ads, social media, direct mail, SMS
  • Segment by behavior (clicks, downloads, views), not just demographics
  • The fortune is in the follow-up -- most sales happen between the 5th and 12th contact

Product applications:

Copy patterns:

  • "Here is the #1 mistake [target market] makes with [topic] — and how to fix it"
  • "How [client name] went from [before state] to [after state] in [time period]"
  • "I noticed you downloaded [lead magnet]. Here is the next step..."

Ethical boundary: Put one-click unsubscribe in every send and honor it immediately (CAN-SPAM / GDPR).

See references/nurture-leads.md when building the welcome sequence -- it has sequence templates, cadence, and behavioral segmentation.

6. Sales Conversion

Core concept: Convert nurtured leads into paying customers by removing friction, overcoming objections, building trust through social proof and guarantees, and making it as easy as possible to say yes.

Why it works: People hesitate for predictable reasons: fear of making a mistake, lack of trust, and confusion about the next step. Pricing psychology, risk reversal, and a structured sales process address those reasons directly.

Key insights:

More skills from wondelai/skills

  • A37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
  • A37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
  • A37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Ablue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
  • Ablue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
  • Ablue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
  • Aclean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
  • Aclean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
  • Aclean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.

All agent skills → · MCP servers