aget-assess-tradeoffs
Analyze trade-offs between competing architectural concerns
npx skills add majiayu000/claude-skill-registry --skill aget-assess-tradeoffs --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.
# aget-assess-tradeoffs Analyze trade-offs between competing concerns and quality attributes. Provides structured decision support for architectural choices. ## Instructions When this skill is invoked: 1. **Identify Competing Concerns** - List quality attributes in tension - Document the options being considered - Note constraints and context 2. **Evaluate Options** - Rate each option against each quality attribute - Use consistent scale (1-5 or Low/Med/High) - Consider both immediate and long-term effects 3. **Assess Reversibility** - Classify decisions: One-way door vs. Two-way door - Note cost of changing later - Identify lock-in risks 4. **Formulate Recommendation** - Provide clear recommendation - Explain trade-off resolution rationale - Document rejected alternatives ## Output Format ```markdown ## Trade-off Analysis: [Decision Topic] ### Context [What decision needs to be made and why] ### Competing Concerns | Quality Attribute | Option A | Option B | Option C | |-------------------|:--------:|:--------:|:--------:| | Performance | ⭐⭐⭐ | ⭐⭐ | ⭐ | | Maintainability | ⭐ | ⭐⭐⭐ | ⭐⭐ | | Cost | ⭐⭐ | ⭐ | ⭐⭐⭐ | | Time to Market | ⭐ | ⭐⭐ | ⭐⭐⭐ | ### Reversibility Assessment | Option
- Instructions
- Output Format
- Constraints
- Related
What does the aget-assess-tradeoffs skill do?
Analyze trade-offs between competing architectural concerns
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill aget-assess-tradeoffs --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.