agentleFS
afaraha8403afaraha8403/balakit/.claude/skills/marketing-psychology/SKILL.md

marketing-psychology

Skill1 starsChanged 12 days agoMITView on GitHub

Apply psychological principles and behavioral design to product copy, onboarding flows, landing pages, feature descriptions, CTAs, and pricing tiers. Covers cognitive biases (loss aversion, social proof, anchoring, paradox of choice, Zeigarnik effect, IKEA effect, reciprocity, commitment & consistency) and the Fogg Behavior Model (B = MAP). Use when the user asks about copy psychology, persuasion, behavioral design, conversion optimization, onboarding flow design, CTA wording, pricing psychology, or ethical influence.

129 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use product-marketing-context, popup-cro and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xfstudioSkill

    product-marketing-context

    When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.

    Also in 26 projects that use this

  • silvainfmSkill

    popup-cro

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.

    Also in 23 projects that use this

  • silvainfmSkill

    ab-test-setup

    When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.

    Also in 24 projects that use this

  • ukunal91appSkill

    churn-prevention

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.

    Also in 30 projects that use this

  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 11 projects that use this

  • ukunal91appSkill

    revops

    When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.

    Also in 26 projects that use this

  • +5 more from silvainfm

The file

Files
SKILL.md

Marketing Psychology

Leading words: loss aversion, social proof, anchoring, paradox of choice, Zeigarnik effect, IKEA effect, reciprocity, commitment & consistency, Fogg behavior model, ethical influence.

Apply cognitive biases and behavioral models to product surfaces — ethically. The goal is to reduce cognitive load, surface genuine value, and help the user act on what they already want — not to manipulate.

Decision model — surface → principle

Pick the surface the user is working on, then apply the primary principle (secondary principles reinforce). Depth on each principle lives in references/principles.md.

SurfacePrimary principleSecondary principle
CTA (call-to-action)Commitment & consistencyReciprocity
Pricing tier comparisonAnchoringLoss aversion
Onboarding flowIKEA effectParadox of choice (avoid)
Feature descriptionLoss aversionSocial proof
Reviews / testimonials / trustSocial proofReciprocity
Dashboard engagementZeigarnik effectLoss aversion
Error / empty stateReciprocityFogg: reduce ability cost

Phase 1 — Audit

- [ ] Identify the surface type from the decision model table above.
- [ ] Map the primary + secondary principle for that surface.
- [ ] Check the current copy's cognitive load (how many concepts must the
      user hold at once to act?).
- [ ] Check ethics: would the ethical-influence test pass? (see references/)

🛑 Checkpoint: State the surface type, primary/secondary principles, and cognitive-load assessment in one sentence. Do not proceed to Design until the audit is named.

Phase 2 — Design

- [ ] Choose 1-2 principles max for the surface (more = noise).
- [ ] Inject the leading word for the chosen principle into the copy.
- [ ] Apply the pattern for that principle (see references/principles.md).
- [ ] Verify the principle is real, not fabricated (real metrics, real
      testimonials, real scarcity).

🛑 Checkpoint: Show the chosen principle(s) and the planned copy structure. Do not draft prose until the design is named.

Phase 3 — Write

- [ ] Draft the copy anchored by the leading word.
- [ ] Use concrete metrics over vague adjectives ("3 missed calls last week"
      > "many missed calls").
- [ ] Run the read-aloud test — does it sound like a person, not a marketer?
- [ ] Run the ethical-influence test (see references/ethical_boundaries.md).

Phase 4 — Validate

- [ ] No dark patterns (fabricated stats, manufactured urgency, confirm-shaming,
      roach motel, bait-and-switch, asymmetric consent).
- [ ] No addiction design (infinite scroll without exit, variable reward
      exploitation).
- [ ] No product-truth overrides (claims must match what the feature actually
      does).
- [ ] Cognitive load reduced, not increased.
- [ ] Plain language — no marketing jargon the user would not use themselves.

Any miss → back to Phase 2.

What NOT to do

Hard boundaries — see references/ethical_boundaries.md for the full list and the ethical-influence test. Summary:

  • No fabricated stats. Real metrics only; if unknown, omit the figure.
  • No manufactured urgency. Real scarcity only — countdowns that reset are deception.
  • No confirm-shaming. Opt-out copy must be neutral.
  • No addiction design. Surfaces must serve the user's goal, not exploit dopamine response.
  • No overriding product truth. Copy must match what the feature actually does.

References

FileUse it for
references/principles.mdFull reasoning behind each cognitive bias + the Fogg Behavior Model
references/ethical_boundaries.mdDark patterns, addiction design, product-truth overrides, ethical-influence test
references/yappi_examples.mdWorked examples from the Yappi.ai context (the original skill's content)

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.