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.
Install
/plugin marketplace add NTCoding/claude-skillzThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add NTCoding/claude-skillz --skill confidence-honestygit clone --depth 1 https://github.com/NTCoding/claude-skillz.git /tmp/claude-skillz
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skillz/confidence-honesty ~/.claude/skills/confidence-honestyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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 anything below 95% 4. Self-validate: if you can gather more evidence yourself, do it before presenting ## Critical Rules 🚨 **EXPRESS CONFIDENCE AS A PERCENTAGE.** Every conclusion needs a specific confidence level, not vague certainty. 🚨 **EXPLAIN WHAT'S STOPPING 100%.** For any confidence below 95%, you MUST explain the gaps. Non-negotiable. 🚨 **VALIDATE BEFORE PRESENTING.** If you can gather more evidence yourself, DO IT. Don't return to user with unvalidated hypotheses.
Details
- Skill name
confidence-honesty- Repository
- NTCoding/claude-skillz
- Path
confidence-honesty/SKILL.md- Repo updated
- 24 March 2026
FAQ
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 the Confidence Honesty skill?
Claude Code plugin: /plugin marketplace add NTCoding/claude-skillz. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Confidence Honesty popular?
It lives in NTCoding/claude-skillz, which has 365 GitHub stars and 47 forks.
Related skills
Architect Refine Critique
365NTCoding/claude-skillz
Three-phase design review. Chain architect → refiner → critique subagents. Triggers on: 'design review', 'architecture review', '/arc', system design proposals, significant refactoring decisions, new service or module design.
Challenge That
365NTCoding/claude-skillz
Force critical evaluation of proposals, requirements, or decisions by analyzing from multiple adversarial perspectives. Triggers on: accepting a proposal without pushback, 'sounds good', 'let's go with', design decisions with unstated tradeoffs, unchallenged assumptions, premature consensus. Invoke with /challenge-that.
Concise Output
365NTCoding/claude-skillz
Enforces brevity and signal-over-noise in all outputs. Eliminates verbose explanations, filler phrases, and unnecessary elaboration. Triggers on: every response (governs output length and density when loaded).
Critical Peer Personality
365NTCoding/claude-skillz
Professional, skeptical communication style. Never over-enthusiastic, verifies before agreeing, challenges constructively, proposes instead of asking preferences. Expert peer who coaches, not serves. Triggers on: composing responses, agreeing with user, making recommendations, giving feedback.
Questions Are Not Instructions
365NTCoding/claude-skillz
Engage with what the user said before taking action. Triggers on: questions ('?'), feedback ('this is wrong', 'that doesn't look right', 'there are issues'), challenges ('why did you', 'have you considered'), criticism ('this isn't working', 'I don't like'), observations ('I notice', 'it seems like'), naming a skill or concept. STOP and respond to the user's actual words before doing anything.
Context Management Context Save
514Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
Use when working with context management context save
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.