Confidence Honesty
Force honest confidence assessment before claiming conclusions. Triggers on 'root cause identified', 'problem identified', 'complete clarity'. Express confidence as percentage, explain what's stopping 100%, validate assumptions before presenting.
npx skills add majiayu000/claude-skill-registry --skill confidence-honesty --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.
# GitHub Copilot Skill: confidence-honesty > **Note:** This skill has been adapted from [claude-skillz](https://github.com/NTCoding/claude-skillz) > for use with GitHub Copilot Agent Skills. --- # Confidence Honesty ## The Problem Claude builds detailed, well-structured analyses that *look* thorough—then presents them with phrases like "complete clarity" or "root cause identified." Users reasonably trust this confidence. They act on it, communicate it to stakeholders, make decisions. Then new evidence appears and invalidates the entire hypothesis. **The harm:** - User trusted a conclusion that was actually ~40% confident - Time wasted on wrong direction - Stakeholders were misinformed - Trust in Claude's analysis erodes **Why this happens:** Claude conflates *explanation quality* with *evidence quality*. A thorough, well-reasoned analysis feels like certainty—but reasoning without verified evidence is just speculation with extra steps. ## The Solution Force explicit confidence assessment before claiming conclusions: 1. Express confidence as a percentage (not vague certainty) 2. Show the math: what evidence adds confidence, what gaps subtract it 3. Mandatory "Why not 100%?" for anyt
- The Problem
- The Solution
- Critical Rules
- When This Triggers
- Confidence Levels
- Pre-Conclusion Checkpoint
- 1. Evidence Inventory
- 2. Falsifiability Check
- 3. Assumption Audit
- 4. Alternative Possibilities
- 5. Validation Opportunities
- Confidence Scoring
- Response Format
- Examples
What does the Confidence Honesty skill do?
Force honest confidence assessment before claiming conclusions. Triggers on 'root cause identified', 'problem identified', 'complete clarity'. Express confidence as percentage, explain what's stopping 100%, validate assumptions before presenting.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill confidence-honesty --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.