confidence-gate SKILL.md skillA

confidence-gate from sara-star-quant/presence is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add sara-star-quant/presence/confidence-gate@git:20260426.243df5a

Pins git:20260426.243df5a in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
sara-star-quant/presence
Path
skills/confidence-gate/SKILL.md
Versions recorded
1
Latest version
git:20260426.243df5a, committed Apr 26, 2026
Size
2,682 bytes
Repository stars
8
License
Apache-2.0

When you're about to claim success ("fixed", "done", "works", "passing tests") at the end of a turn, verify the claim is backed by actual evidence in this session. presence's Stop hook will flag a success claim that has no recent test/build pass behind it. Be aware of this gate and either run the verification, or hedge the claim explicitly.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Confidence gate: claim what you can verify

`presence`'s Stop hook parses your final assistant message for unhedged success language. If it finds words like "fixed", "done", "works", "passing tests", and there's been an edit but no passing test/build event since that edit, it logs the discrepancy. In strict presets it also re-prompts you to verify before stopping.

## How to avoid the warning

Three options, in order of preference:

### 1. Actually verify

Run the test suite, build, lint, or whatever the project uses for verification, **before** declaring success. The presence event log captures `npm test`, `pytest`, `cargo test`, `tsc`, `next build`, and ~15 other common commands automatically. Running any of them creates a `test_pass` / `build_pass` event that satisfies the gate.

### 2. Hedge explicitly

If you can't run the verification (no tests in the project, network-isolated environment, user wants quick scaffold without running CI), hedge the claim:

- "I think this fixes the issue, but I haven't run the tests."
- "This should work; needs verification."
- "Untested: ..."

These hedges are recognized by the gate and disable the warning.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add sara-star-quant/presence/confidence-gate@sha256:e3a0a791e1d2ad6d

The line at the top of this page pins the label git:20260426.243df5a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_rsd5api5qhrjxftd.svg)](https://markdownregistry.com/a/art_rsd5api5qhrjxftd)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Apr 26, 2026.

versioncommittedcommitsizeaudit
git:20260426.243df5a latest2026-04-26 243df5a 2,682 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (2682 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

sara-star-quant/presence · 8 stars · license Apache-2.0 · pushed 2026-10-30 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_rsd5api5qhrjxftd
GET https://markdownregistry.com/api/v1/resolve?ref=sara-star-quant/presence/confidence-gate
GET https://markdownregistry.com/api/v1/blob/e3a0a791e1d2ad6d23d91f447df00c92144a2c0e9bf8ec13960e477e1335db9b

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from sara-star-quant/presence

llms.txt llms.txt file
sara-star-quant/presence · llms.txt
git:20261030.1901e90 · audit B · 8 stars
outcome-check SKILL.md skill
sara-star-quant/presence · skills/outcome-check/SKILL.md · When you're about to claim a previous fix worked, or are tempted to repeat an approach Claude Code has tried in this…
git:20260426.243df5a · audit A · 8 stars
project-model SKILL.md skill
sara-star-quant/presence · skills/project-model/SKILL.md · When working in a codebase you've touched before, consult and update the persistent project model maintained by…
git:20260426.243df5a · audit A · 8 stars

Every file in sara-star-quant/presence

Browse by kind, by grade A, or by owner.