Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问clear审计通过

decision-matrix决策矩阵

Agent Skill

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

总安装

1,858

周安装

79

GitHub Stars

85

下载量

651
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/lyndonkl/claude --skill decision-matrix

简介

通过加权评分与敏感性分析使主观因素显性化可比化。

  • 包含完整工作流检查清单,确保关键步骤不被遗漏。
  • 支持多选项在多维度下的量化对比与胜出判定。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。
  • 建议配合敏感性分析验证权重合理性后再做最终决定。
  • decision-matrix 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Decision Matrix

Overview

A decision matrix scores each option on each criterion, making subjective factors visible and comparable. It includes weighted criteria, sensitivity analysis, and clear recommendations.

Quick example:

OptionCost (30%)Speed (25%)Quality (45%)Weighted Score
Option A8 (2.4)6 (1.5)9 (4.05)7.95 ← Winner
Option B6 (1.8)9 (2.25)7 (3.15)7.20
Option C9 (2.7)4 (1.0)6 (2.7)6.40

Option A wins despite not being fastest or cheapest because quality matters most (45% weight).

Workflow

Copy this checklist and track your progress:

Decision Matrix Progress:
- [ ] Step 1: Frame the decision and list alternatives
- [ ] Step 2: Identify and weight criteria
- [ ] Step 3: Score each alternative on each criterion
- [ ] Step 4: Calculate weighted scores and analyze results
- [ ] Step 5: Validate quality and deliver recommendation

Step 1: Frame the decision and list alternatives

Ask user for decision context (what are we choosing and why), list of alternatives (specific named options, not generic categories), constraints or dealbreakers (must-have requirements), and stakeholders (who needs to agree). Understanding must-haves helps filter options before scoring. See Framing Questions for clarification prompts.

Step 2: Identify and weight criteria

Collaborate with user to identify criteria (what factors matter for this decision), determine weights (which criteria matter most, as percentages summing to 100%), and validate coverage (do criteria capture all important trade-offs). If user is unsure about weighting → Use resources/template.md for weighting techniques. See Criterion Types for common patterns.

Step 3: Score each alternative on each criterion

For each option, score on each criterion using consistent scale (typically 1-10 where 10 = best). Ask user for scores or research objective data (cost, speed metrics) where available. Document assumptions and data sources. For complex scoring → See resources/methodology.md for calibration techniques.

Step 4: Calculate weighted scores and analyze results

Calculate weighted score for each option (sum of criterion score × weight). Rank options by total score. Identify close calls (options within 5% of each other). Check for sensitivity (would changing one weight flip the decision). See Sensitivity Analysis for interpretation guidance.

Step 5: Validate quality and deliver recommendation

Self-assess using resources/evaluators/rubric_decision_matrix.json (minimum score ≥ 3.5). Present decision-matrix.md file with clear recommendation, highlight key trade-offs revealed by analysis, note sensitivity to assumptions, and suggest next steps (gather more data on close calls, validate with stakeholders).

Framing Questions

To clarify the decision:

  • What specific decision are we making? (Choose X from Y alternatives)
  • What happens if we don't decide or choose wrong?
  • When do we need to decide by?
  • Can we choose multiple options or only one?

To identify alternatives:

  • What are all the named options we're considering?
  • Are there other alternatives we're ruling out immediately? Why?
  • What's the "do nothing" or status quo option?

To surface must-haves:

  • Are there absolute dealbreakers? (Budget cap, timeline requirement, compliance need)
  • Which constraints are flexible vs rigid?

Criterion Types

Common categories for criteria (adapt to your decision):

Financial Criteria:

  • Upfront cost, ongoing cost, ROI, payback period, budget impact
  • Typical weight: 20-40% (higher for cost-sensitive decisions)

Performance Criteria:

  • Speed, quality, reliability, scalability, capacity, throughput
  • Typical weight: 30-50% (higher for technical decisions)

Risk Criteria:

  • Implementation risk, reversibility, vendor lock-in, technical debt, compliance risk
  • Typical weight: 10-25% (higher for enterprise/regulated environments)

Strategic Criteria:

  • Alignment with goals, future flexibility, competitive advantage, market positioning
  • Typical weight: 15-30% (higher for long-term decisions)

Operational Criteria:

  • Ease of use, maintenance burden, training required, integration complexity
  • Typical weight: 10-20% (higher for internal tools)

Stakeholder Criteria:

  • Team preference, user satisfaction, executive alignment, customer impact
  • Typical weight: 5-15% (higher for change management contexts)

Weighting Approaches

Method 1: Direct Allocation (simplest) Stakeholders assign percentages totaling 100%. Quick but can be arbitrary.

Method 2: Pairwise Comparison (more rigorous) Compare each criterion pair: "Is cost more important than speed?" Build ranking, then assign weights.

Method 3: Must-Have vs Nice-to-Have (filters first) Separate absolute requirements (pass/fail) from weighted criteria. Only evaluate options that pass must-haves.

Method 4: Stakeholder Averaging (group decisions) Each stakeholder assigns weights independently, then average. Reveals divergence in priorities.

See resources/methodology.md for detailed facilitation techniques.

Sensitivity Analysis

After calculating scores, check robustness:

1. Close calls: Options within 5-10% of winner → Need more data or second opinion 2. Dominant criteria: One criterion driving entire decision → Is weight too high? 3. Weight sensitivity: Would swapping two criterion weights flip the winner? → Decision is fragile 4. Score sensitivity: Would adjusting one score by ±1 point flip the winner? → Decision is sensitive to that data point

Red flags:

  • Winner changes with small weight adjustments → Need stakeholder alignment on priorities
  • One option wins every criterion → Matrix is overkill, choice is obvious
  • Scores are mostly guesses → Gather more data before deciding

Common Patterns

Technology Selection:

  • Criteria: Cost, performance, ecosystem maturity, team familiarity, vendor support
  • Weight: Performance and maturity typically 50%+

Vendor Evaluation:

  • Criteria: Price, features, integration, support, reputation, contract terms
  • Weight: Features and integration typically 40-50%

Strategic Choices:

  • Criteria: Market opportunity, resource requirements, risk, alignment, timing
  • Weight: Market opportunity and alignment typically 50%+

Hiring Decisions:

  • Criteria: Experience, culture fit, growth potential, compensation expectations, availability
  • Weight: Experience and culture fit typically 50%+

Feature Prioritization:

  • Criteria: User impact, effort, strategic value, risk, dependencies
  • Weight: User impact and strategic value typically 50%+

When NOT to Use This Skill

Skip decision matrix if:

  • Only one viable option (no real alternatives to compare)
  • Decision is binary yes/no with single criterion (use simpler analysis)
  • Options differ on only one dimension (just compare that dimension)
  • Decision is urgent and stakes are low (analysis overhead not worth it)
  • Criteria are impossible to define objectively (purely emotional/aesthetic choice)
  • You already know the answer (using matrix to justify pre-made decision is waste)

Use instead:

  • Single criterion → Simple ranking or threshold check
  • Binary decision → Pro/con list or expected value calculation
  • Highly uncertain → Scenario planning or decision tree
  • Purely subjective → Gut check or user preference vote

Quick Reference

Process:

  1. Frame decision → List alternatives
  2. Identify criteria → Assign weights (sum to 100%)
  3. Score each option on each criterion (1-10 scale)
  4. Calculate weighted scores → Rank options
  5. Check sensitivity → Deliver recommendation

Resources:

Deliverable: decision-matrix.md file with table, rationale, and recommendation

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

27.4%
按下载量换算178

Gemini CLI

26.31%
按下载量换算171

Antigravity

17.93%
按下载量换算117

windsurf

14.39%
按下载量换算94

OpenCode

8.71%
按下载量换算57

github-copilot

3.52%
按下载量换算23

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills