Agent skill · operations · sickn33
dos-verify-done-claims
Before accepting an agent's 'done / shipped / fixed' claim, verify it against ground truth (git ancestry + the commit's own diff) using the DOS kernel's `dos verify` and `dos commit-audit` — never the agent's own narration.
Why this skill is useful
Adds specific commands and workflows for verifying AI agent claims against git history that the AI wouldn't reliably generate on its own.
What it needs
Requires dos-kernel installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Verify done-claims against ground truth, not the agent's word Overview When an AI agent says "done", "shipped", or "fixed", that is a claim, not a fact — and a claim the agent checks by re-reading its own work is consistency, not grounding. This skill replaces that self-report with a verdict from a witness the agent did not author: it shells the DOS kernel (dos verify, dos commit-audit) to confirm the claimed effect from git ancestry and the commit's actual diff. DOS is deterministic — no API key, no LLM. The verdict is git-only and offline as used here; the one exception is dos verify in a workspace that wires a CI oracle, which --no-ci suppresses (see Security & Safety Notes). This skill adapts the DOS reference "witness-claim" pattern (anthony-chaudhary/dos-kernel) into a host-agnostic screenplay. When to Use This Skill Use when an agent reports a task/phase/feature as complete and you want that "done" confirmed from evidence before building on it. Use right after a commit, to confirm the commit's message matches its diff (catch a fix: that only touched a README, or a "tests pass" that deleted the assertions). Use when folding many sub-agents' results — verify each claimed effect instead of trusting the return string. Do not use it to judge whether code is correct — that is what the test suite is for. This skill checks did-the-claimed-thing-actually-ship. How It Works Step 1: Install the kernel (once) Step 2: Audit the latest commit's claim vs its diff A commit subject is forgeable (whoever wrote the message authored it); the files it touched are not (git did). dos commit-audit grades the subject against the actual diff: commit-audit --json prints a JSON array of audited commits (one element even for a single HEAD), so read verdict from the first element — e.g. dos commit-audit --workspace . HEAD --json jq -r '.[0].verdict'. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/dos-verify-done-claims