Token导航 LogoToken导航

Agent Skill · 开发

decision-analysis(决策分析)

decision-analysis 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

decision-analysis 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 16,412。

总安装 504周安装 21GitHub Stars 61下载 168核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/melodic-software/claude-code-plugins --skill decision-analysis

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

用于对复杂决策进行结构化分析,支持决策表、加权评分矩阵和决策树等工具。适合需要明确判断框架和可追溯推理路径的场景,提升决策透明度。通过命令行安装,需确认权限范围及是否触发网络或文件操作。建议结合原始 README 核验具体用法和维护状态后再使用。

decision-analysis 属于开发类 Skill,可作为该场景下的辅助能力补充。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

decision-analysis 怎么安装?

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

decision-analysis 支持哪些 AI 工具?

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

decision-analysis 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

decision-analysis 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

decision-analysis 用的人多吗?

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

decision-analysis 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
decision-analysis

决策分析 · 本页

50461只读MIT通过

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

SKILL.md 原文

Decision Analysis

Model and analyze complex decisions using structured techniques: decision tables, weighted scoring matrices, and decision trees. Creates clear, defensible decision frameworks with traceable rationale.

What is Decision Analysis?

Decision Analysis is a systematic approach to evaluating complex choices by breaking them down into components: objectives, alternatives, criteria, and trade-offs. It transforms subjective judgment into structured, transparent reasoning.

TechniqueBest ForOutput
Decision TableRule-based logic, many conditionsAction based on condition combinations
Weighted Scoring MatrixMulti-criteria comparisonRanked alternatives with scores
Decision TreeSequential decisions, uncertaintyOptimal path with probabilities
Pugh MatrixConcept selection, design choicesBest concept vs baseline

Technique 1: Decision Tables

What is a Decision Table?

A decision table captures complex conditional logic in a compact grid format. It lists all combinations of conditions and their corresponding actions.

ComponentDescriptionExample
ConditionsInput variables/statesCustomer type, Order value
ActionsOutcomes/responsesApply discount, Require approval
RulesCondition combinationsIF Premium AND >$1000 THEN 20% off

Decision Table Workflow

Step 1: Identify Conditions and Actions
## Decision Context

**Decision:** [What are we deciding?]
**Trigger:** [When is this decision made?]

### Conditions (Inputs)
| # | Condition | Possible Values |
|---|-----------|-----------------|
| C1 | [Condition 1] | [Value A / Value B / ...] |
| C2 | [Condition 2] | [Yes / No] |
| C3 | [Condition 3] | [Low / Medium / High] |

### Actions (Outputs)
| # | Action | Description |
|---|--------|-------------|
| A1 | [Action 1] | [What happens] |
| A2 | [Action 2] | [What happens] |
Step 2: Build the Decision Table
## Decision Table: [Name]

| Rule | C1 | C2 | C3 | A1 | A2 |
|------|----|----|----|----|----|
| R1 | Premium | Yes | High | X | - |
| R2 | Premium | Yes | Low | X | X |
| R3 | Standard | Yes | - | - | X |
| R4 | Standard | No | High | - | - |
| R5 | - | No | Low | - | X |

**Legend:** X = Execute action, - = Skip, [blank] = Any value
Step 3: Validate Completeness
CheckQuestionPass?
CompletenessAll condition combinations covered?☐
ConsistencyNo contradictory rules?☐
UniquenessEach combination maps to one outcome?☐
SimplificationCan rules be consolidated?☐

Decision Table Template

## Decision Table: [Decision Name]

**Context:** [Business context]
**Owner:** [Decision owner]
**Last Updated:** [ISO date]

### Conditions
| ID | Condition | Values |
|----|-----------|--------|
| C1 | | |
| C2 | | |

### Actions
| ID | Action | Description |
|----|--------|-------------|
| A1 | | |
| A2 | | |

### Rules
| Rule | C1 | C2 | → | A1 | A2 | Notes |
|------|----|----|---|----|----|-------|
| R1 | | | | | | |
| R2 | | | | | | |

### Validation
- [ ] All combinations covered
- [ ] No contradictions
- [ ] Rules simplified

Technique 2: Weighted Scoring Matrix

What is a Weighted Scoring Matrix?

A weighted scoring matrix (also called decision matrix or Pugh matrix) evaluates multiple alternatives against weighted criteria to produce a ranked list.

ComponentDescription
AlternativesOptions being compared
CriteriaFactors for evaluation
WeightsImportance of each criterion (sum to 100%)
ScoresRating of each alternative on each criterion
Weighted ScoreScore × Weight, summed across criteria

Weighted Scoring Workflow

Step 1: Define the Decision
## Decision Context

**Decision:** [What are we choosing?]
**Objective:** [What outcome do we want?]
**Constraints:** [Non-negotiable requirements]
**Timeline:** [When must we decide?]
Step 2: Identify Alternatives
## Alternatives

| # | Alternative | Description | Source |
|---|-------------|-------------|--------|
| A | [Option A] | [Brief description] | [How identified] |
| B | [Option B] | [Brief description] | [How identified] |
| C | [Option C] | [Brief description] | [How identified] |
Step 3: Define and Weight Criteria
## Criteria

| # | Criterion | Description | Weight | Rationale |
|---|-----------|-------------|--------|-----------|
| 1 | [Criterion 1] | [What it measures] | 30% | [Why this weight] |
| 2 | [Criterion 2] | [What it measures] | 25% | [Why this weight] |
| 3 | [Criterion 3] | [What it measures] | 25% | [Why this weight] |
| 4 | [Criterion 4] | [What it measures] | 20% | [Why this weight] |
|   | **Total** | | **100%** | |

Weighting Methods:

MethodDescriptionWhen to Use
Direct AssignmentStakeholders assign weights directlyClear priorities, experienced team
Pairwise ComparisonCompare criteria pairs (AHP)Unclear priorities, need consensus
RankingRank criteria, convert to weightsQuick, approximate
Equal WeightsAll criteria weighted equallyNo clear priority, initial analysis
Step 4: Score Alternatives
## Scoring Scale

| Score | Meaning |
|-------|---------|
| 5 | Excellent - Fully meets/exceeds criterion |
| 4 | Good - Mostly meets criterion |
| 3 | Adequate - Partially meets criterion |
| 2 | Poor - Minimally meets criterion |
| 1 | Unacceptable - Does not meet criterion |
Step 5: Calculate Weighted Scores
## Decision Matrix

| Criterion | Weight | Alt A | Alt B | Alt C |
|-----------|--------|-------|-------|-------|
| Criterion 1 | 30% | 4 | 3 | 5 |
| Criterion 2 | 25% | 3 | 5 | 4 |
| Criterion 3 | 25% | 5 | 4 | 3 |
| Criterion 4 | 20% | 4 | 4 | 4 |
| **Weighted Score** | | **3.95** | **3.95** | **4.05** |
| **Rank** | | 2 | 3 | 1 |

**Calculation:** Weighted Score = Σ(Score × Weight)
Step 6: Sensitivity Analysis

Test how results change if weights shift:

## Sensitivity Analysis

| Scenario | Weight Change | Winner | Confidence |
|----------|---------------|--------|------------|
| Baseline | As defined | Alt C | - |
| Cost +10% | C1: 40%, others adjusted | Alt A | Low |
| Quality +10% | C2: 35%, others adjusted | Alt C | High |

**Robustness:** [Is the winner stable across scenarios?]

Pugh Matrix (Concept Selection)

A specialized scoring matrix comparing alternatives to a baseline:

## Pugh Matrix: [Decision]

**Baseline:** [Reference option - usually current state or simplest option]

| Criterion | Weight | Alt A vs Baseline | Alt B vs Baseline | Alt C vs Baseline |
|-----------|--------|-------------------|-------------------|-------------------|
| Criterion 1 | 30% | + | S | ++ |
| Criterion 2 | 25% | - | + | S |
| Criterion 3 | 25% | S | + | - |
| Criterion 4 | 20% | + | S | + |
| **Σ Plus** | | 2 | 2 | 2 |
| **Σ Minus** | | 1 | 0 | 1 |
| **Σ Same** | | 1 | 2 | 1 |
| **Net Score** | | +1 | +2 | +1 |

**Legend:** ++ Much better, + Better, S Same, - Worse, -- Much worse

Technique 3: Decision Trees

What is a Decision Tree?

A decision tree maps sequential decisions and uncertain events to visualize possible paths and outcomes. It's ideal for decisions with multiple stages or probabilistic outcomes.

Node TypeSymbolDescription
Decision Node□Choice point (you control)
Chance Node○Uncertain event (probabilities)
End Node△Final outcome (value)

Decision Tree Workflow

Step 1: Frame the Decision
## Decision Tree Context

**Decision:** [Primary decision]
**Objective:** [What we're optimizing - NPV, utility, etc.]
**Time Horizon:** [How far into future]
**Key Uncertainties:** [Major unknown factors]
Step 2: Identify Decision Points and Uncertainties
## Structure

### Decision Points
| # | Decision | Options |
|---|----------|---------|
| D1 | [First decision] | Option A, Option B |
| D2 | [Subsequent decision] | Option X, Option Y |

### Chance Events
| # | Event | Outcomes | Probabilities |
|---|-------|----------|---------------|
| E1 | [Uncertainty 1] | High, Low | 60%, 40% |
| E2 | [Uncertainty 2] | Success, Failure | 70%, 30% |
Step 3: Assign Values and Probabilities
## Outcomes

| Path | Sequence | Probability | Value | Expected Value |
|------|----------|-------------|-------|----------------|
| P1 | D1:A → E1:High → D2:X | 0.60 | $100K | $60K |
| P2 | D1:A → E1:High → D2:Y | 0.60 | $80K | $48K |
| P3 | D1:A → E1:Low | 0.40 | $20K | $8K |
| P4 | D1:B → E2:Success | 0.70 | $150K | $105K |
| P5 | D1:B → E2:Failure | 0.30 | -$50K | -$15K |
Step 4: Calculate Expected Values (Rollback)

Work backwards from end nodes:

## Rollback Analysis

### Chance Node E1 (after D1:A)
EV = (0.60 × max($100K, $80K)) + (0.40 × $20K)
EV = (0.60 × $100K) + $8K = $68K

### Chance Node E2 (after D1:B)
EV = (0.70 × $150K) + (0.30 × -$50K)
EV = $105K - $15K = $90K

### Decision Node D1
Choose B: EV = $90K > $68K

**Recommendation:** Choose Option B

Decision Tree Mermaid Diagram

flowchart TD
    D1{Decision 1<br/>Choose A or B?}

    D1 -->|A| E1((Event 1<br/>Market))
    D1 -->|B| E2((Event 2<br/>Tech))

    E1 -->|High 60%| D2{Decision 2}
    E1 -->|Low 40%| OUT1[/$20K/]

    D2 -->|X| OUT2[/$100K/]
    D2 -->|Y| OUT3[/$80K/]

    E2 -->|Success 70%| OUT4[/$150K/]
    E2 -->|Failure 30%| OUT5[/-$50K/]

    style D1 fill:#ffcc00
    style D2 fill:#ffcc00
    style E1 fill:#66ccff
    style E2 fill:#66ccff

DMN-Lite: Decision Model Notation

For simple, repeatable decisions, use a lightweight DMN approach:

## Decision: [Name]

**Decision ID:** DEC-001
**Business Context:** [When this decision is made]

### Input Data
| Input | Type | Source |
|-------|------|--------|
| Customer Segment | Text | CRM |
| Order Value | Currency | Order System |
| Credit Score | Number | Credit Bureau |

### Decision Logic

IF Customer Segment = "Premium" AND Order Value > 1000 THEN Discount = 20% ELSE IF Customer Segment = "Premium" THEN Discount = 10% ELSE IF Order Value > 5000 THEN Discount = 15% ELSE THEN Discount = 0%


### Output

| Output | Type | Range |
| --- | --- | --- |
| Discount | Percentage | 0% - 20% |

## Output Formats

### Narrative Summary

Decision Analysis Summary

Decision: [What was decided] Date: [ISO date] Analyst: decision-analyst

Context

[2-3 sentences on why this decision was needed]

Approach

  • Technique Used: [Decision Table / Weighted Matrix / Decision Tree]
  • Alternatives Considered: [Count and brief list]
  • Criteria Applied: [Count and key criteria]

Recommendation

Recommended Option: [Name] Rationale: [Key reasons - 2-3 points] Confidence: High / Medium / Low

Key Trade-offs

FactorRecommended OptionRunner-up
[Factor 1][Assessment][Assessment]
[Factor 2][Assessment][Assessment]

Risks and Mitigations

RiskLikelihoodImpactMitigation
[Risk 1]H/M/LH/M/L[Action]

Next Steps

  1. [Immediate action]
  2. [Follow-up action]

### Structured Data (YAML)

decision_analysis: version: "1.0" date: "2025-01-15" analyst: "decision-analyst"

context: decision: "Select project management tool" objective: "Maximize team productivity while minimizing cost" constraints: - "Budget under $500/month" - "Must integrate with team messaging platform" timeline: "Decision by end of Q1"

technique: "weighted_scoring_matrix"

alternatives: - id: A name: "Tool A (Enterprise)" description: "Enterprise-grade, feature-rich work item tracking" - id: B name: "Tool B (Collaborative)" description: "User-friendly, good collaboration features" - id: C name: "Tool C (Developer-Focused)" description: "Modern, developer-focused interface"

criteria: - id: C1 name: "Ease of Use" weight: 0.30 rationale: "Team adoption is critical" - id: C2 name: "Feature Set" weight: 0.25 rationale: "Must handle complex workflows" - id: C3 name: "Integration" weight: 0.25 rationale: "Slack integration required" - id: C4 name: "Cost" weight: 0.20 rationale: "Within budget constraint"

scores: - alternative: A scores: {C1: 3, C2: 5, C3: 4, C4: 3} weighted_total: 3.75 - alternative: B scores: {C1: 5, C2: 4, C3: 5, C4: 4} weighted_total: 4.50 - alternative: C scores: {C1: 4, C2: 4, C3: 3, C4: 5} weighted_total: 3.95

ranking: - rank: 1 alternative: B score: 4.50 - rank: 2 alternative: C score: 3.95 - rank: 3 alternative: A score: 3.75

sensitivity: - scenario: "Cost weight +10%" winner: C stable: false - scenario: "Ease of Use weight +10%" winner: B stable: true

recommendation: choice: B confidence: high rationale: - "Highest weighted score (4.50)" - "Stable across sensitivity scenarios" - "Best ease of use for team adoption"

risks: - description: "Asana pricing may increase" likelihood: medium impact: low mitigation: "Negotiate annual contract"


### Mermaid Decision Matrix Visualization

quadrantChart title Decision Matrix - Tool Selection x-axis Low Cost --> High Cost y-axis Low Features --> High Features quadrant-1 Premium quadrant-2 Best Value quadrant-3 Budget quadrant-4 Expensive Limited "Tool A (Enterprise)": [0.7, 0.9] "Tool B (Collaborative)": [0.5, 0.7] "Tool C (Developer)": [0.3, 0.6] "Tool D (Basic)": [0.2, 0.3]


## When to Use

| Scenario | Technique |
| --- | --- |
| Rule-based logic with many conditions | Decision Table |
| Comparing multiple options on criteria | Weighted Scoring Matrix |
| Sequential decisions with uncertainty | Decision Tree |
| Concept selection vs baseline | Pugh Matrix |
| Simple repeatable business rules | DMN-Lite |
| Quick relative comparison | Pugh Matrix |
| Need stakeholder buy-in | Weighted Scoring (transparent) |

## Integration

### Upstream

- **stakeholder-analysis** - Identify decision makers and criteria sources
- **root-cause-analysis** - Understand problem before deciding solution
- **swot-pestle-analysis** - Strategic context for decisions

### Downstream

- **Requirements** - Decision drives requirement priorities
- **Risk registers** - Capture decision risks
- **Implementation plans** - Execute chosen alternative

## Related Skills

- `prioritization` - MoSCoW, Kano for feature prioritization
- `risk-analysis` - Risk assessment for decision alternatives
- `root-cause-analysis` - Problem analysis before solution selection
- `business-model-canvas` - Strategic business decisions
- `stakeholder-analysis` - Decision maker identification

## Version History

- **v1.0.0** (2025-12-26): Initial release

平台分布

Antigravity

28.28%
按下载量换算48

trae

23.87%
按下载量换算40

windsurf

18.75%
按下载量换算32

Claude Code

12.71%
按下载量换算21

Codex

8.26%
按下载量换算14

Gemini CLI

3.76%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills