tradeoff-evaluation
Use when metrics conflict or feature has mixed results - evaluates short-term vs long-term impact, segments by user lifecycle, aligns with strategic positioning, and explores mitigation strategies before binary rollback decisions
Profile →npx skills add majiayu000/claude-skill-registry --skill tradeoff-evaluation-jayhjenkins-productosv0-2 --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.
What it does
Makes informed decisions when improving one metric harms another or when A/B results are mixed, avoiding binary ship/rollback thinking by exploring nuanced approaches to preserve gains while addressing losses.
How it works
Activates when metrics conflict or mixed results occur, and follows a structured process:
- Identify the conflict: determine which metrics rose or fell, magnitude, and significance, and document the trade-off.
- Apply strategic lens: assess alignment with strategic positioning, long-term competitiveness, and core value proposition to rank metrics by importance.
- Segment the analysis: analyze how trade-offs vary by user lifecycle and segments;
- Identify mitigation options: brainstorm 3-5 approaches to modify, segment rollout, or compensate with other features.
- Make recommendation: choose from four options (Ship fully, Ship to segments, Iterate first, Rollback) with rationale and risks, and plan monitoring.
When to use it
Activates automatically under conditions like:
- A/B test shows some metrics up, others down
- Feature launched with mixed performance
- Optimizing one goal reduces another
- Stakeholders disagree on ship/no-ship decision
- Redesign shifted user behavior unexpectedly
- tradeoff-decision workflow evaluates mixed results
- metrics-definition workflow identifies counter-metrics
- Need to choose between competing priorities
What it can touch
Not applicable in this excerpt; tool names or scripts are not enumerated beyond implied workflows and segmentation logic.
Caveats
- Focuses on avoiding binary outcomes and exploring mitigations before rollback.
- Emphasizes long-term strategic value and flywheel effects over single-metric gains.
- Requires segmentation and mitigation brainstorming; outcomes rely on documented analysis and monitoring plans.
# Trade-off Evaluation ## Purpose Make informed decisions when improving one metric harms another, or when A/B test results are mixed. Avoids binary thinking (ship vs. rollback) by exploring nuanced approaches that preserve gains while addressing losses. ## When to Use This Skill Activate automatically when: - A/B test shows some metrics up, others down - Feature launched with mixed performance - Optimizing for one goal reduces another - Stakeholders disagree on ship/no-ship decision - Redesign shifted user behavior unexpectedly - `tradeoff-decision` workflow evaluates mixed results - `metrics-definition` workflow identifies counter-metrics - Need to choose between competing priorities **When NOT to use:** - All metrics clearly positive (ship it) - All metrics clearly negative (don't ship) - Harm is minor and acceptable (make call quickly) - Decision is time-sensitive and stakes are low ## Core Principles ### 1. Default to "It Depends" **Avoid binary yes/no thinking:** - ❌ "Should we ship this? Yes or No" - ✓ "Should we ship this to everyone, some segments, or iterate first?" **Segmentation thinking:** - New users vs. established users - Power users vs. casual users - Free tier vs.
- Purpose
- When to Use This Skill
- Core Principles
- 1. Default to "It Depends"
- 2. Long-Term Strategic Value > Short-Term Gains
- 3. Mitigation Before Rollback
- Decision Frameworks
- Framework 1: User Lifecycle Segmentation
- Framework 2: Strategic Positioning Alignment
- Framework 3: Flywheel Impact Analysis
- Framework 4: Revenue Impact (Short vs. Long-Term)
- Mitigation Strategies Catalog
- Strategy 1: Segmented Rollout
- Strategy 2: Targeted Modifications
What does the tradeoff-evaluation skill do?
Use when metrics conflict or feature has mixed results - evaluates short-term vs long-term impact, segments by user lifecycle, aligns with strategic positioning, and explores mitigation strategies before binary rollback decisions
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill tradeoff-evaluation-jayhjenkins-productosv0-2 --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.