decision-matrix
Skill1 starsChanged 2 months agoMITView on GitHub
Objective trade-off analysis using weighted criteria. Eliminates popularity bias by requiring user-defined priorities. Use when choosing between technologies, architectures, or vendors.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- jaskirat1616/grok-skillstheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- vredin/vredin-CC-Harnesstheir own version, first seen Nov 1, 2026
- varelaia/claude-skills-publictheir own version, first seen Oct 26, 2026
- JayRHa/agent-skillstheir own version, first seen Oct 15, 2026
- markusbegerow/board-of-directorstheir own version, first seen Oct 13, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- jaskirat1616/grok-skills★ 22same name
- Hongyu-yu/matsci-ai-skills★ 19same name
- JayRHa/agent-skills★ 12same name
- JayRHa/AgentSkills★ 12same name
- vredin/vredin-CC-Harness★ 9same name
- fzfclee/consulting-skills★ 6same name
- The-Utopia-Studio/skills★ 6same name
- markusbegerow/board-of-directors★ 5same name
- 53able/skills★ 4same name
- hraness/personal-monorepo-template★ 4same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- chestertons-fenceSkill
- first-principles-thinkingSkill
- humanizer-karu-customSkill
- inversion-thinkingSkill
- map-vs-territorySkill
- occams-razorSkill
- pareto-principleSkill
- rubber-duckingSkill
- second-order-thinkingSkill
- systems-thinkingSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Any Multi-Option Decision: When there are 3+ options and no obvious winner.
- Distinctive: line 21
2 options or fewer: Use Pros/Cons instead. Matrix adds overhead without benefit.
- Distinctive: line 23
Non-compensatory criteria: If any criterion is an absolute blocker (e.g., "must support IE11"), filter those options first.
- Distinctive: line 24
High uncertainty / no data: When you cannot evidence any scores, the matrix produces false precision.
- Distinctive: line 25
Already decided: If the user has already chosen, the matrix will confirm rather than inform.
- Distinctive: line 38
Ask the user for their Top 3-5 evaluation criteria.
- Distinctive: line 47
Before proceeding, ask the user:
- Distinctive: line 51
If yes, filter out disqualified options before scoring.
- Distinctive: line 54
Ask the user to rate the importance of each criterion.
- Distinctive: line 92
Before presenting results, verify:
- Distinctive: line 102
Time budget: If analysis exceeds 30 minutes, simplify to binary (Meets/Doesn't meet) or Pros/Cons
- Distinctive: line 146
Review: If no entries in 60+ days, check LEARNINGS.md before next use.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Decision Matrix (The Bias Eliminator)
"When you can measure what you are speaking about... you know something about it." - Lord Kelvin
When to Use
- Technology Choices: "Should we use React or Vue?"
- Architecture Decisions: "Monolith vs Microservices?"
- Vendor Selection: "AWS vs GCP vs Azure?"
- Any Multi-Option Decision: When there are 3+ options and no obvious winner.
When NOT to Use
- 2 options or fewer: Use Pros/Cons instead. Matrix adds overhead without benefit.
- Incommensurable options: Cannot compare "adopt React" vs "build custom framework" if the evaluation criteria cannot be objectively measured.
- Non-compensatory criteria: If any criterion is an absolute blocker (e.g., "must support IE11"), filter those options first.
- High uncertainty / no data: When you cannot evidence any scores, the matrix produces false precision.
- Already decided: If the user has already chosen, the matrix will confirm rather than inform.
The Protocol: Weighted Scoring
0. Pre-Check (Occam's Razor)
- 2 Options Only? Skip the matrix. Use a simple Pros/Cons list.
- 3+ Options? Proceed with the full matrix.
1. List Options
Enumerate all viable choices.
- Example: React, Vue, Svelte, Angular
2. Define Criteria (WITH USER)
Ask the user for their Top 3-5 evaluation criteria.
[!IMPORTANT] You MUST ask the user for criteria. Do not invent criteria based on general knowledge. The user's context defines what matters.
- Example Criteria: Performance, Learning Curve, Ecosystem Size, Bundle Size, Hiring Pool
3. Check for Conflicts
Before proceeding, ask the user:
- "Do any of these criteria conflict with each other?" (e.g., "max performance" vs "min bundle size")
- "Is any criterion non-negotiable — meaning if any option fails it, it's automatically disqualified?"
If yes, filter out disqualified options before scoring.
4. Assign Weights (WITH USER)
Ask the user to rate the importance of each criterion.
| Weight | Meaning |
| 1 | Nice to have |
| 2 | Moderately important |
| 3 | Very important |
| 4 | Critical (high weight, but compensable — non-negotiables should be filtered in Step 3 instead) |
5. Score Options (with Evidence)
Rate each option against each criterion (1-5 scale).
| Score | Meaning | Evidence Required |
| 1 | Poor | Must cite specific data point |
| 3 | Adequate | Default if uncertain |
| 5 | Excellent | Must cite specific data point |
[!WARNING] No evidence = Score 3. If you cannot cite benchmarks, docs, or user research, default to "Adequate" (3). Do not guess.
You (the agent) can score based on research, but weights come from the user.
6. Calculate Weighted Scores
For each option: Total = Σ (Score × Weight)
Present results as a single Total per option (e.g., "Vue: 40, React: 35, Angular: 31"). Use ranges only when the user explicitly asks for uncertainty estimates.
7. Recommend & Verbalize
Present the matrix and state the winner with reasoning.
- "Based on your priorities (Performance=Critical, Learning Curve=Important), Vue scores highest because..."
8. Set Review Trigger
Set a 6-month review checkpoint. Log this decision to .learnings/REVIEW.md.
Validation Steps
Before presenting results, verify:
- Non-compensatory filter applied: Were hard constraints checked first?
- Conflict detection done: Were negatively correlated criteria surfaced?
- Evidence anchoring: Did you cite evidence for scores of 1 or 5?
- Uncertainty notation: Did you use ranges for high-uncertainty outputs?
Timeboxing
- Maximum criteria: 7 (beyond this, weights become statistically meaningless)
- Maximum options: 10 (beyond this, scoring becomes inconsistent)
- Time budget: If analysis exceeds 30 minutes, simplify to binary (Meets/Doesn't meet) or Pros/Cons
Example
User Goal: Choose a frontend framework for a small team with tight deadlines.
User Criteria & Weights:
| Criterion | Weight |
| Learning Curve | 4 |
| Performance | 2 |
| Ecosystem | 3 |
Agent Scoring:
| Option | Learning (×4) | Perf (×2) | Ecosystem (×3) | Total |
| React | 3 (12) | 4 (8) | 5 (15) | 35 |
| Vue | 5 (20) | 4 (8) | 4 (12) | 40 ✅ |
| Angular | 2 (8) | 4 (8) | 5 (15) | 31 |
Recommendation: "Vue scores highest (40) primarily due to its excellent Learning Curve score, which you rated as Critical."
Skill Integration
| Situation | Use Instead/Also |
| 2 options | rubber-ducking |
| Need to validate scores | map-vs-territory |
| Criteria might be wrong | chestertons-fence |
| Risk of over-analysis | occams-razor |
| Need to understand second-order effects | second-order-thinking |
| Prioritizing a backlog | pareto-principle |
Self-Improvement Protocol
Log only if prediction was wrong.
## [YYYY-MM-DD] {Brief Description}
**Decision:** {what was chosen}
**Outcome:** {Correct or wrong?}
**Lesson:** {one sentence}Review: If no entries in 60+ days, check LEARNINGS.md before next use.
Evaluations
Eval 1: Three-Way Technology Choice
Scenario: User must choose between Postgres, MongoDB, Redis for a new project. No existing codebase. Expected: Asks for 3-5 criteria with weights, scores each option, produces weighted recommendation. Pass criteria: Requires user input for criteria/weights, cites evidence for scores of 1 or 5.
Eval 2: Two Options (Should Skip)
Scenario: User asks "React or Vue for a startup?" Expected: Recognizes 2 options, redirects to Pros/Cons, does NOT build full matrix. Pass criteria: Skips matrix, offers simpler alternative.
Eval 3: Non-Compensatory Filter
Scenario: User asks "pick a cloud vendor" with constraint "must support HIPAA." Expected: Identifies HIPAA as non-negotiable, filters vendors BEFORE scoring. Pass criteria: Applies filter first, then matrix only on remaining options.
Resources
- Detailed Research Notes
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

