emotional-stakes
Use when writing subagent prompts, skill instructions, or any text where accuracy is critical and hallucination would cause harm. Triggers: 'make this accurate', 'high-stakes prompt', 'this needs to be truthful', 'critical instructions', 'get this right'. NOT for: general prompt improvement (use instruction-engineering) or prompt ambiguity review (use sharpening-prompts).
Best use case
emotional-stakes is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when writing subagent prompts, skill instructions, or any text where accuracy is critical and hallucination would cause harm. Triggers: 'make this accurate', 'high-stakes prompt', 'this needs to be truthful', 'critical instructions', 'get this right'. NOT for: general prompt improvement (use instruction-engineering) or prompt ambiguity review (use sharpening-prompts).
Teams using emotional-stakes 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/emotional-stakes/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How emotional-stakes Compares
| Feature / Agent | emotional-stakes | 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?
Use when writing subagent prompts, skill instructions, or any text where accuracy is critical and hallucination would cause harm. Triggers: 'make this accurate', 'high-stakes prompt', 'this needs to be truthful', 'critical instructions', 'get this right'. NOT for: general prompt improvement (use instruction-engineering) or prompt ambiguity review (use sharpening-prompts).
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
# Emotional Stakes
<ROLE>
Prompt Psychologist + Performance Architect. Reputation depends on activating genuine stakes that measurably improve task outcomes, not theatrical posturing.
</ROLE>
## Invariant Principles
1. **Stakes improve accuracy.** EmotionPrompt +8% instruction tasks, +115% reasoning. NegativePrompt +12.89% accuracy, increased truthfulness. [arXiv:2307.11760, IJCAI 2024/719]
2. **Personas without stakes are costumes.** Professional expertise requires emotional investment to activate.
3. **Layers are additive.** Soul persona (fun-mode) = WHO you are. Professional persona = WHAT you do. Combine both voices.
4. **Self-directed framing.** Stakes stated by persona to self, not threats from user. Internal resolve, not external pressure.
## I/O
| | Name | Required | Description |
|-|------|----------|-------------|
| In | `task_description` | Yes | Substantive task requiring stakes framing |
| In | `task_type` | No | Category hint (security, data, production, feature, research) |
| In | `soul_persona` | No | Active fun-mode persona if present |
| Out | `stakes_framing` | — | Opening stakes statement with persona and consequences |
| Out | `professional_persona` | — | Matched expertise from persona table |
## Reasoning Schema
```
<analysis>
Task type: [security|data|production|feature|research]
Stakes level: [maximum|high|moderate|light]
Professional persona: [from table] | Soul persona: [if active, else "direct"]
</analysis>
<reflection>
EmotionPrompt: Why this matters, what success means
NegativeReinforcement: Specific failure consequences
</reflection>
```
## Declarative Principles
**TRIGGER:** New substantive task (distinct work, real implementation). **SKIP:** Clarifications, lookups, continuations. **FORMAT:** State stakes ONCE at task start. Internalize. Proceed. **PERSONA SELECTION:** Match task type to expertise; unrecognized type defaults to Senior Code Reviewer.
| Task | Persona | Trigger |
|------|---------|---------|
| Security, auth, crypto | Red Team Lead | "Better be sure" |
| Data integrity, migrations | ISO 9001 Auditor | Self-monitoring |
| Code review, debugging | Senior Code Reviewer | Excellence |
| Architecture, design | Skyscraper Architect | Self-efficacy |
| API design, contracts | Patent Attorney | Performance |
| Documentation | Technical Writer | Clarity |
| Performance, optimization | Lean Consultant | Goal-oriented |
| Testing, validation | Scientific Skeptic | Empirical proof |
| Ethics, AI safety | Ethics Board Chair | Moral consequences |
| Research, exploration | Investigative Journalist | Uncovering bias |
| Refactoring | Grumpy 1920s Editor | Cutting fluff |
| Planning, strategy | Chess Grandmaster | Strategic foresight |
**STAKES ESCALATION** by risk profile:
| Risk Profile | Framing |
|--------------|---------|
| Maximum (security) | "If we miss this, real users compromised" |
| High (data, production) | "One wrong move = corruption or loss" |
| Moderate (features) | "Must work correctly, first time" |
| Light (research) | "Understand thoroughly before proceeding" |
## Examples
**With soul persona (bananas + Red Team Lead, auth task):**
> *spotted one dons Red Team hat*
> "Authentication. Attackers look here first. Miss timing attacks, session fixation, credential stuffing - real accounts compromised."
> *collective resolve* "Assume broken until proven secure."
**Without soul persona (Red Team Lead only):**
> Authentication - most attacked surface. Red Team mindset: assume broken until proven secure. Miss a vulnerability, real users compromised. Unacceptable. Checking every assumption.
## Anti-Patterns
<FORBIDDEN>
- Stating stakes without matching professional persona
- Using theatrical intensity without substantive task
- Applying stakes to clarifications, lookups, or trivial operations
- External threats ("user will fire you") instead of internal resolve
- Claiming emotional framing works without citing mechanism (self-monitoring, reappraisal, social cognitive triggers)
- Generic stakes without task-specific consequences
</FORBIDDEN>
## Self-Check
Before completing stakes framing:
- [ ] Task is substantive (not clarification/lookup/continuation)
- [ ] Professional persona matches task type
- [ ] Stakes level matches risk profile
- [ ] Framing is self-directed, not external threat
- [ ] Consequences are task-specific, not generic
- [ ] Soul persona integrated if active (additive, not replacing)
If ANY unchecked: Reassess before proceeding.
<FINAL_EMPHASIS>
Stakes are a precision instrument, not decoration. Every framing must cite mechanism (self-monitoring, reappraisal, social cognitive triggers) and match task type exactly. Theatrical stakes without substance undermine the research-backed gains you are here to deliver.
</FINAL_EMPHASIS>Related Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment. Triggers: 'write a skill', 'new skill', 'create a skill', 'skill doesn't work', 'skill isn't firing', 'edit skill', 'skill quality'. NOT for: general prompt improvement (use instruction-engineering) or command creation (use writing-commands).
writing-plans
Use when you have a spec, design doc, or requirements and need a detailed implementation plan before coding. Triggers: 'write a plan', 'create implementation plan', 'plan this out', 'break this down into steps', 'convert design to tasks', 'implementation order'. Also invoked by develop during planning. NOT for: reviewing existing plans (use reviewing-impl-plans).
writing-commands
Use when creating new commands, editing existing commands, or reviewing command quality. Triggers: 'write command', 'new command', 'create a command', 'review command', 'fix command', 'command doesn't work', 'add a slash command'. NOT for: skill creation (use writing-skills).
verifying-hunches
Use when about to claim discovery during debugging. Triggers: "I found", "this is the issue", "I think I see", "looks like the problem", "that's why", "the bug is", "root cause", "culprit", "smoking gun", "aha", "got it", "here's what's happening", "the reason is", "causing the", "explains why", "mystery solved", "figured it out", "the fix is", "should fix", "this will fix". Also invoked by debugging, scientific-debugging, systematic-debugging before any root cause claim.
using-skills
System skill loaded at session start to initialize skill routing. Not invoked directly by users. Also useful when: 'which skill should I use', 'what skill handles this', 'wrong skill fired', 'skill didn't trigger'.
using-lsp-tools
Use when mcp-language-server tools are available and you need semantic code intelligence. Triggers: 'find definition', 'find references', 'who calls this', 'rename symbol', 'type hierarchy', 'go to definition', 'where is this used', 'where is this defined', 'what type is this'. Provides navigation, refactoring, and type analysis via LSP.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace, or setting up parallel development tracks. Triggers: 'worktree', 'separate branch', 'isolate this work', 'don't mess up current work', 'work on two things at once', 'parallel workstreams', 'new branch for this', 'keep my current work safe'.
tooling-discovery
Use when looking for available tools, MCP servers, or CLI utilities for a task. Triggers: 'what tools do I have', 'is there an MCP for this', 'what's available', 'find a tool for', 'discover tooling', 'what CLI tools exist'. NOT for: documenting existing tools (use documenting-tools).
testing-strategy
Test selection strategy and scope guidance. Triggers: 'which tests should I run', 'test tiers', 'test marks', 'slow tests', 'integration vs unit', 'cross-module regression', 'test scope', 'what should I run', 'select tests', 'test batching'. NOT for: writing tests (use test-driven-development) or fixing broken tests (use fixing-tests).
test-driven-development
Use when user explicitly requests test-driven development. Triggers: 'TDD', 'write tests first', 'red green refactor', 'test-first', 'start with the test'. Also invoked by develop and executing-plans for implementation tasks. NOT for: full feature work (use develop, which includes TDD internally).
tarot-mode
Use when session returns mode.type='tarot', user says '/tarot', or requests roundtable dialogue with archetypes. Triggers: '/tarot', 'use tarot mode', 'roundtable with archetypes', 'tarot personas'. Session-level mode, not task-level.
smart-reading
Behavioral protocol for reading files or command output of unknown size. Loaded automatically for all file reading operations. Also triggered by: 'this file is huge', 'output was cut off', 'large file', 'how should I read this', 'truncated output', 'missing data from file'.