跳到正文
cccskills
免费在 GitHub 公开

confidence-scorer

Assign confidence scores (0-100) to every claim in a response. Helps users understand which parts are verified facts and which are educated guesses. Use when the user needs to know how much to trust each part of the answer.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md2.3 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Confidence Scorer

Assign a numerical confidence score to every claim, so users know exactly how much to trust each part of your response.

Scoring scale

ScoreMeaningExample
95-100Verified against code just now"src/auth.ts exports validateToken (I just read it)"
80-94Confirmed by search/tool output"Grep found 3 references to this function"
60-79Strong inference from evidence"Based on the error handling pattern, this likely..."
40-59Educated guess from general knowledge"Express middleware typically handles this by..."
20-39Uncertain, limited evidence"This might be related to the session config..."
0-19Speculation, no evidence"It could be a race condition, but I haven't checked"

How to apply

After making claims, add confidence annotations:

"The authentication flow works as follows:

  • Users hit /api/login which calls validateUser() [95 - read the route file]
  • Passwords are hashed with bcrypt [90 - confirmed in package.json]
  • Sessions are stored in Redis [70 - inferred from redis import, haven't confirmed config]
  • Session timeout is 24 hours [40 - common default, haven't checked actual config]"

Threshold rules

SituationMinimum score to state as fact
Code changes80+ (must have read the code)
Security advice90+ (must have verified)
Production commands95+ (must be certain)
Explanations60+ (inference OK if labeled)
Suggestions40+ (clearly framed as suggestions)

When to score

Use confidence scoring when:

  • The user asks "are you sure?"
  • You're giving advice that will be acted on
  • Multiple possible explanations exist
  • You're working with unfamiliar code
  • The stakes are high (production, security, data)

Improving low scores

If a claim scores below the threshold:

  1. Use tools to gather more evidence
  2. Read the relevant files
  3. Search for confirming/denying evidence
  4. Re-score based on new evidence
  5. If still low, state it as uncertain rather than fact

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Complete methodology for preventing AI hallucinations. Use when accuracy is critical and you need Claude to verify before claiming, cite before asserting, and admit uncertainty instead of guessing.

中文简介正在准备中。当前显示原文说明。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Transform rough ideas into solid designs through structured questioning

中文简介正在准备中。当前显示原文说明。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Canvas API Connection Skill

中文简介正在准备中。当前显示原文说明。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Forces every code-related claim to include file:line citations. No citation means the claim must be verified or removed. Use when building documentation, writing code reviews, or any output that others will rely on.

中文简介正在准备中。当前显示原文说明。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Forces Claude to extract exact quotes from files before making claims about them. Prevents hallucinations by grounding every statement in actual text from the codebase. Use when working with large files or unfamiliar code.

中文简介正在准备中。当前显示原文说明。

a-ariff/ariff-claude-plugins142026年3月29日 更新

Verify every claim from multiple independent angles -- code, docs, tests, git history. Use when you need high confidence that something is correct before acting on it.

中文简介正在准备中。当前显示原文说明。

a-ariff/ariff-claude-plugins142026年3月29日 更新

查看 a-ariff 的全部技能

报告此技能的问题