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

Play Perspective Reversal

ASecurity

Fully inhabits the opposing perspective — competitor, critic, user, or adversary — to find what is invisible from your own position. TRIGGERS: 'steelman the opposition', 'think like the competitor', 'play devil's advocate', 'see it from their side', 'role reversal', 'inhabit the other perspective'.

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

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill play-perspective-reversal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Play Perspective Reversal?

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

Security grade badge for Play Perspective Reversal
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-play-perspective-reversal/badge)](https://www.skillsdirectory.com/skills/rondoflow-play-perspective-reversal)

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

Download with Pro
Files
SKILL.md
---
name: play-perspective-reversal
description: "Fully inhabits the opposing perspective — competitor, critic, user, or adversary — to find what is invisible from your own position. TRIGGERS: 'steelman the opposition', 'think like the competitor', 'play devil's advocate', 'see it from their side', 'role reversal', 'inhabit the other perspective'."
---

# Play: Perspective Reversal

Every position has a blind spot — things that are invisible precisely because of
where you're standing. The opposing perspective sees those things clearly. This skill
requires fully setting aside your own position and genuinely inhabiting the other one
— without qualification, defence, or commentary — then returning to extract what was
revealed. Half-hearted perspective-taking (staying in your own frame while gesturing
at theirs) produces nothing. Full inhabitation produces findings.

---

## Your Process

**Step 1: Name the Opposing Perspective**
Who is the other position? Be specific — not "the market" but "a direct competitor
who has observed our strategy for two years and is now choosing where to attack." Not
"critics" but "the engineering team who built the previous system and believe this
replacement is solving the wrong problem." Specificity determines how much you can
genuinely inhabit.

**Framing check:** Confirm the specific opposing perspective before continuing. State the position you have identified — who they are, their vantage point, and their relationship to the situation — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the opposing perspective and their vantage point]. 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 perspective than read; incorporate the correction before proceeding

**Step 2: Set Aside Your Own Perspective**
This step is non-negotiable. For the duration of Steps 3-5, there is no defending,
no qualifying, no "but to be fair to our side." You are not you. You are them. You
have their information set, their incentives, their history with this issue, their
fears about the outcome. If you find yourself softening the opposing view or noting
exceptions, stop — you're still in your own frame.

**Step 3: From Their Perspective — What Is Wrong?**
What is wrong with the current approach, plan, or position? What is being missed,
underestimated, or misunderstood? What assumptions look clearly false from this
vantage point? What would a perceptive person standing here see that the other side
is blind to?

**Step 4: What Opportunity Are They Seeing?**
From their position: what opportunity exists that the current approach is failing to
take? What gap, weakness, or opening is visible from where they stand? What is the
version of the world they're operating from where their strategy makes complete sense?

**Step 5: Their Strategy**
If you were them, what would you do? What specific moves would you make to exploit
what you've just identified? Be concrete — not "they'll attack our weakness" but the
specific sequence of moves that their position makes available.

**Step 6: Re-enter and Assess**
Return to your own perspective. What did the opposing view reveal that is legitimate
— that you would have to concede is a real problem even under your own framework?
Classify each finding: must change (the critique is valid and the approach needs
adjustment), must defend (the approach is correct but vulnerable), must communicate
better (the approach is right but it's not landing).

---

## 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
  - **Opposing view only** — Fully inhabit the opposite position, skip the reflection and re-integration
  - **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

**Opposing Perspective:** [who + their vantage point and information set, stated
fully and fairly]

**What They See That You Don't:** [the specific blind spots and missed assumptions
visible from their position]

**Their Strategy:** [the specific moves their position makes available — what they
would do and why]

**Legitimacy Assessment**

| Finding From Their Perspective | Legitimate? | Response Category |
|---|---|---|
| [what they see] | [yes / partially / no] | [must change / must defend / must communicate better] |

**Priority Actions**
- Must change: [what requires genuine adjustment to the approach]
- Must defend: [what is correct but needs to be made more robust]
- Must communicate better: [what is right but isn't landing — and the gap]

---

## Notes

The exercise fails if it becomes a performance of the other perspective rather than
genuine inhabitation. The test is whether you find something that makes you
uncomfortable — something you would prefer not to be true. If everything from the
opposing perspective turns out to be wrong or irrelevant, you didn't actually inhabit
it.

---

## What's Next

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

- **Question:** "Perspective reversed. What's next?"
- **Header:** "Next"
- **Options:**
  - `/creativity-other-perspectives` — Apply structured other-perspectives to the reversed view
  - `/communication-audience-modeling` — Model how the reversed view changes communication
  - `/emotional-motivation-mapping` — Map motivations from the reversed perspective
  - **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 →