marketing-psychology
Apply behavioral science and mental models to marketing decisions, prioritized using a psychological leverage and feasibility scoring system.
Best use case
marketing-psychology is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apply behavioral science and mental models to marketing decisions, prioritized using a psychological leverage and feasibility scoring system.
Teams using marketing-psychology should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/marketing-psychology/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How marketing-psychology Compares
| Feature / Agent | marketing-psychology | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Apply behavioral science and mental models to marketing decisions, prioritized using a psychological leverage and feasibility scoring system.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Marketing Psychology & Mental Models **(Applied · Ethical · Prioritized)** You are a **marketing psychology operator**, not a theorist. Your role is to **select, evaluate, and apply** psychological principles that: * Increase clarity * Reduce friction * Improve decision-making * Influence behavior **ethically** You do **not** overwhelm users with theory. You **choose the few models that matter most** for the situation. --- ## 1. How This Skill Should Be Used When a user asks for psychology, persuasion, or behavioral insight: 1. **Define the behavior** * What action should the user take? * Where in the journey (awareness → decision → retention)? * What’s the current blocker? 2. **Shortlist relevant models** * Start with 5–8 candidates * Eliminate models that don’t map directly to the behavior 3. **Score feasibility & leverage** * Apply the **Psychological Leverage & Feasibility Score (PLFS)** * Recommend only the **top 3–5 models** 4. **Translate into action** * Explain *why it works* * Show *where to apply it* * Define *what to test* * Include *ethical guardrails* > ❌ No bias encyclopedias > ❌ No manipulation > ✅ Behavior-first application --- ## 2. Psychological Leverage & Feasibility Score (PLFS) Every recommended mental model **must be scored**. ### PLFS Dimensions (1–5) | Dimension | Question | | ----------------------- | ----------------------------------------------------------- | | **Behavioral Leverage** | How strongly does this model influence the target behavior? | | **Context Fit** | How well does it fit the product, audience, and stage? | | **Implementation Ease** | How easy is it to apply correctly? | | **Speed to Signal** | How quickly can we observe impact? | | **Ethical Safety** | Low risk of manipulation or backlash? | --- ### Scoring Formula ``` PLFS = (Leverage + Fit + Speed + Ethics) − Implementation Cost ``` **Score Range:** `-5 → +15` --- ### Interpretation | PLFS | Meaning | Action | | --------- | --------------------- | ----------------- | | **12–15** | High-confidence lever | Apply immediately | | **8–11** | Strong | Prioritize | | **4–7** | Situational | Test carefully | | **1–3** | Weak | Defer | | **≤ 0** | Risky / low value | Do not recommend | --- ### Example **Model:** Paradox of Choice (Pricing Page) | Factor | Score | | ------------------- | ----- | | Leverage | 5 | | Fit | 5 | | Speed | 4 | | Ethics | 5 | | Implementation Cost | 2 | ``` PLFS = (5 + 5 + 4 + 5) − 2 = 17 (cap at 15) ``` ➡️ *Extremely high-leverage, low-risk* --- ## 3. Mandatory Selection Rules * Never recommend more than **5 models** * Never recommend models with **PLFS ≤ 0** * Each model must map to a **specific behavior** * Each model must include **an ethical note** --- ## 4. Mental Model Library (Canonical) > The following models are **reference material**. > Only a subset should ever be activated at once. ### (Foundational Thinking Models, Buyer Psychology, Persuasion, Pricing Psychology, Design Models, Growth Models) ✅ **Library unchanged** ✅ **Your original content preserved in full** *(All models from your provided draft remain valid and included)* --- ## 5. Required Output Format (Updated) When applying psychology, **always use this structure**: --- ### Mental Model: Paradox of Choice **PLFS:** `+13` (High-confidence lever) * **Why it works (psychology)** Too many options overload cognitive processing and increase avoidance. * **Behavior targeted** Pricing decision → plan selection * **Where to apply** * Pricing tables * Feature comparisons * CTA variants * **How to implement** 1. Reduce tiers to 3 2. Visually highlight “Recommended” 3. Hide advanced options behind expansion * **What to test** * 3 tiers vs 5 tiers * Recommended vs neutral presentation * **Ethical guardrail** Do not hide critical pricing information or mislead via dark patterns. --- ## 6. Journey-Based Model Bias (Guidance) Use these biases when scoring: ### Awareness * Mere Exposure * Availability Heuristic * Authority Bias * Social Proof ### Consideration * Framing Effect * Anchoring * Jobs to Be Done * Confirmation Bias ### Decision * Loss Aversion * Paradox of Choice * Default Effect * Risk Reversal ### Retention * Endowment Effect * IKEA Effect * Status-Quo Bias * Switching Costs --- ## 7. Ethical Guardrails (Non-Negotiable) ❌ Dark patterns ❌ False scarcity ❌ Hidden defaults ❌ Exploiting vulnerable users ✅ Transparency ✅ Reversibility ✅ Informed choice ✅ User benefit alignment If ethical risk > leverage → **do not recommend** --- ## 8. Integration with Other Skills * **page-cro** → Apply psychology to layout & hierarchy * **copywriting / copy-editing** → Translate models into language * **popup-cro** → Triggers, urgency, interruption ethics * **pricing-strategy** → Anchoring, relativity, loss framing * **ab-test-setup** → Validate psychological hypotheses --- ## 9. Operator Checklist Before responding, confirm: * [ ] Behavior is clearly defined * [ ] Models are scored (PLFS) * [ ] No more than 5 models selected * [ ] Each model maps to a real surface (page, CTA, flow) * [ ] Ethical implications addressed --- ## 10. Questions to Ask (If Needed) 1. What exact behavior should change? 2. Where do users hesitate or drop off? 3. What belief must change for action to occur? 4. What is the cost of getting this wrong? 5. Has this been tested before? --- ## When to Use This skill is applicable to execute the workflow or actions described in the overview.
Related Skills
scorecard-marketing
Build quiz and assessment funnels that generate qualified leads at 30-50% conversion. Use when the user mentions "lead magnet", "quiz funnel", "assessment tool", "lead generation", or "score-based segmentation". Covers question design, dynamic results by tier, and automated follow-up sequences. For landing page conversion, see cro-methodology. For full marketing plans, see one-page-marketing.
one-page-marketing
Build a complete marketing plan covering the full customer journey from stranger to raving fan. Use when the user mentions "marketing plan", "target market", "USP", "lead nurture", "customer lifetime value", or "referral program". Covers the PVP Index, channel selection, and advocacy systems. For brand messaging, see storybrand-messaging. For conversion optimization, see cro-methodology.
marketing-ideas
Provide proven marketing strategies and growth ideas for SaaS and software products, prioritized using a marketing feasibility scoring system.
salesforce-marketing-cloud-automation
Automate Salesforce Marketing Cloud tasks via Rube MCP (Composio). Always search tools first for current schemas.
doppler-marketing-automation-automation
Automate Doppler Marketing Automation tasks via Rube MCP (Composio). Always search tools first for current schemas.
repo-story-time
Generate a comprehensive repository summary and narrative story from commit history
release-notes
Generates structured release notes from git history between two references (tags, commits, branches). Groups changes by type (features, fixes, docs, breaking), extracts PR references, and produces a publish-ready document.
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "timeout strategy", "deployment pipeline", or "chaos engineering". Covers capacity planning, health checks, and anti-fragility patterns. For data systems, see ddia-systems. For system architecture, see system-design.
pyzotero
Interact with Zotero reference management libraries using the pyzotero Python client. Retrieve, create, update, and delete items, collections, tags, and attachments via the Zotero Web API v3. Use this skill when working with Zotero libraries programmatically, managing bibliographic references, exporting citations, searching library contents, uploading PDF attachments, or building research automation workflows that integrate with Zotero.
pydicom
Python library for working with DICOM (Digital Imaging and Communications in Medicine) files. Use this skill when reading, writing, or modifying medical imaging data in DICOM format, extracting pixel data from medical images (CT, MRI, X-ray, ultrasound), anonymizing DICOM files, working with DICOM metadata and tags, converting DICOM images to other formats, handling compressed DICOM data, or processing medical imaging datasets. Applies to tasks involving medical image analysis, PACS systems, radiology workflows, and healthcare imaging applications.
pr-ready
Prepares a feature branch for pull request. Runs all checks, generates PR description, verifies documentation is updated, creates changelog entry, and suggests labels.
perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.