本文へ移動
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(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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 のスキルをすべて見る

このスキルの問題を報告する