When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context.
71
44%
Does it follow best practices?
Impact
87%
1.11xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/marketing-psychology/SKILL.mdQuality
Discovery
54%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is heavily skewed toward trigger terms and 'when to use' guidance while almost entirely neglecting what the skill actually does. It has outstanding keyword coverage but fails to describe any concrete actions, outputs, or capabilities. A user or Claude selecting this skill would know when to pick it but not what it will deliver.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes marketing copy for cognitive biases, generates persuasion frameworks, recommends behavioral nudges for campaigns, and maps consumer decision-making patterns.'
Restructure to lead with a 'what it does' clause listing 3-5 specific capabilities before the 'Use when...' trigger guidance.
Use third-person active voice for capabilities (e.g., 'Applies cognitive bias frameworks to marketing strategy' rather than the current passive framing).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks concrete actions. It says 'apply psychological principles' and 'understand or leverage how people think' but never specifies what the skill actually does — no concrete outputs or actions like 'generates persuasion frameworks,' 'analyzes copy for cognitive biases,' or 'creates behavioral nudge strategies.' | 1 / 3 |
Completeness | The 'when' is thoroughly addressed with explicit trigger terms and use cases. However, the 'what' is extremely weak — it never explains what the skill concretely does or produces. The description is almost entirely trigger guidance with no capability description. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' and 'nudge.' These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The marketing psychology niche is somewhat specific, but the vague capability description ('apply psychological principles to marketing') could overlap with general marketing strategy skills, copywriting skills, or consumer research skills. The trigger terms help differentiate but the lack of concrete actions creates ambiguity. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like a psychology textbook rather than an actionable skill file. It spends the vast majority of its token budget explaining concepts Claude already knows (anchoring, social proof, loss aversion, etc.) with only brief, non-specific marketing application notes. The content would be far more effective as a concise decision-making framework with a quick reference table, linking to detailed examples in separate files.
Suggestions
Drastically reduce the body to a quick-reference table mapping challenges to models with 1-line application notes, moving detailed model descriptions to a separate REFERENCE.md file that can be consulted on demand.
Replace generic 'Marketing application' descriptions with concrete, executable examples: specific copy variations, A/B test setups, page layout recommendations, or template snippets that Claude can directly apply.
Add a clear decision workflow: given a user's marketing challenge, how should Claude select which 2-3 models to apply, in what order, and how to validate the approach (e.g., 'propose hypothesis → suggest A/B test → define success metric').
Remove explanations of well-known psychological concepts (sunk cost fallacy, confirmation bias, etc.) and focus tokens on novel application patterns, common mistakes, and ethical guardrails specific to this product/marketing context.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This is extremely verbose at 300+ lines, essentially a textbook of psychological concepts Claude already knows well. Nearly every entry explains basic psychology (e.g., what sunk cost fallacy is, what anchoring means) rather than providing novel, project-specific implementation guidance. The vast majority of tokens are spent on definitions Claude doesn't need. | 1 / 3 |
Actionability | Each model includes a 'Marketing application' line that gives directional guidance, but none provide executable code, specific templates, copy examples, or step-by-step implementation instructions. The applications are brief conceptual suggestions rather than concrete, copy-paste-ready artifacts. | 2 / 3 |
Workflow Clarity | The quick reference table and task-specific questions provide some structure for applying models to situations, and the initial 4-step process (identify, explain, apply, implement) gives a workflow. However, there are no validation checkpoints, no feedback loops for testing whether the applied psychology actually works, and no clear decision tree for selecting which models to use. | 2 / 3 |
Progressive Disclosure | The content is organized into logical sections with headers, and the Related Skills section provides cross-references. However, this is a monolithic wall of text that would benefit enormously from splitting detailed model descriptions into separate reference files, keeping only the quick reference table and high-level guidance in the main SKILL.md. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
2c7c108
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.