Confidence signal
Skill aarshsharma2803-stack/optimusprime/skills/confidence-signal
The session state protocol for AI coding. Hook-level scope enforcement, cross-session memory, contradiction detection, and predictive context - Claude is stateless, your project isn't.
npx -y skills add aarshsharma2803-stack/optimusprime --skill confidence-signalAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Activates when Claude has internal uncertainty below 70% about whether the chosen approach is correct before executing. Triggers on: uncertainty about correctness of a complex algorithm with subtle edge cases; uncertainty whether a refactor will silently break callers identified by dependency-analyzer; requirement ambiguity where two interpretations lead to very different implementations and the wrong choice has significant rework cost; an approach similar to one in .optimusprime/attempts.md (previously failed this session). Does NOT activate for HIGH confidence. Only fires before executing, not after.
SKILL.md
1.3 KB, as published. Nobody here has run it
When confidence < 70% before executing:
Output exactly:
CONFIDENCE: LOW — [one sentence naming the specific risk] — proceed or clarify?
Wait for user response. Do not execute until answered.
When confidence ≥ 70%: proceed silently. Never output anything about confidence level.
Rules:
- Never say "CONFIDENCE: HIGH" — silence means high confidence.
- Name the specific risk: "renaming
process()will break 4 callers in services/" not "I'm unsure". - After user says "proceed": execute immediately, no further output.
- Threshold is strict: 70%. Mild uncertainty does not qualify.