agentleFS
varunk130varunk130/claude-code-skills/skills/ai-ux-design/uncertainty-and-explainability-patterns/SKILL.md

uncertainty-and-explainability-patterns

Skill1 starsChanged 20 days agoMITView on GitHub

Selects how an Artificial Intelligence (AI) feature should communicate confidence, citations, sources, and reasoning for a specific audience and risk level, producing a pattern specification with display rules, thresholds, and an anti-pattern check covering false precision, explanation theater, and citation laundering. Use when deciding whether to show confidence scores; designing citations for a Retrieval-Augmented Generation (RAG) answer; explaining why a model made a recommendation; or users over-trust or ignore AI output.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify calibration before showing any numeric confidence

    line 120
  2. Distinctive:

    Test whether the pattern changes user reliance in the right direction

    line 124
  3. Distinctive:

    Use more decimal places than the evidence supports

    line 128

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Uncertainty and Explainability Patterns

The goal of an explanation is not to look transparent. It is to help the user decide whether to rely on the output.

What this skill is

A pattern-selection workflow that matches how uncertainty and reasoning are shown to who is looking and what is at stake. It profiles the audience and decision, picks from a catalog of confidence, provenance, and reasoning patterns, sets display thresholds, and checks the design against common anti-patterns. The output is a specification a designer and engineer can implement consistently across a product.

What it solves

  • Confidence percentages that look precise but are not calibrated to real accuracy
  • Citation lists that link to sources which do not support the claim
  • Long reasoning dumps that users skip, adding noise without improving decisions
  • The same explanation shown to a novice consumer and an expert analyst
  • Users over-relying on AI output in high-stakes moments, or ignoring it in low-stakes ones

When to invoke

  • Deciding whether and how to display a confidence score or probability
  • Designing citations and source display for a search or retrieval answer
  • Explaining a model recommendation, ranking, classification, or flag
  • Regulatory or internal policy requires explainability for automated decisions
  • Research shows users accept wrong answers, or redo work the AI did correctly

Phase 1: Profile the audience and decision

FactorOptions
Audience expertiseNovice / Practitioner / Expert in the domain
Statistical literacyLow / Medium / High
Decision stakesLow (preference) / Medium (rework) / High (money, health, legal, safety)
Time pressureGlanceable (seconds) / Considered (minutes) / Deliberate (audit, review)
User can verify independently?Easily / With effort / Not practically
AccountabilityWho answers for the decision if the AI is wrong

The core question per decision: what does the user need to know to decide whether to rely on this output?

Phase 2: Measure before you show

Uncertainty display is only honest if the underlying signal is real.

Signal sourceUse for display?
Calibrated probability (validated against held-out accuracy)Yes, numeric display allowed
Retrieval relevance or grounding check scoreYes, as categorical bands, not raw numbers
Self-consistency across multiple samplesYes, as agreement ("3 of 3 runs agreed")
Model self-reported certainty in textNo, not without calibration evidence
No signal availableShow provenance instead of confidence
Calibration check: for outputs labeled "High confidence," measured accuracy should be within 5 points of the implied rate
If uncalibrated, collapse to 2-3 categorical bands or remove the confidence display

Phase 3: Select confidence patterns

PatternBest forAvoid when
Categorical band (High / Medium / Low)Novices, glanceable decisionsBands are not backed by measured thresholds
Numeric probabilityExperts with calibrated modelsLow statistical literacy or uncalibrated scores
Frequency framing ("Right about 8 in 10 times for cases like this")Mixed audiences, risk communicationVery small sample sizes
Visual emphasis (dimming or underlining weak claims)Long generated textColor is the only signal (accessibility)
Alternatives shown (top 3 options)Ambiguous inputs, classificationUsers need a single action
Abstain or askConfidence below threshold on high stakesLow stakes where a best guess is fine

Threshold rule: define the confidence level below which the feature abstains or asks rather than answers. For high-stakes decisions this matters more than any display choice.

Phase 4: Select provenance and reasoning patterns

PatternWhat it showsBest for
Inline citationClaim-level link to the supporting passageFactual answers, research, policy questions
Source cardTitle, owner, date, and type of each sourceJudging source quality
Quote highlightThe exact passage that supports the claimHigh-stakes facts users must verify
Key-factor explanationTop 3 inputs that drove a recommendationScores, rankings, risk flags
Counterfactual"Would change if X were different"Decisions users want to contest or improve
Step summaryShort list of steps the agent tookAgent actions and multi-step tasks
Full trace (on demand)Detailed reasoning or tool logExperts, debugging, audit

Match by profile:

ProfileDefault pattern set
Novice, low stakesCategorical band or none; source card on demand
Novice, high stakesAbstain-or-ask, quote highlight, clear path to a human
Expert, low stakesInline citations, full trace on demand
Expert, high stakesCalibrated numeric confidence, quote highlight, counterfactual, audit trace

Layer it: one glanceable signal by default, evidence one click away, full trace for those who want it.

Phase 5: Run the anti-pattern check

Anti-patternSymptomFix
False precision"87.3 percent confident" from an uncalibrated modelUse bands or remove
Explanation theaterLong reasoning text no one reads and no one validatedReplace with key factors or step summary
Citation launderingLink present but passage does not support the claimClaim-level grounding check; show the quote
Uniform confidenceEvery answer styled the same regardless of evidenceVary treatment by evidence strength
Disclaimer wallpaper"AI can make mistakes" on every screenSpecific, contextual cues where risk is real
Post-hoc rationalizationExplanation generated separately from the decisionExplain from the actual inputs and features used
Color-only signalsRed, yellow, or green with no textAdd labels and icons

Output

  • Audience and decision profile per surface
  • Signal inventory with calibration status
  • Selected confidence, provenance, and reasoning patterns per surface
  • Abstain-or-ask thresholds for high-stakes decisions
  • Layering spec (default, one click, full trace)
  • Anti-pattern checklist with pass or fail and fixes

Operating rules

Always

  • Verify calibration before showing any numeric confidence
  • Tie every citation to the specific claim it supports
  • Set a threshold below which the system abstains or asks
  • Layer explanations: glanceable first, detail on demand
  • Test whether the pattern changes user reliance in the right direction

Never

  • Display model self-reported certainty as if it were a measured probability
  • Use more decimal places than the evidence supports
  • Count the number of citations as a proxy for answer quality
  • Show the same explanation depth to every audience
  • Rely on a generic disclaimer as the trust mechanism

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.