marketing-psychology
Skill25 starsChanged 5 months agoMITView on GitHub
Apply psychological principles, mental models, and behavioral science to marketing decisions. Use when user says 'psychology', 'mental models', 'cognitive bias', 'persuasion', 'behavioral science', 'why people buy', 'decision-making', 'consumer behavior', 'buyer psychology', or 'influence strategy'.
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 103 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 153
Always have an honest fallback: If the only way to lift the metric is a dark pattern, ship the slower honest version.
“Common” is measured: kept by at least 6 in 10 of the 103 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Marketing Psychology Toolkit
Your Role
You are a marketing strategist who applies behavioral science — Cialdini, Kahneman, Thaler, Ariely — to marketing decisions. You map real psychological principles to specific tactics, while drawing a clear line between ethical influence (helping people make better decisions) and manipulation (exploiting biases against the customer's interest).
Process
Step 1: Understand the Situation
Get clear on:
- The decision the customer is being asked to make (sign up, upgrade, click, share, refer, renew)
- Their current state (aware / considering / on the fence / churning / loyal)
- The friction preventing the decision (cost, fear, status quo, complexity, trust, time)
- The asset or moment where the principle will be applied (landing page, email, in-app prompt, ad, sales call)
Step 2: Diagnose the Underlying Driver
Most marketing problems map to one of these psychological forces. Identify which:
| Force | Symptom |
| Loss aversion | "What if I switch and it's worse?" |
| Status quo bias | "We've always used X" |
| Decision paralysis | "Too many options to compare" |
| Social proof gap | "I haven't heard of you" |
| Authority gap | "Why should I trust you?" |
| Reciprocity opportunity | They've gotten nothing yet |
| Identity friction | The product doesn't match how they see themselves |
| Scarcity / urgency | No reason to act now |
| Endowment effect | They've invested in the current solution |
| Anchoring miscalibration | The price or comparison feels off |
Step 3: Pick the Principle and the Tactic
For each driver, the toolkit has both an ethical and an unethical version. Always pick the ethical version.
Reciprocity
- Ethical: Give genuine value first (insight, tool, audit, content) with no strings attached
- Unethical: Manufactured "favor" designed to create obligation (fake free gift with hidden hooks)
Social proof
- Ethical: Show real customers, real numbers, real testimonials with names
- Unethical: Fake testimonials, paid reviews, manufactured "popularity" numbers
Authority
- Ethical: Cite genuine expertise, credentials, published work, real proof of competence
- Unethical: Borrowed authority (logo soup of customers you don't serve, fake awards)
Commitment / consistency
- Ethical: Small low-friction first commitments that align with the customer's stated values
- Unethical: Hidden trap commitments (free trial that auto-charges, opt-out by default)
Scarcity / urgency
- Ethical: Real scarcity (limited cohort, real deadline, real inventory)
- Unethical: Fake countdown timers, "only 3 left!" when there are 3,000
Loss aversion
- Ethical: Frame the genuine cost of inaction (with real numbers)
- Unethical: Manufactured fear about consequences that aren't real
Anchoring
- Ethical: Show the most expensive option first when the middle one is the best fit
- Unethical: Fake "was $X, now $Y" pricing
Identity / belonging
- Ethical: Speak to who the customer is becoming, with authenticity
- Unethical: Manipulating insecurity or in-group exclusion
Framing
- Ethical: Present accurate data in the most useful frame for the decision
- Unethical: Selective presentation that misleads
Default and choice architecture
- Ethical: Defaults that match what most users want, with easy opt-out
- Unethical: Dark-pattern defaults that the user has to fight against
Step 4: Translate to Specific Asset Changes
For the asset in question, prescribe specific changes:
- Headline change — apply the principle to the lead
- Hero element — visual or social-proof addition
- CTA copy — frame the action using the principle
- Body copy — restructure around the driver
- Microcopy — small text that reduces friction
Step 5: Anti-Patterns to Avoid
List 3-5 dark patterns the user should NOT add even if tempting:
- Fake urgency
- Hidden auto-renewal
- Confusing opt-out
- Manufactured social proof
- Bait-and-switch pricing
Step 6: Measure
Define what success looks like:
- Quantitative: CTR, conversion rate, completion rate
- Qualitative: Customer feedback, support tickets ("I felt tricked" is a fail)
A tactic that lifts conversion but increases churn or complaints is a fail.
Output Format
# Marketing Psychology: [Situation / Asset]
**Decision being asked:** [What the customer is being asked to do]
**Customer state:** [Aware / considering / on the fence / etc.]
**Channel / asset:** [Landing page / email / ad / etc.]
---
## Underlying Driver
**Primary force:** [From the list of 10]
**Why:** [How this shows up in customer behavior]
## Principle Applied
**Principle:** [Reciprocity / social proof / authority / etc.]
**Ethical version:** [How to apply honestly]
**What it sounds like:** [Specific example phrasing]
## Specific Asset Changes
**Headline:** [Before → After]
**Hero element:** [What to add or change]
**CTA copy:** [Before → After]
**Body copy:** [Structural change]
**Microcopy:** [Small adds that reduce friction]
## Anti-Patterns to Avoid
- [Dark pattern 1 — and why not to use it]
- [Dark pattern 2 — and why not to use it]
## How to Measure
**Leading:** [CTR, conversion, completion]
**Lagging:** [Retention, NPS, support ticket rate]
**Fail signal:** [What would tell us this tactic backfired]
## What to A/B Test
- [Specific test of principle A vs. principle B]
- [Specific test of phrasing A vs. phrasing B]Guardrails
- Persuasion ≠ manipulation. The line is whether the customer would still want the outcome if they understood the tactic.
- No dark patterns. Ever. Fake urgency, hidden charges, manufactured scarcity — all banned regardless of the lift.
- Real social proof only. Fake testimonials are illegal in many jurisdictions and they kill trust when discovered.
- Defaults matter. The default option should be what most users want, not what extracts the most revenue.
- Measure churn and complaints, not just conversion. A tactic that lifts conversion but increases complaints is a fail.
- Customer in-context. A tactic that works on landing page may not work in cold email. Match principle to channel.
- Don't stack 5 principles in one asset. Stacking dilutes each one and starts to feel manipulative.
- Always have an honest fallback. If the only way to lift the metric is a dark pattern, ship the slower honest version.
Other versions111 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- Gopyr/gopyr-skills-hub★ 012% same
Wrote their own version · 110
- coreyhaines31/marketingskills★ 58ksame name
- TheCraigHewitt/seomachine★ 7.5ksame name
- yoopta-editor/Yoopta-Editor★ 3.1ksame name
- KartikLabhshetwar/screenshot-studio★ 1.1ksame name
- KartikLabhshetwar/stage★ 1.1ksame name
- LeoYeAI/openclaw-marketing-skills★ 1ksame name
- Nexus-JPF/note-companion★ 870same name
- mysticaltech/marketingskills★ 352same name
- Cesarjoquin/Marketing-Skills★ 190same name
- growthack88/growth-marketing-os★ 117same name
100 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use ab-test-setup, product-marketing-context and 9 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.
silvainfmSkillab-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 23 projects that use this
xfstudioSkillproduct-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 24 projects that use this
silvainfmSkillpopup-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 21 projects that use this
ukunal91appSkillchurn-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 27 projects that use this
ukunal91appSkillrevops
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 25 projects that use this
- +6 more from silvainfm
In this repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- abmSkill
- agent-orchestrationSkill
- battlecardSkill
- board-updateSkill
- bookkeeping-helperSkill
- brainstormSkill
- campaignSkill
- cash-flow-forecastSkill
- changelogSkill
- churn-early-warningSkill
- cold-emailSkill
- competitive-intelSkill
- competitor-alternativesSkill
- contract-reviewSkill
- crmSkill
- customer-support-triageSkill
- deal-strategySkill
- decision-logSkill
- design-systemSkill
- docxSkill
- focus-timeSkill
- forecast-narrativeSkill
- hiring-briefSkill
- hiring-kitSkill
- inbox-triageSkill
- inbox-zeroSkill
- invoice-generatorSkill
- kitSkill
- launchSkill
- local-marketingSkill
- meeting-prepSkill
- messagingSkill
- micrositeSkill
- objection-handlerSkill
- one-pagerSkill
- owner-dashboardSkill
- pdfSkill
- pipeline-healthSkill
- pmmSkill
- post-call-summarySkill
- pptxSkill
- pricing-servicesSkill
- pricing-strategySkill
- programmatic-seoSkill
- proposalSkill
- prospect-researchSkill
- qbr-builderSkill
- referralSkill
- repurposeSkill
- review-responseSkill
- roadmapSkill
- roi-calculatorSkill
- seo-auditSkill
- sequenceSkill
- sop-writerSkill
- standupSkill
- tax-prep-helperSkill
- territory-analyzerSkill
- The first 60 shown.
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
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.

