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 Resistance Diagnosis

ASecurity

Diagnoses why people are resisting — finding what's underneath the pushback. Resistance is information, not obstruction; it always has a source. TRIGGERS: 'why are they resisting', 'diagnose the pushback', 'they won't get on board', 'people aren't buying in', 'resistance diagnosis'.

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

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill emotional-resistance-diagnosis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Emotional Resistance Diagnosis?

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

Security grade badge for Emotional Resistance Diagnosis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-emotional-resistance-diagnosis/badge)](https://www.skillsdirectory.com/skills/rondoflow-emotional-resistance-diagnosis)

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

Download with Pro
Files
SKILL.md
---
name: emotional-resistance-diagnosis
description: "Diagnoses why people are resisting — finding what's underneath the pushback. Resistance is information, not obstruction; it always has a source. TRIGGERS: 'why are they resisting', 'diagnose the pushback', 'they won't get on board', 'people aren't buying in', 'resistance diagnosis'."
---

# Emotional Resistance Diagnosis

Resistance is not a problem to overcome — it is a signal to decode. People resist for
different reasons, and applying the wrong response to the wrong type makes it worse.
Presenting more data to someone who is emotionally resistant does nothing. Acknowledging
feelings with someone who has an intellectual objection is patronising. This skill
identifies the source before prescribing the response.

---

## Your Process

**Step 1: Describe the Resistance**
Who is resisting, what are they saying explicitly, and how are they behaving?
Get behaviorally specific — passive non-compliance, vocal objection, questions
designed to slow things down, and political manoeuvring are different signals
pointing to different sources.

**Framing check:** Confirm the specific resistance situation before continuing. State who is resisting, what they appear to be resisting, and in what context, in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of who is resisting, what they're resisting, and in what context]. 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: Classify Each Instance**
Assign each type of resistance to one or more of these categories:
- **Intellectual** — they disagree with the reasoning, evidence, or conclusion.
  They think you're wrong.
- **Emotional** — they feel something important to them is at risk. They may not
  be able to articulate what, but something feels threatening.
- **Political** — a competing interest is served by the current state. Changing
  things costs them something real.
- **Practical** — they don't believe the plan can actually work. They've seen
  similar things tried and fail.

**Step 3: Source of Each Type**
Dig to the specific source. Intellectual: which claim do they reject, and why?
Emotional: what are they afraid of losing — status, security, relationships,
credit? Political: whose interests benefit from the status quo, and how do they
intersect with this person? Practical: what specifically do they believe will
fail, and what informs that belief?

**Step 4: What Are They Legitimately Protecting?**
Most resistance protects something real — a working system, a relationship, a
principle, an investment of time and reputation. Name it explicitly. Even if their
expression of resistance is unhelpful, the thing they're protecting may be
legitimate. Dismissing this hardens resistance into permanent opposition.

**Step 5: What Would Reduce Each Type?**
Each type has a different lever. Intellectual resistance needs evidence, logic,
or acknowledgment that their counter-argument was considered. Emotional needs
acknowledgment of the risk they feel and credible reassurance. Political needs
negotiation or incentive realignment. Practical needs proof of concept or a staged
rollout that limits downside.

**Step 6: Engagement vs Clarity**
Some resistance requires genuine engagement — changing the plan, negotiating
trade-offs, addressing real concerns with merit. Some requires clarity — the plan
isn't actually what they think it is, and better communication resolves it.
Distinguish these before acting.

---

## 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
  - **Resistance source only** — What's actually causing the resistance, skip the implications
  - **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

**Resistance Diagnosis**

| Resistance | Type | Source | What They're Legitimately Protecting | What Reduces It | Engage or Clarify? |
|---|---|---|---|---|---|
| [description] | [type] | [root cause] | [legitimate interest] | [lever] | [engage/clarify] |

**Engagement Priority**
Which resistance requires the most substantive response first, and why. Name the
one thing that, if addressed well, would most shift the overall dynamic.

---

## Notes

The worst response to resistance is to push harder. The best is to correctly
classify it first — then respond to the actual type. Treating emotional resistance
as intellectual (presenting more data) is a common and costly mistake. Treating
political resistance as emotional (offering reassurance) is equally ineffective.
Classification is the work.

---

## What's Next

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

- **Question:** "Resistance diagnosed. What's next?"
- **Header:** "Next"
- **Options:**
  - `/emotional-trust-audit` — Assess whether trust issues are fuelling the resistance
  - `/communication-objection-mapping` — Map objections rooted in the resistance
  - `/strategy-alliance` — Build alliances to reduce or bypass the resistance
  - **Done** — Wrap up and synthesise what we have so far

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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', ...

693621 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 →