prioritize-by-impact
Use this skill when the user has a list of tasks and needs help deciding what to do first. Rank by impact and urgency — not order of mention — and surface the highest-leverage work.
68
Quality
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Prioritize by Impact
Not all tasks are equal — help the user focus on what matters most.
Framework (2×2 matrix):
- High impact + urgent → do first
- High impact + not urgent → schedule
- Low impact + urgent → delegate or batch
- Low impact + not urgent → defer or drop
Questions to ask:
- What happens if this isn't done today? This week?
- Which task unlocks the most other work when completed?
- Is there a hard deadline or dependency?
Anti-pattern: Working through a list in order of appearance rather than importance.
- Repository
- aiming-lab/MetaClaw
- Commit
922caf3
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.