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

Analogy Perspective Shifting

ASecurity

Approaches a problem from completely different fields to break the assumption blindness that comes from domain expertise. Triggers: 'fresh eyes', 'outside perspective', 'what would a [different expert] say', 'beginner's mind', 'approach from another field'.

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

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill analogy-perspective-shifting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Analogy Perspective Shifting?

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

Security grade badge for Analogy Perspective Shifting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-analogy-perspective-shifting/badge)](https://www.skillsdirectory.com/skills/rondoflow-analogy-perspective-shifting)

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

Download with Pro
Files
SKILL.md
---
name: analogy-perspective-shifting
description: "Approaches a problem from completely different fields to break the assumption blindness that comes from domain expertise. Triggers: 'fresh eyes', 'outside perspective', 'what would a [different expert] say', 'beginner's mind', 'approach from another field'."
---

# Analogy Perspective Shifting

Domain expertise creates assumption blindness. The more you know about a field, the more
invisible its foundational assumptions become — they stop looking like choices and start
looking like facts. Bringing in genuine outsider perspectives breaks this. Not
hypothetically — by actually applying the diagnostic instincts and tools of people who
have never heard of your problem's usual framing.

---

## Your Process

**Step 1: State the Problem**
Describe the problem as you currently understand it. This is the insider framing — it will
contain the assumptions you're trying to surface.

**Framing check:** Confirm the specific problem before continuing. State what you've identified — the actual situation being examined and its domain — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the problem and its domain]. 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: Choose 2-3 Genuinely Different Fields**
Select fields with fundamentally different training, tools, and instincts. For software
problems: film production, archaeology, emergency medicine, urban planning. For
organisational problems: ecology, military logistics, theatre direction, structural
engineering. Avoid fields that are adjacent — choose fields that would produce different
first questions.

**Step 3: Build Each Expert's Toolkit**
For each field: what are their core diagnostic tools and instincts? What do they always
check first? What patterns are they trained to spot? What would their first question be
when encountering an unknown problem?

**Step 4: Apply Each Lens**
Apply each expert's toolkit to your problem. What do they immediately notice that insiders
overlook? What would they try first that you haven't? What would strike them as obviously
wrong or unnecessarily complex? Don't moderate the outsider view — let it be naive.

**Step 5: Find Cross-Field Patterns**
What do multiple outsiders notice independently? When different fields converge on the
same observation, that observation has a strong claim to being real — it's visible from
multiple angles, not an artefact of one framing.

---

## 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
  - **Shifted perspective only** — The view from the new field, skip the formal structural mapping
  - **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

**Problem (insider framing):**
> [Current description]

**Field perspectives:**

| Field | Core instincts / tools | What they notice | What they'd try first |
|-------|------------------------|------------------|-----------------------|
| | | | |
| | | | |

**Cross-field patterns (what multiple outsiders see):**
> [Observations that appear across more than one field]

**Most useful foreign insight:**
> [The single observation or approach from outside that would most change how you work
> the problem — and why it's been invisible from inside]

---

## Notes

The exercise fails if the "outside" perspectives are just your own reasoning relabelled.
Each field's observations should surprise you. If they don't, you haven't actually left
your frame — you've just dressed it in different vocabulary.

---

## What's Next

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

- **Question:** "Perspectives shifted. What's next?"
- **Header:** "Next"
- **Options:**
  - `/communication-audience-modeling` — Model the audience through each shifted perspective
  - `/creativity-alternatives` — Generate alternatives from each perspective
  - `/emotional-motivation-mapping` — Map motivations visible from each 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 →