# SKILL — Verify Work

## When to use
Every time a specialist returns work, **before** I accept it or report it to Sam. I trust
nothing on a claim alone.

## Workflow
1. **Check against the spec.** Walk each success criterion from the delegation spec and
   confirm it's actually met — one by one, explicitly.
2. **Demand evidence, not claims.** "Done" is not proof. For every claim, get the proof:
   the file exists, the source is cited and real, the command output backs it up.
3. **Scan for AI failure modes.** Be suspicious of:
   - Hallucinated facts, citations, packages, or URLs that don't exist.
   - "Success" declared without evidence; steps skipped and glossed over.
   - Checks/tests that assert nothing; errors swallowed instead of surfaced.
   - Confident prose hiding an unverified assumption.
4. **Cross-check against our source of truth** using read-only tools only:
   - Read the relevant repo doc; `git status` / `git log` to confirm state;
     `ls` / `cat` to confirm a file exists and contains what's claimed; `docker ps` to
     confirm a service is up.
5. **Verdict:** accept · send back with the *specific* missing evidence · or escalate to Sam.

## Quality standards
- Never accept "done" without traceable evidence.
- Every factual claim must be checkable against a source or a command output.
- If I can't verify it, I say so plainly — I don't launder a guess into a fact.

## Tools (read-only)
File read access; read-only shell (`git status`/`log`, `ls`, `cat`, `docker ps`). No writes,
no deletes, no installs, no network. See `../../TOOLS.md`.

## Limits
I verify **truth, completeness, and consistency with our facts** — not a line-by-line code
or security audit. Deep code/security review is a future specialist's job; I route it there.

## Upstream sources & updates
- ⚠️ [fivetaku/fablize](https://github.com/fivetaku/fablize) — evidence/verification as procedure (principle authored above; license unspecified, not installed).
- ⚠️ [amElnagdy/guard-skills](https://github.com/amElnagdy/guard-skills) — the 14 AI failure modes to distrust (authored above).
- ⚠️ [golbin/agent-skills](https://github.com/golbin/agent-skills) — review implementation vs spec.
- ⚠️ [ronikobrosly/RigorLoop](https://github.com/ronikobrosly/RigorLoop) — treat work as a reviewable artifact.
- If any of these add an OSI license, promote in `../README.md` and install via `npx skills add <owner>/<repo>`.
