Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Emotional Stakes Mapping

ASecurity

Maps what each stakeholder actually cares about underneath their stated position — because addressing the stated position while missing the real stake accomplishes nothing. TRIGGERS: 'what do they actually want', 'underlying stakes', 'what's really at stake', 'beneath the position', 'why won't they agree'.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgoapi

Works with

api

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill emotional-stakes-mapping --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Emotional Stakes Mapping?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Emotional Stakes Mapping
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-emotional-stakes-mapping/badge)](https://www.skillsdirectory.com/skills/rondoflow-emotional-stakes-mapping)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: emotional-stakes-mapping
description: "Maps what each stakeholder actually cares about underneath their stated position — because addressing the stated position while missing the real stake accomplishes nothing. TRIGGERS: 'what do they actually want', 'underlying stakes', 'what's really at stake', 'beneath the position', 'why won't they agree'."
---

# Emotional Stakes Mapping

People argue about positions. They care about stakes. Addressing the stated position
while missing the real stake is the most common reason negotiations, decisions, and
alignment efforts fail. This skill maps the gap between the two — not by guessing,
but by working systematically through what each party stands to lose if the outcome
goes against them.

---

## Your Process

**Step 1: List Stakeholders**
Identify every party with a meaningful stake in the outcome — including silent ones
who will be affected but aren't in the room. Passive non-participants often have the
highest stakes; they just have no forum to name them.

**Framing check:** Confirm the specific situation and its stakeholders before continuing. State what you've identified — the actual conflict or decision being mapped and the parties involved — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the situation, the core tension, and the parties involved]. Is that right?"
- **Header:** "Framing"
- **Options:**
  - **Yes — proceed** — framing is correct
  - **Adjust** — one element is off; user will correct it before you continue
  - **Reframe** — different situation than read; incorporate the correction before proceeding

**Step 2: Stated Position**
What is each stakeholder explicitly asking for, pushing toward, or resisting? Keep
this behaviorally specific — "they want sign-off authority" not "they want control."
Surface the precise ask.

**Step 3: Real Fear**
What are they actually afraid of losing? Common real fears: status within their
organisation, control over resources they currently hold, credit for outcomes they've
invested in, relevance if the change makes their expertise obsolete, relationships
that depend on the current arrangement, safety from blame if things go wrong. Fears
drive positions — find the fear beneath the ask.

**Step 4: Minimum Conditions for Agreement**
What would need to be true — not just what would help, but what is the floor — for
each stakeholder to feel safe enough to say yes? The minimum condition is often
surprisingly specific once the real fear is named: "I need to be cited as a
contributor" or "I need a fallback option if this fails."

**Step 5: Face-Saving Explanation**
How would they explain agreement to their team, their boss, or themselves? A
stakeholder may privately accept a compromise but publicly need a narrative that
doesn't look like capitulation. Agreement that can't be explained is agreement that
won't hold — or won't be delivered.

**Step 6: Map Alignment and Conflict Zones**
Find where underlying stakes actually overlap (alignment zones) and where they
genuinely compete (conflict zones). Alignment at the stake level often exists even
when surface positions look completely opposed. Conflict zones where one party's win
structurally requires another's loss cannot be resolved through reframing — they
require explicit negotiation.

---

## Human Check-in

Before proceeding, use the `AskUserQuestion` tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:

- **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?"
- **Header:** "Scope"
- **Options:**
  - **Full analysis** — Complete all steps, reasoning shown throughout
  - **Key findings only** — Bottom-line output, skip step-by-step detail
  - **Highest stakes only** — What each person cares about most, skip secondary concerns
  - **Reframe** — The read is off; correct it and the analysis will follow the corrected framing

Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.

## Output Format

**Stakeholder Table**

| Stakeholder | Stated Position | Real Fear | Minimum Condition | Face-Saving Explanation |
|---|---|---|---|---|
| [name/role] | [explicit ask] | [underlying fear] | [the floor for agreement] | [how they'd narrate agreement] |

**Alignment Zones**
Stakes that multiple stakeholders share underneath apparently conflicting positions.
List the shared underlying interest and which parties share it.

**Conflict Zones**
Stakes that genuinely compete — where one party's win requires another's loss. Name
each conflict zone explicitly and identify what explicit negotiation or trade-off it
requires.

**Next Move**
Given the alignment and conflict zones: what is the highest-leverage first
conversation or action?

---

## Notes

Surface-level positions are negotiating stances; underlying stakes are the actual
terrain. Work on the terrain. Conflict zones that can't be resolved through alignment
require explicit trade-off decisions — don't paper over them with language that
pretends everyone wins when they don't. The face-saving explanation step is often
what makes agreement stick in practice even after it's been reached in principle.

---

## What's Next

After delivering this output, use `AskUserQuestion` to offer the next move:

- **Question:** "Stakes mapped. What's next?"
- **Header:** "Next"
- **Options:**
  - `/decision-premortem-analysis` — Stress-test with highest-stakes outcomes in mind
  - `/ethics-empathy-circle` — Apply structured empathy to the highest-stakes people
  - `/communication-audience-modeling` — Model the audience through their stakes
  - **Done** — Wrap up and synthesise what we have so far

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →