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

Creativity Other Perspectives

ASecurity

Apply Edward de Bono's OPS (Other People's Shoes) tool to genuinely think from other perspectives. Use when the user needs to understand how others will respond to a decision, wants to anticipate objections, is designing something for other people, is in a conflict or negotiation, or needs to check whether they've considered the people affected by a situation. OPS is structured empathy — not sentiment, but reasoning.

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

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill creativity-other-perspectives --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Creativity Other Perspectives?

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

Security grade badge for Creativity Other Perspectives
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-creativity-other-perspectives/badge)](https://www.skillsdirectory.com/skills/rondoflow-creativity-other-perspectives)

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

Download with Pro
Files
SKILL.md
---
name: creativity-other-perspectives
description: "Apply Edward de Bono's OPS (Other People's Shoes) tool to genuinely think from other perspectives. Use when the user needs to understand how others will respond to a decision, wants to anticipate objections, is designing something for other people, is in a conflict or negotiation, or needs to check whether they've considered the people affected by a situation. OPS is structured empathy — not sentiment, but reasoning."
---

You are facilitating an OPS (Other People's Shoes) session using Edward de Bono's CoRT thinking tools. OPS is a structured empathy tool — not an exercise in emotional identification, but a disciplined method for thinking through how other people actually reason about a situation.

## What OPS is and isn't

OPS is not asking "how would they feel?" It is asking "how would they think?" The distinction matters. Feelings are important but often guessed inaccurately. Thinking patterns — the values, interests, constraints, and goals that drive someone's reasoning — can be mapped more reliably.

When you put on someone else's shoes in an OPS session, you:
- Take on their values and priorities, not just their role
- Reason from their information and perspective, not yours
- Surface what they would actually say or think — not what you wish they would say
- Maintain their internal logic — even if you disagree with it

The point is not sympathy. It is accuracy. A bad OPS produces a straw man — a caricature of what the other person thinks, filtered through your assumptions. A good OPS produces a genuine model of how they actually reason.

## Your process

**Step 1: Identify the perspectives to explore**
Who are the relevant others? These might be named individuals, roles, stakeholder groups, or affected parties. For decisions with clear stakeholders, be specific — "the person who has to implement this" is more useful than "employees."

**Framing check:** Confirm the specific challenge or situation before continuing. State what you've identified — the actual situation being analyzed and whose perspectives matter — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the situation and the decision or action at the center of it]. 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

Aim to include:
- The people most affected
- The people most likely to resist or object
- The people whose cooperation is needed
- Any party whose interests are easily overlooked

**Before narrowing:** Show the complete list of candidate perspectives to the user first. Use `AskUserQuestion`:
- **Question:** "I've identified [N] perspectives to explore: [list them]. Before I select the most relevant ones to reason through in depth, are there any you'd flag as especially important, or any I've missed?"
- **Header:** "Prioritise"
- **Options:**
  - **Proceed with your selection** — the set looks right
  - **Flag one** — user will name a specific perspective to include
  - **Add a missing one** — user will describe it

**Step 2: For each perspective — reason from inside it**

For each person or group, work through:

*What do they value and prioritize?*
What matters most to them — in work, in this situation specifically? What are their goals? What do they want to protect or preserve?

*What do they know and believe?*
What information do they have access to? What do they assume about the situation? What might they not know that you know?

*What are their constraints and pressures?*
What are they accountable for? What are the consequences for them of different outcomes? What are they trying to avoid?

*How do they see this situation?*
From their vantage point, what is this situation about? What would they say is happening here? What would they say the main issue is?

*What would they say or do?*
If they were in the room, what would they say? What objections would they raise? What would they support? What would they ask for?

**Step 3: What does the full picture reveal?**
After working through all perspectives, step back. What does the map of perspectives show? Where are the conflicts? Where is there more alignment than expected? What factor keeps appearing across multiple perspectives? What does this suggest about what needs attention?

## 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
  - **One key perspective** — The single viewpoint most likely being missed or underweighted
  - **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

**Situation:** [What is being decided or done]

**Perspectives explored:**

---
**[Person/Group 1]**
- Values and priorities: [what matters to them]
- What they know/believe: [their information and assumptions]
- Constraints and pressures: [what they're accountable for, what they fear]
- How they see this: [their framing of the situation]
- What they'd say/do: [their likely response]

---
**[Person/Group 2]**
[same structure]

---

**What the full picture reveals:**
[Key tensions between perspectives, unexpected alignment, what factor appears most consistently, what needs attention based on this map]

## The discipline

An OPS session fails if every perspective ends up agreeing with your own position. Real stakeholders have real interests that sometimes conflict with yours. If the OPS output reads like a chorus of support for your preferred approach, the shoes weren't actually worn — they were just described from the outside. The test: does the OPS reveal something you hadn't considered, or surface an objection you hadn't anticipated? If not, go deeper.

---

## What's Next

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

- **Question:** "Other perspectives applied. What's next?"
- **Header:** "Next"
- **Options:**
  - `/communication-audience-modeling` — Model how to communicate to each perspective
  - `/emotional-motivation-mapping` — Map the motivations revealed by each perspective
  - `/ethics-empathy-circle` — Extend the perspective analysis with structured empathy
  - **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 →