Token导航 LogoToken导航

Agent Skill · 研究检索

multi-perspective-analysis(多视角分析)

multi-perspective-analysis 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

multi-perspective-analysis 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 61,288。

总安装 353周安装 15GitHub Stars 5下载 124核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:multi-perspective-analysis(多视角分析)
来源仓库:https://github.com/legacybridge-tech/claude-plugins
仓库路径:skills/multi-perspective-analysis
安装命令:
npx skills add https://github.com/legacybridge-tech/claude-plugins --skill multi-perspective-analysis
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/legacybridge-tech/claude-plugins --skill multi-perspective-analysis

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

multi-perspective-analysis 用于多视角信息检索与分析,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。支持基于关键词、任务场景或来源线索筛选信息,适用于研究、调研等需要多角度梳理内容的场景。

通过 npx skills add 命令从 GitHub 仓库安装,需确认权限与维护状态后再使用。建议在使用前核实是否会触发联网、命令执行或文件读写操作,避免安全风险。可结合原始 README 和仓库路径进一步了解具体用法与限制条件。

来源仓库内路径:skills/multi-perspective-analysis

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/legacybridge-tech/claude-plugins --skill multi…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

multi-perspective-analysis 怎么安装?

在终端执行 npx skills add https://github.com/legacybridge-tech/claude-plugins --skill multi-perspecti…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

multi-perspective-analysis 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

multi-perspective-analysis 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

multi-perspective-analysis 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

multi-perspective-analysis 用的人多吗?

公开数据是累计安装 353 次,近一周安装 15 次,下载 124 次,GitHub 5 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

multi-perspective-analysis 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
multi-perspective-analysis

多视角分析 · 本页

3535权限未标注未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Multi-Perspective Analysis Skill

A systematic methodology for examining propositions through dynamically generated expert perspectives.

When to Invoke This Skill

  • User presents a proposition, thesis, or idea for examination
  • User asks "what do experts think about", "different perspectives on", "analyze this from multiple angles"
  • User wants to validate assumptions or find blindspots
  • User mentions "devil's advocate", "critique", "challenge this idea"
  • User requests debate or contrasting viewpoints
  • Keywords: "perspectives", "validate", "blindspots", "assumptions", "debate", "critique", "examine", "multi-angle", "expert opinion"

Core Concepts

Dynamic Expert Generation

Unlike fixed expert panels, this skill generates experts contextually relevant to each proposition:

  • Domain Experts (2): Direct specialists in the proposition's field, providing depth
  • Adjacent Experts (1-2): Specialists in related but distinct fields, providing breadth
  • Contrarian Expert (1): Those likely to challenge the proposition, providing critical perspective
  • Meta Expert (1): Methodologists, epistemologists, or systems thinkers, providing macro view

Three Analysis Modes

  1. Validation Mode: Find blindspots, hidden assumptions, and potential counterarguments
  2. Comprehensive Analysis Mode: Each expert provides detailed perspective
  3. Debate Mode: Experts engage in structured dialogue with opposing views

Workflow

Phase 1: Proposition Intake

Extract and clarify the proposition:

  1. Identify the core claim or thesis
  2. Detect domain(s) involved (technology, philosophy, business, science, etc.)
  3. Assess complexity level (simple assertion vs. multi-faceted thesis)
  4. Note any implicit assumptions visible in the framing

Present understanding to user:

I understand your proposition as:

"[Restate the proposition in clear language]"

Related domains: [Domain 1], [Domain 2], [Domain 3]
Implicit assumptions: [Assumptions built into the proposition]

Is this understanding correct? Would you like to adjust this framing before we continue?

Wait for user confirmation before proceeding.

Phase 2: Expert Role Generation

Generate 4-6 contextually relevant experts:

For each expert, determine:

  • Title/Role: Specific expertise area
  • Perspective Lens: What lens they view problems through
  • Likely Stance: Initial inclination toward the proposition (supportive/skeptical/neutral)
  • Unique Contribution: What insight only this expert brings

Expert Generation Logic:

Given proposition domain(s), generate:

1. DOMAIN EXPERTS (2)
   - Primary field specialists
   - Deep knowledge, may have field-specific biases
   - Example: For "AI will replace programmers" → Senior Software Architect, AI Researcher

2. ADJACENT FIELD EXPERTS (1-2)
   - Related but distinct perspectives
   - See connections others miss
   - Example: For "AI will replace programmers" → Labor Economist, Cognitive Scientist

3. CONTRARIAN/CRITICAL EXPERT (1)
   - Likely to challenge the proposition
   - Finds weaknesses others overlook
   - Example: For "AI will replace programmers" → Technology Historian (who's seen similar predictions fail)

4. META/SYSTEMS EXPERT (1)
   - Sees bigger picture, systemic effects
   - Challenges framing itself
   - Example: For "AI will replace programmers" → Systems Theorist, Philosopher of Technology

Present expert panel to user:

Based on your proposition, I recommend the following expert perspectives:

1. **[Expert Title 1]**
   - Perspective: [What they focus on]
   - Likely stance: [Supportive/Skeptical/Neutral]
   - Unique contribution: [Unique insight]

2. **[Expert Title 2]**
   - Perspective: [What they focus on]
   - Likely stance: [Supportive/Skeptical/Neutral]
   - Unique contribution: [Unique insight]

3. **[Expert Title 3]**
   - Perspective: [What they focus on]
   - Likely stance: [Supportive/Skeptical/Neutral]
   - Unique contribution: [Unique insight]

4. **[Expert Title 4]**
   - Perspective: [What they focus on]
   - Likely stance: [Supportive/Skeptical/Neutral]
   - Unique contribution: [Unique insight]

[Additional experts...]

Would you like to:
- Proceed with these experts for analysis
- Add a specific type of expert
- Remove or replace an expert
- Suggest a custom expert role

Wait for user confirmation or adjustment.

Phase 3: Analysis Mode Selection

Present mode options using AskUserQuestion:

Please select an analysis mode:

1. **Validation Mode**
   Each expert identifies:
   - Hidden assumptions in the proposition
   - Potential blindspots
   - Counterarguments
   - Failure conditions for the proposition
   Best for: Testing robustness of an idea before commitment

2. **Comprehensive Analysis Mode**
   Each expert provides:
   - Their assessment of the proposition
   - Supporting evidence from their domain
   - Concerns and caveats
   - Recommendations
   Best for: Understanding all angles before making a decision

3. **Debate Mode**
   Experts engage in structured debate:
   - Opening statements (each expert's position)
   - Cross-examination (experts challenge each other)
   - Rebuttals and synthesis
   - Final verdict and unresolved uncertainties
   Best for: Exploring genuine disagreements and finding synthesis

Which mode would you like to use?

Wait for user selection.

Phase 4: Execute Analysis

Mode 1: Validation Analysis

For each expert, generate:

### [Expert Title]: Validation Analysis

#### Hidden Assumptions Detected
1. **[Assumption 1]**: [Why this is an assumption that wasn't stated]
2. **[Assumption 2]**: [Why this is an assumption that wasn't stated]

#### Blindspots Identified
1. **[Blindspot 1]**: [What the proposition overlooks]
   - Importance: [What impact if ignored]
   - How to address: [Mitigation measures]

2. **[Blindspot 2]**: [What the proposition overlooks]
   - Importance: [What impact if ignored]
   - How to address: [Mitigation measures]

#### Counterarguments
1. **[Counterargument 1]**
   - Challenge: [Statement of opposing view]
   - Evidence/Logic: [Why this counterargument has value]
   - Possible response: [How the proposition might respond]
   - Strength: [Strong/Medium/Weak]

#### Failure Conditions
- The proposition fails if: [Condition 1]
- The proposition fails if: [Condition 2]

#### Overall Robustness Assessment
[Brief statement about how well the proposition holds up to scrutiny]

After all experts, provide synthesis:

## Validation Synthesis

### Key Blindspots (Consensus)
[Blindspots identified by multiple experts]

### Most Challenging Counterarguments
[Ranked by strength and frequency]

### Critical Assumptions Requiring Verification
[Assumptions that would invalidate the proposition if wrong]

### Robustness Score: [X/10]
- Passes basic scrutiny: [Yes/No]
- Withstands expert challenges: [Yes/Partially/No]
- Requires revision: [Specifically what]

### Recommended Actions
1. [Action to address blindspots/assumptions]
2. [Action to address blindspots/assumptions]
Mode 2: Comprehensive Analysis

For each expert, generate:

### [Expert Title]: Comprehensive Analysis

#### Assessment
[2-3 paragraphs of the expert's overall view of the proposition]

#### Evidence and Reasoning
**Supporting factors:**
- [Factor 1 with evidence]
- [Factor 2 with evidence]

**Concerning factors:**
- [Concern 1 with reasoning]
- [Concern 2 with reasoning]

#### Domain-Specific Insights
[What their expertise reveals that others might miss]

#### Confidence Level
- Assessment confidence: [High/Medium/Low]
- Key uncertainties: [What would change their view]

#### Recommendations
1. [Actionable recommendation from this perspective]
2. [Actionable recommendation from this perspective]

After all experts, provide synthesis:

## Comprehensive Synthesis

### Areas of Agreement
[Where experts converge]

### Areas of Divergence
[Where experts diverge and why]

### Integrated Assessment
[Balanced view combining all perspectives]

### Decision Framework
If you believe [X], then: [Conclusion A]
If you prioritize [Y], then: [Conclusion B]
If [Z] is uncertain, then: [Wait for more information]

### Recommended Next Steps
1. [Action with rationale]
2. [Action with rationale]
Mode 3: Debate Analysis

Structure the debate:

## Expert Debate: [Proposition]

### Round 1: Opening Statements

**[Expert 1 - Supportive]:**
> [2-3 paragraphs of opening statement supporting the proposition]

**[Expert 2 - Skeptical]:**
> [2-3 paragraphs of opening statement opposing or qualifying the proposition]

**[Expert 3 - Neutral/Adjacent]:**
> [2-3 paragraphs of opening statement offering an alternative framework]

**[Expert 4 - Systems View]:**
> [2-3 paragraphs of opening statement analyzing from a macro perspective]

[Additional experts as applicable]

---

### Round 2: Cross-Examination

**[Expert 1] challenges [Expert 2]:**
> "[Specific challenge to their argument]"

**[Expert 2] responds:**
> "[Defense and counter-challenge]"

**[Expert 3] interjects:**
> "[Observation that affects both arguments]"

**[Expert 4] adds:**
> "[Systems-level addition]"

[Continue cross-examination, ensuring each expert interacts with at least one other]

---

### Round 3: Rebuttals and Concessions

**[Expert 1] concedes:**
> "[What they now acknowledge from the debate]"
> "However, I maintain [core position] because [reason]"

**[Expert 2] concedes:**
> "[What they now acknowledge from the debate]"
> "However, I maintain [core position] because [reason]"

[All experts as applicable]

---

### Round 4: Synthesis Attempt

**Moderator Synthesis:**

The experts have identified these key tensions:
1. [Tension 1]: [Expert A] vs [Expert B] on [issue]
2. [Tension 2]: [Expert C] vs [Expert D] on [issue]

Possible resolution paths:
- [Resolution 1]
- [Resolution 2]
- [Acknowledge as genuinely irresolvable disagreement]

---

### Debate Outcome

**Points of Consensus:**
- [Consensus 1]
- [Consensus 2]

**Unresolved Disagreements:**
- [Disagreement 1 - Why it persists]
- [Disagreement 2 - Why it persists]

**Verdict:**
[Summary of where the proposition stands after the debate]

**For the proposition holder:**
If proceeding, consider: [Key modifications suggested by the debate]
If reconsidering, explore: [Alternative framings that emerged]

Phase 5: Output Delivery & Follow-up

Present analysis to user:

Deliver the full analysis in the format matching the selected mode.

Offer follow-up options:

Analysis complete. Would you like to:

1. **Deep dive**: Explore one expert's perspective in more detail
2. **Challenge**: Have me defend against a specific point
3. **Switch mode**: Re-analyze the same proposition with a different analysis mode
4. **Refine proposition**: Update your proposition based on insights and re-analyze
5. **Save results**: Save this analysis as a file
6. **Finish**: End the analysis

Phase 6: Optional Save

If user chooses to save:

Ask the user how they would like to save the analysis results:

How would you like to save this analysis?

1. **Specify path**: Tell me the file path to save to
2. **Via AkashicRecords**: Use the knowledge management system to save (if enabled)
3. **Copy to clipboard**: I'll output formatted content for you to copy

Option 1: Specify path

  1. Ask user for the file path to save
  2. Format content using the suggested document structure
  3. Write file using the Write tool

Option 2: Via AkashicRecords (if enabled)

  1. Invoke AkashicRecords' add-content skill
  2. Recommend directory based on content analysis
  3. Execute save following the target directory's RULE.md

Option 3: Output formatted content

Output formatted Markdown content directly in the conversation for the user to copy and save manually.

Suggested document structure:

---
title: Multi-Perspective Analysis - [Proposition Summary]
date: [YYYY-MM-DD]
type: analysis
mode: [validation|comprehensive|debate]
experts: [List of expert roles]
tags: [Auto-generated from domains]
---

# Multi-Perspective Analysis

## Proposition
[Original proposition]

## Expert Panel
[List of experts used]

## Analysis
[Complete analysis content for the selected mode]

## Key Insights
[Synthesis and conclusions]

## Follow-up Questions
[Any unresolved questions for future exploration]

Expert Role Templates

Technology Domain

  • Software Architect
  • AI/ML Researcher
  • Cybersecurity Specialist
  • Technology Historian
  • UX Researcher
  • DevOps Engineer
  • CTO / Technical Leadership

Business Domain

  • Management Consultant
  • Venture Capitalist
  • Operations Manager
  • Market Analyst
  • Entrepreneur
  • CFO / Financial Leadership
  • Labor Economist

Science Domain

  • Research Scientist
  • Science Communicator
  • Philosopher of Science
  • Data Scientist
  • Research Methodologist
  • Interdisciplinary Researcher

Social/Humanities Domain

  • Sociologist
  • Psychologist
  • Political Scientist
  • Ethicist
  • Historian
  • Anthropologist
  • Legal Scholar

Systems/Meta Domain

  • Systems Theorist
  • Epistemologist
  • Complexity Scientist
  • Futurist
  • Risk Analyst
  • Decision Theorist

Error Handling

Proposition Too Vague

Your proposition appears quite general. To generate relevant experts, I need more specifics.

Could you clarify:
- What specific claim are you making?
- In what context or domain?
- What decision or understanding would this help with?

Alternatively, I can attempt analysis with this interpretation: [Suggested interpretation]

Too Many Domains

This proposition spans multiple domains. I suggest:

Option A: Analyze with 6 experts (maximum), prioritizing [suggested priority order]
Option B: Break into sub-propositions and analyze separately:
  - Sub-proposition 1: [Aspect 1]
  - Sub-proposition 2: [Aspect 2]

Which approach do you prefer?

User Wants Custom Expert

You've requested a [custom expert type].

For this expert, please help me understand:
- What perspective do they view problems through?
- What are their likely biases or tendencies?
- What unique insight should they bring?

Alternatively, I can infer: [Suggested interpretation of custom expert]

Examples

Example 1: Technology Proposition (Validation Mode)

User: "I believe microservices architecture is always better than monolithic architecture for enterprise applications"

Skill response:

I understand your proposition as:

"Microservices architecture is universally superior to monolithic architecture for enterprise applications"

Related domains: Software Architecture, Enterprise IT, Operations
Implicit assumptions: Assumes "better" means better across all dimensions (scalability, maintainability, cost, etc.)

Is this understanding correct?

[User confirms]

Based on your proposition, I recommend the following expert perspectives:

1. **Enterprise Software Architect**
   - Perspective: System design, scalability, maintainability
   - Likely stance: Nuanced (has seen both succeed and fail)
   - Unique contribution: Real-world implementation experience

2. **DevOps/Platform Engineer**
   - Perspective: Operational complexity, deployment, monitoring
   - Likely stance: Skeptical (bears the operational burden)
   - Unique contribution: Hidden costs of distributed systems

3. **CTO with Startup-to-Enterprise Experience**
   - Perspective: Organizational evolution, team structure
   - Likely stance: Context-dependent (depends on stage)
   - Unique contribution: When architectural transitions make sense

4. **Technology Historian**
   - Perspective: Patterns in technology adoption
   - Likely stance: Skeptical of "always" claims
   - Unique contribution: Historical perspective on silver bullet thinking

5. **Labor Economist**
   - Perspective: Human resources, skills market, organizational efficiency
   - Likely stance: Neutral
   - Unique contribution: Talent market and team composition angles

Proceed with these experts for analysis?

[User selects Validation Mode]

[Skill produces validation analysis with blindspots like: organizational readiness, operational complexity costs, team skill requirements, latency overhead, debugging complexity, etc.]

Example 2: Business Strategy (Debate Mode)

User: "Remote work is more productive than office work"

Skill response:

I understand your proposition as:

"Remote work arrangements produce higher productivity than traditional office work"

Related domains: Organizational Behavior, Management, Work Psychology
Implicit assumptions: Assumes productivity can be measured and compared across different contexts

Is this understanding correct?

[User confirms, selects Debate Mode with experts: Organizational Psychologist, Remote-First CEO, Traditional Management Consultant, Labor Economist, Systems Theorist]

[Skill produces structured debate with opening statements, cross-examination, and synthesis showing the nuanced conditions under which each arrangement excels]

Example 3: Philosophy/Ethics (Comprehensive Analysis)

User: "AI should be granted legal personhood once it passes certain cognitive thresholds"

Skill response:

I understand your proposition as:

"Artificial intelligence systems should be recognized as legal persons when they demonstrate cognitive capabilities beyond defined thresholds"

Related domains: AI Ethics, Law, Philosophy of Mind, Public Policy
Implicit assumptions: Assumes cognitive capability is the relevant criterion for personhood

Is this understanding correct?

[User confirms, selects Comprehensive Analysis with experts: AI Ethicist, Legal Scholar, Philosopher of Mind, AI Researcher, Policy Maker, Systems Theorist]

[Skill produces comprehensive analysis with each expert's deep perspective, evidence, concerns, and recommendations, followed by integrated synthesis]

Notes

  • Expert generation is dynamic - no fixed panel, always contextually relevant
  • All three modes provide actionable insights, not just academic analysis
  • User confirmation checkpoints ensure alignment before time-intensive analysis
  • Save functionality supports multiple methods: direct file path, AkashicRecords integration, or formatted output for manual copy
  • Quality depends on clear proposition framing - encourage refinement if needed
  • This skill works independently but enhances existing workflows

平台分布

Codex

31.84%
按下载量换算39

Claude

31.77%
按下载量换算39

Cursor

17.55%
按下载量换算22

Gemini CLI

9.41%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills