evaluating-trade-offs
Evaluate trade-offs and produce a Trade-off Evaluation Pack (trade-off brief, options+criteria matrix, all-in cost/opportunity cost table, impact ranges, recommendation, stop/continue triggers). Use for tradeoff/trade-off, pros and cons, cost-benefit, opportunity cost, build vs buy, ship fast vs ship better, continue vs stop (sunk costs). Category: Leadership.
npx skills add majiayu000/claude-skill-registry --skill evaluating-trade-offs --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Evaluating Trade-offs ## Scope **Covers** - Turning an ambiguous “pros/cons” debate into a decision-ready **trade-off evaluation** - Comparing options using **all-in cost** (not just dollars) and explicit **opportunity cost** - Using **order-of-magnitude estimates** (ranges + confidence) instead of false precision - Stress-testing decisions with **thought experiments** (pre-mortems, reversibility, “worse first” dips) - Avoiding sunk-cost traps with a clean **stop/continue** decision rule **When to use** - “Help me evaluate this trade-off and recommend a path.” - “Create a pros/cons that actually leads to a decision.” - “Compare options with cost/impact ranges and key assumptions.” - “We’re debating speed vs quality—what’s the right trade and how do we manage the dip?” - “Should we keep investing in this project, or stop? (Sunk cost question.)” **When NOT to use** - You need to clarify what problem you’re solving (use `problem-definition`). - You need a full cross-functional decision process (use `running-decision-processes`). - You’re prioritizing across many initiatives (use `prioritizing-roadmap`). - You’re cutting scope to hit a date/timebox (use `scoping-cutting`). - The deci
- Scope
- Inputs
- Outputs (deliverables)
- Workflow (7 steps)
- 1) Frame the trade-off (make it decidable)
- 2) Define what you’re optimizing (criteria + horizon)
- 3) Build the all-in cost + opportunity cost view
- 4) Estimate impact with ranges (avoid false precision)
- 5) Run “thought experiments” (think more, build less)
- 6) Account for “worse first” + sunk costs
- 7) Recommend, commit, and quality-gate
- Quality gate (required)
- Examples
What does the evaluating-trade-offs skill do?
Evaluate trade-offs and produce a Trade-off Evaluation Pack (trade-off brief, options+criteria matrix, all-in cost/opportunity cost table, impact ranges, recommendation, stop/continue triggers). Use for tradeoff/trade-off, pros and cons, cost-benefit, opportunity cost, build vs buy, ship fast vs ship better, continue vs stop (sunk costs). Category: Leadership.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill evaluating-trade-offs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.