skills/emotional-stakes/SKILL.md
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).
npx skillsauth add axiomantic/spellbook emotional-stakesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| | 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 |
<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>
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" |
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.
Before completing stakes framing:
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>
testing
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).
development
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).
testing
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).
development
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.