Mmcp.market

contagious skill

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

Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "referral program", "nobody is sharing it", or "make this spread". Also trigger when designing shareable features, crafting social campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.

A100/100content scan

Is the contagious skill safe?

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

No findings.

Install the contagious 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/contagious ~/.claude/skills/contagious
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

Word-of-Mouth & Virality Framework

A framework for engineering word-of-mouth and making products, ideas, and content contagious, based on Jonah Berger's research into why things catch on. Use it to design shareability into products, campaigns, and content instead of hoping for luck.

Core Principle

Virality is not born — it is engineered. Products spread because they were designed — consciously or not — to be shared. Only 7% of word-of-mouth happens online; the other 93% happens in offline conversations, so virality is about the psychology of sharing, not social media mechanics. Those psychological patterns are predictable and can be engineered into anything using the STEPPS framework.

See: references/word-of-mouth.md when the brief over-indexes on social media — it makes the offline-vs-online case, lists conversation triggers, and gives a WOM measurement/audit method.

Scoring

Goal: 10/10. Score each of the six STEPPS drivers (the six Quick Diagnostic rows) — 0 absent, 1 present but weak, 2 strong and deliberate — for a raw 0-12, then map: 11-12 -> 10, 9-10 -> 8-9, 6-8 -> 6-7, 3-5 -> 4-5, 0-2 -> <=3. Bands:

  • 9-10 — three or more drivers at strength 2, at least one of them Public or Social Currency (the self-propagating ones), and the brand survives the Trojan Horse test.
  • 6-8 — two drivers genuinely strong, but spread still leans on paid reach or product quality alone.
  • <=5 — at most one weak driver; sharing is incidental, not engineered.

Report the raw count, the mapped score, and the specific driver(s) to raise next to reach 10/10.

STEPPS Overview

Not a checklist — a multiplier. Each principle independently increases sharing; the most contagious ideas activate several at once, but even one or two done well dramatically increase word-of-mouth.

The STEPPS Framework

1. Social Currency

Core concept: People share things that make them look good — smart, cool, in-the-know. Make people feel like insiders and they'll spread it to boost their own image.

Why it works: Sharing is self-presentation — listeners infer the sharer's traits from what they pass on, so people curate shares the way they curate clothes. Mechanism: give the sharer a payoff in status or identity and you outsource your marketing to their ego.

Key insights:

  • Remarkability — surprising, novel, or extreme things make the sharer seem interesting; "Did you know...?" is a powerful sharing trigger
  • Game mechanics — leaderboards, badges, and status tiers create visible accomplishments people want to display
  • Exclusivity and scarcity — secret menus and invite-only access give people "insider knowledge" to share
  • Inner remarkability — even mundane products have a remarkable angle; it's framing, not the product

Product applications:

Copy patterns:

  • "Most people don't know that..."
  • "You're one of the first to try..."
  • "You've unlocked [achievement]..."

Ethical boundary: Create real insider value, not false scarcity or manufactured exclusivity that breeds toxicity.

See: references/social-currency.md when a product feels unremarkable — it has the inner-remarkability exercise, game-mechanic design, exclusivity types, and a scored audit.

2. Triggers

Core concept: Top-of-mind means tip-of-tongue. Link your product to environmental cues — sights, sounds, times, routines — so everyday life keeps reminding people to talk about you.

Why it works: Most word-of-mouth is driven not by excitement but by whatever happens to be top-of-mind mid-conversation; a product linked to a frequent cue gets mentioned more because it's more accessible in memory.

Key insights:

  • Frequency beats strength — a daily trigger (coffee) outperforms a powerful but rare one (a holiday); Kit Kat linked itself to coffee breaks
  • Habitat matters — map where and when people encounter contexts related to your product
  • Competitive triggers — link a competitor's moment to your own brand
  • Ongoing vs. temporary — persistent environmental triggers sustain word-of-mouth; event triggers only spike it

Product applications:

Copy patterns:

  • "Every time you [frequent activity], think of..."
  • "Next time you [daily habit]..."
  • "It's [day/time] — time for..."

Ethical boundary: Build genuine, helpful associations — hijacking sensitive contexts (grief, health scares) as triggers backfires.

See: references/triggers.md when picking a cue to attach to — it has the habitat-analysis worksheet, the frequency matrix, and the 4-step trigger design process.

3. Emotion

Core concept: When we care, we share. High-arousal emotions — positive (awe, excitement, amusement) or negative (anger, anxiety) — drive sharing; low-arousal emotions (sadness, contentment) suppress it.

Why it works: Physiological arousal — racing heart, activated state — creates a need to share. It's activation vs. deactivation, not positivity vs. negativity.

Key insights:

  • High-arousal drives sharing: awe, excitement, amusement, inspiration, anger, anxiety
  • Low-arousal suppresses it: contentment and relaxation feel no urgency; sadness makes people withdraw
  • Awe is the most powerful sharing emotion — feeling small before something vast or surprising spreads furthest
  • Emotional framing — the same facts can be framed for different arousal levels; facts inform, framing motivates sharing

Product applications:

Copy patterns:

  • "I can't believe [surprising fact]..."
  • "Watch what happens when..."
  • "This will change how you think about..."

Ethical boundary: Engineering outrage for clicks corrodes trust — use high-arousal negative emotion sparingly and only when the cause genuinely warrants it.

See: references/emotion.md when content feels flat — it has the emotion-sharing matrix, awe-engineering techniques, and humor design rules.

4. Public

Core concept: Built to show, built to grow. If people can see others using your product, they're more likely to adopt it — design for observability.

Why it works: Visible choices resolve uncertainty for the observer — seeing others use a product lowers their perceived risk and supplies social proof at zero marginal cost, so observability turns each user into a passive, continuous billboard.

Key insights:

  • Behavioral residue — design visible traces that outlast use: a Livestrong wristband long outlives the donation
  • Self-advertising products — every Hotmail email carried "Get your free email at Hotmail"; the product marketed itself through use
  • Public = imitable — people can only copy what they can observe; find ways to make invisible usage visible

Product applications:

Copy patterns:

  • "Show the world you [achievement/identity]..."
  • "Share your [output] — powered by [brand]..."
  • "Join [number] others who..."

Ethical boundary: Visibility must empower, never shame — users always control what becomes public, and private data (failures, health, finances) stays private.

See: references/public-visibility.md when usage is invisible — it has the public-vs-private breakdown, the behavioral-residue design checklist, and the Apple-logo design lesson.

5. Practical Value

Core concept: People share useful information to help others. News you can use spreads — especially packaged for easy passing along.

Why it works: Sharing practical value is altruism — if your content saves people time, money, or effort, they'll forward it as a favor to their network.

Key insights:

  • Prospect Theory — people judge deals against reference points: $10 off a $20 item feels better than $10 off a $1,000 item
  • Rule of 100 — under $100, use percentage discounts ("50% off"); over $100, use dollar amounts ("$200 off")
  • Narrow audience = wider sharing — niche content gets forwarded to "the person who needs this"
  • Knowledge packaging — lists, how-tos, and tip collections are inherently more shareable than essays

Product applications:

Copy patterns:

  • "The [number]-step guide to..."
  • "Quick tip: [immediately useful advice]..."
  • "Share this with someone who needs to hear it"

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