marketing-psychology
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,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.
66
58%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/marketing-psychology/SKILL.mdQuality
Discovery
89%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 is a well-structured description with excellent trigger term coverage and clear 'when to use' guidance. Its main weakness is that it describes the domain and resource (70+ mental models) rather than listing specific concrete actions the skill performs. Adding explicit action verbs describing what the skill does (e.g., 'identifies relevant cognitive biases for campaigns, maps persuasion frameworks to messaging') would strengthen it further.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Identifies relevant cognitive biases for campaigns, maps persuasion frameworks to messaging strategy, recommends behavioral nudges for conversion optimization.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (psychological principles applied to marketing) and mentions '70+ mental models organized for marketing application,' but does not list specific concrete actions like 'analyze consumer decisions,' 'apply cognitive biases to copy,' or 'map persuasion frameworks to campaigns.' | 2 / 3 |
Completeness | Clearly answers both 'what' (provides 70+ mental models organized for marketing application of psychological principles) and 'when' (explicit 'Use when' clause with specific trigger terms and use cases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' and 'consumer behavior' are all terms users would naturally use when seeking this kind of help. | 3 / 3 |
Distinctiveness Conflict Risk | The intersection of psychology/behavioral science with marketing is a clear niche. The specific trigger terms like 'cognitive bias,' 'mental models,' 'why people buy' are distinct enough to avoid conflicts with general marketing or general psychology skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a psychology textbook chapter dumped into a SKILL.md file. While the content is accurate and the marketing applications are relevant, it massively violates token efficiency by explaining concepts Claude already knows in detail. The lack of progressive disclosure means every invocation loads 400+ lines of reference material that should be split into separate files and referenced as needed.
Suggestions
Reduce SKILL.md to a concise overview with the quick reference table and task-specific questions, moving detailed model descriptions into separate reference files (e.g., `models/foundational.md`, `models/pricing.md`, `models/persuasion.md`).
Remove explanations of well-known concepts (Sunk Cost Fallacy, Pareto Principle, etc.) and focus only on the non-obvious marketing applications that Claude wouldn't generate on its own.
Add concrete, actionable templates or frameworks—e.g., a 'Psychology Audit Template' with specific questions to answer for a landing page, or a 'Pricing Page Checklist' with exact implementation steps.
Add a decision workflow: given a user's challenge, how to systematically select and apply 2-3 relevant models, with an example walkthrough showing input scenario → selected models → specific recommendations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This is extremely verbose at 400+ lines, cataloging 70+ mental models with explanations Claude already knows. Concepts like 'Sunk Cost Fallacy,' 'Pareto Principle,' and 'Anchoring Effect' are well within Claude's training data. The entire document could be reduced to the quick reference table plus a few novel, project-specific application patterns. | 1 / 3 |
Actionability | Each model includes a 'Marketing application' section with specific guidance, which is helpful. However, there are no executable code examples, no templates, no concrete deliverable formats, and the applications remain at the level of general advice rather than step-by-step implementation instructions. | 2 / 3 |
Workflow Clarity | The 'How to Use This Skill' section provides a 4-step process and the task-specific questions offer a diagnostic framework. However, there's no clear workflow for how to actually apply multiple models to a real scenario, no validation steps, and no decision tree for selecting which models to use beyond the reference table. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with all 70+ models inline. The content desperately needs to be split into separate reference files (e.g., pricing-psychology.md, persuasion-models.md) with SKILL.md serving as a concise overview and quick reference. The related skills section at the end is good but doesn't compensate for the massive inline content. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
2c6f6e8
- Reviewed
Table of Contents
Is this your skill?
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.