skills/decision-toolkit/SKILL.md
Generate structured decision-making tools — step-by-step guides, bias checkers, scenario explorers, and interactive dashboards. Use when facing significant choices requiring systematic analysis. Supports multiple cognitive styles and output formats.
npx skillsauth add alexdcd/mafia-claude-skills decision-toolkitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Create structured decision support materials that help humans think through significant choices systematically. This skill produces interactive tools, not just analysis — empowering the decision-maker rather than deciding for them.
Different people process decisions differently:
| Style | Accommodation | |-------|---------------| | Analytical | Numbers, matrices, weighted scores | | Intuitive | Gut-check prompts, "how does this feel?" | | Visual | Diagrams, progress bars, color coding | | Verbal | Written summaries, question prompts | | Sequential | Step-by-step wizard flow | | Global | Dashboard overview option |
Invoke this skill when user faces:
Not for: Trivial decisions, emergency responses, or when user just needs information.
Should I pursue this opportunity?
Where should I invest my time/money/attention?
What could go wrong and is it worth it?
Which option among alternatives?
Nine steps, each focused on one dimension:
┌─────────────────────────────────────────────────────────────┐
│ 1. CONTEXT What is the decision? │
│ 2. FIRST PRINCIPLES Does this solve a real problem? │
│ 3. TIMING Is now the right moment? │
│ 4. STAKEHOLDERS Who else is involved? Are they stable? │
│ 5. BIASES What might cloud my judgment? │
│ 6. OPPORTUNITY COST What am I giving up? │
│ 7. SCENARIOS What could happen? │
│ 8. QUESTIONS What do I still need to learn? │
│ 9. SYNTHESIS Summary + decision │
└─────────────────────────────────────────────────────────────┘
Step-by-step wizard with:
For offline/text-based use:
For audio consumption:
For documentation/sharing:
1. What problem does this solve?
2. Can I solve it myself?
3. Is this the best solution?
4. What assumptions am I making?
5. If starting fresh today, would I choose this?
□ FOMO — Am I afraid of missing out?
□ Sunk Cost — Am I factoring past investment?
□ Authority — Am I deferring to credentials?
□ Social Proof — Am I following the crowd?
□ Commitment — Do I feel locked in by past statements?
□ Optimism — Am I assuming problems will resolve?
□ Recency — Am I overweighting recent events?
□ Confirmation — Am I seeking validating info only?
□ Shiny Object — Is novelty distracting me?
□ Loss Aversion — Am I overweighting potential losses?
Hours/week × Weeks × Hourly rate = Direct cost
+ What else could those hours produce?
+ What relationships/opportunities might suffer?
= True opportunity cost
| Scenario | Probability | Outcome | Expected Value |
|----------|-------------|---------|----------------|
| Worst | X% | ... | ... |
| Bad | X% | ... | ... |
| Neutral | X% | ... | ... |
| Good | X% | ... | ... |
| Best | X% | ... | ... |
Imagine it's [future date]. This decision failed. Why?
Possible causes:
1. ...
2. ...
3. ...
Which causes are within my control?
Which warning signs should I watch for?
How will I feel about this decision in:
- 10 minutes?
- 10 months?
- 10 years?
Imagine you're 80 looking back.
Would you regret doing this?
Would you regret NOT doing this?
Ask user for:
Or extract from existing documents (meeting transcripts, notes).
Based on user preference and context:
Use templates in templates/ directory:
decision-guide-template.html — Full interactive wizarddecision-framework.md — Text-based analysisdecision-voice-summary.md — Audio script templateReplace placeholders:
{{DECISION_TITLE}} — What's being decided{{CONTEXT}} — Background information{{OPTIONS}} — Available choices{{STAKEHOLDERS}} — People/teams involved{{TIMELINE}} — Relevant dates{{FACTORS}} — Key evaluation criteriaIf using Agency brand:
<main role="main" aria-label="Decision Guide">
<nav aria-label="Progress">
<ol role="list">...</ol>
</nav>
<section aria-labelledby="step-title">
<h1 id="step-title">...</h1>
</section>
</main>
// Ensure all interactive elements are focusable
// Tab order follows visual order
// Enter/Space activate buttons
// Arrow keys navigate options
<div role="status" aria-live="polite" id="announcer">
<!-- Announce step changes, selections, results -->
</div>
/* Minimum 4.5:1 for normal text, 3:1 for large text */
--text-on-light: #000000; /* 21:1 on white */
--text-on-dark: #ffffff; /* 21:1 on black */
--text-on-primary: #ffffff; /* Check each color */
@media (prefers-reduced-motion: reduce) {
* {
animation: none !important;
transition: none !important;
}
}
User: Analyze this meeting transcript and create a decision toolkit
Claude: [Extracts decision, stakeholders, options from transcript]
[Generates interactive HTML guide]
[Creates voice summary]
User: I need to decide whether to take a new job offer
Claude: [Asks clarifying questions]
[Generates decision framework]
[Customizes for career decision type]
User: Help me think through this partnership decision, just give me the frameworks
Claude: [Provides markdown framework]
[Skips interactive tool]
[Focuses on key questions]
SKILL.md — This filetemplates/decision-guide-template.html — Interactive wizard templatetemplates/decision-framework.md — Text-based analysis templatetemplates/decision-voice-summary.md — Audio script templatereferences/bias-encyclopedia.md — Detailed bias descriptionsreferences/framework-deep-dives.md — Extended framework explanationsWorks well with:
Context: Initial skill creation from Synthius decision session
Key Insight: Dashboard-everything-at-once overwhelms. Step-by-step wizard with one concept per screen dramatically improves usability.
Architecture: 9-step journey covering all major decision dimensions. State object persists selections across steps. Summary aggregates everything.
Accessibility Note: High contrast neobrutalism actually helps accessibility — clear borders, distinct states, no subtle gradients.
tools
Auditoría defensiva para repositorios AI-native. Usar SIEMPRE que el usuario quiera revisar un repo antes de lanzar, mergear, actualizar dependencias, migrar package manager, configurar un agente IA, MCP, Claude/Cursor/Codex/OpenClaw, o cuando mencione supply chain, prompt injection, secretos, GitHub Actions, npm/pnpm, paquetes maliciosos, scripts peligrosos, o riesgos de seguridad en repos con IA. Activar también si el usuario dice "revisa el repo", "está seguro esto", "antes de producción", "audita el PR" o cualquier variación.
development
Use when given a detailed implementation plan from a frontier AI to execute inside OpenCode with non-frontier coding models. Validates the plan against the real repository, breaks it into safe steps, verifies each step, inspects diffs, and prevents destructive changes. Triggers on: receiving a multi-step plan from Claude Opus/GPT-5/etc., executing a pre-written spec, implementing a detailed PR description, or being told to "execute this plan step by step."
development
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
tools
Generates optimized prompts for any AI tool. Use when writing, fixing, improving, or adapting a prompt for LLM, Cursor, Midjourney, image AI, video AI, coding agents, or any other AI tool.