skills/multi-brain-score/SKILL.md
Confidence scoring overlay for multi-brain decisions. Each perspective rates its own confidence (1-10) with justification. Consensus uses scores as weights, flags low-confidence areas, and surfaces uncertainty explicitly.
npx skillsauth add fatih-developer/fth-skills multi-brain-scoreInstall 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.
Add quantified confidence scoring to any multi-brain decision. Each perspective rates its own confidence, and the consensus uses scores as decision weights. Uncertainty becomes visible instead of hidden.
1. Run base multi-brain (3 perspectives)
2. Each instance scores its confidence (1-10)
3. Weighted consensus based on scores
4. Flag uncertainty zones
5. Produce full output with scores visible
Each instance provides their perspective plus a confidence score:
## 🧠 Brainstorm (Scored)
**Instance A — Creative:** (Confidence: 6/10)
[2-3 sentences]
_Confidence rationale: Novel approach but limited precedent in production._
**Instance B — Pragmatic:** (Confidence: 9/10)
[2-3 sentences]
_Confidence rationale: Well-established pattern, used this successfully before._
**Instance C — Comprehensive:** (Confidence: 7/10)
[2-3 sentences]
_Confidence rationale: Good coverage of risks but missing data on edge case X._
Before consensus, analyze the confidence landscape:
## 📊 Confidence Analysis
| Instance | Score | Strength | Weakness |
|----------|-------|----------|----------|
| A — Creative | 6/10 | High potential impact | Unproven approach |
| B — Pragmatic | 9/10 | Battle-tested | May miss innovation |
| C — Comprehensive | 7/10 | Risk-aware | Incomplete data |
**Average Confidence:** 7.3/10
**Spread:** 3 points (moderate disagreement)
**Highest Confidence:** Instance B
Use confidence scores to weight the consensus:
## ⚖️ Weighted Consensus
**Primary direction:** [Based on highest-confidence perspective]
**Modified by:** [Elements from medium-confidence perspectives]
**Flagged for research:** [Low-confidence areas that need validation]
**Overall Decision Confidence:** [Weighted average]/10
If any perspective scores below 5, or if the spread between scores is > 4:
> ⚠️ **Uncertainty Alert:** [Description of what is uncertain and what would resolve it]
Mandatory: The final response must include all scored perspectives, the confidence analysis table, the weighted consensus, any uncertainty flags, and the complete deliverable.
| Score | Meaning | When to Use | |-------|---------|-------------| | 9-10 | Near-certain | Strong evidence, proven pattern, minimal unknowns | | 7-8 | Confident | Good reasoning, some minor unknowns | | 5-6 | Moderate | Reasonable approach but notable gaps | | 3-4 | Low | Speculative, lacks supporting evidence | | 1-2 | Guess | No solid basis, flagging for transparency |
references/EXAMPLES.md for scored decision examples.tools
Create, optimize, critique, and structure prompts for AI systems. Use this skill whenever the user is designing or improving a prompt, system prompt, coding prompt, image prompt, evaluation rubric, agent prompt, workflow prompt, or MCP-oriented prompt package. Also use it when the user asks to turn vague AI behavior into a precise instruction set, tool policy, agent spec, or prompt architecture.
testing
Assumption-first architecture review skill to stress-test project plans and expose hidden risks.
testing
Enforce and manage DESIGN.md specifications, extract design systems from URLs, and combine design reasoning with token roles to prevent drift.
testing
Forces the agent to act with a Claude-like product mindset, prioritizing user journey, UX states, and visual quality before coding.