decide
Skill25 starsChanged 7 days agoMITView on GitHub
Apply a 12-lens decision framework. Use when weighing options, making a call, or asking for help deciding.
51 other projects use a version of this.
Adopted by
Most recently taken up by
- aditya-vermax/skillstheir own version, first seen Nov 8, 2026
- vimkim/my-skillstheir own version, first seen Nov 8, 2026
- yuri-xyz/skillstheir own version, first seen Nov 8, 2026
- blamechris/chroxytheir own version, first seen Nov 8, 2026
- dirien/yet-another-agent-harnesstheir own version, first seen Nov 8, 2026
- Integralist/agent-skillstheir own version, first seen Nov 6, 2026
Used with
Projects with it also use redesign, weekly and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
arjunkshahSkillredesign
Redesign existing interfaces to premium quality while preserving product goals and functional behavior.
Also in 3 projects that use this
gaiaaiagentSkillweekly
Generate a weekly digest rolling up dailies into higher-level pattern analysis
Also in 3 projects that use this
SethGammonSkillexperiment
Automated optimization loop with scalar fitness function. Proposes changes in isolated worktrees, measures with a metric command, keeps improvements, discards failures. Supports convergence detection and diminishing returns.
Also in 3 projects that use this
kv0906Skillinbox
Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.
Also in 3 projects that use this
genomewalkerSkillhealth
Soul system health check with remediation
Also in 3 projects that use this
AWSSkillmap
Map verified service capabilities against customer-provided control framework and threat model. Produces mapping-results.json, controls-catalog.md, and framework-mapping.md. Supports pluggable frameworks: CCMv4, NIST 800-53, CIS Benchmarks, ISO 27001, etc. Split into 4 focused sub-skills for better accuracy; this skill orchestrates them.
Also in 3 projects that use this
Other versions51 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 51
- ParadevAI/Paradev★ 16ksame name
- superset-sh/superset★ 16ksame name
- coreyhaines31/makerskills★ 893same name
- me2resh/apexyard★ 542same name
- menkesu/awesome-pm-skills★ 441same name
- BlockRunAI/blockrun-mcp★ 389same name
- kv0906/pm-kit★ 138same name
- Abilityai/cornelius★ 109same name
- me2resh/agent-decision-record★ 48same name
- seandavi/lifeos-template★ 46same name
41 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 repository71 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- llms.txtllms.txt
- agent-fitnessSkill
- body-checkSkill
- briefSkill
- capsule-compactSkill
- closeSkill
- codex-adapterSkill
- cognitive-updateSkill
- comms-summarizeSkill
- compact-noteSkill
- context-capsuleSkill
- context-hygieneSkill
- critique-planSkill
- deep-reconSkill
- DiagnoseSkill
- digestSkill
- dreamSkill
- EnvelopeSkill
- find-weaknessSkill
- First 10 MovesSkill
- first-winSkill
- frontend-slidesSkill
- Honesty CheckSkill
- humanize-docsSkill
- impeccableSkill
- learn-from-failureSkill
- LearnSkill
- memory-bridgeSkill
- meta-improveSkill
- meta-improve-vaultSkill
- nightly-close-paritySkill
- nightly-ledger-captureSkill
- nightlySkill
- openSkill
- operator-setupSkill
- orientSkill
- pauseSkill
- ponytailSkill
- port-specSkill
- PromoteSkill
- reconcileSkill
- research-deepSkill
- resumeSkill
- Sandbox RoutingSkill
- scout-vaultSkill
- Self-ReviewSkill
- semantic-searchSkill
- setupSkill
- ship-adapterSkill
- Skill AuditSkill
- skill-huntSkill
- skill-recallSkill
- solution-huntSkill
- sprite-specSkill
- startSkill
- statusSkill
- StuckSkill
- supersedeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 50 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Run any decision through the evaluation framework from system/04_decision_frameworks.md.
- Distinctive: line 54
If confidence is low, structure it as an experiment, not a commitment.
- Distinctive: line 55
If it's Level 3, present the analysis but explicitly say "this is your call."
- Distinctive: line 56
Always name the trade-off.
“Common” is measured: kept by at least 6 in 10 of the 50 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 Framework
Run any decision through the evaluation framework from system/04_decision_frameworks.md. Produces a structured recommendation.
Usage
/decide [decision or opportunity to evaluate]
Process
- Parse the decision — What's being decided? What are the options?
- Run relevant lenses — Not all 12 apply to every decision. Select the 4-6 most relevant:
- Leverage — disproportionate output?
- Alignment — advances an active priority?
- Reversibility — can it be undone?
- Time Sensitivity — does waiting cost anything?
- Revenue Impact — creates/protects/accelerates revenue?
- Asymmetry — large upside, bounded downside?
- Dependency — unblocks other work?
- Cost — money, time, attention?
- Compounding — gets better over time?
- Simplicity — simpler path available?
- Confidence — how certain are the inputs?
- Opportunity Cost — what are we NOT doing?
- Check against principal's decision framework —
system/14_decision_framework.md- Does it pass the pattern filter?
- Where does it sit in the priority stack?
- Does it pass the asymmetry test?
- Check authority level —
system/12_authority_matrix.md- Is this Level 1 (just do it), Level 2 (recommend), or Level 3 (human only)?
Output Format
DECISION: [What we're deciding]
OPTIONS: [A vs B vs C]
RECOMMENDATION: [What to do and why]
KEY LENSES: [3-4 lenses that drove the recommendation]
TRADE-OFF: [What we're giving up]
CONFIDENCE: [High / Medium / Low — and why]
AUTHORITY: [Level 1/2/3 — can the AIgent act or needs approval]
NEXT ACTION: [Specific immediate step]Rules
- Be direct. Recommend, don't waffle.
- If confidence is low, structure it as an experiment, not a commitment.
- If it's Level 3, present the analysis but explicitly say "this is your call."
- Always name the trade-off. Every yes is a no to something else.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

