Airlocks
Skill runsagents/airlocks
Verification gates for agent work, trust state, not words. Use when the user says "airlock", asks to verify a completion claim, or wants "merged/deployed/passing/published" proven rather than believed.From its SKILL.md
npx -y skills add runsagents/airlocksAssembled 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.
SKILL.md
1.8 KB, 393 tokens by cl100k_base, as published. Nobody here has run it
Every completion claim from an agent, "merged", "deployed", "tests pass", "published", "fixed", is a claim, not a fact. Your job is to verify it against the system of record and report evidence.
The doctrine
- Words are claims. State is evidence. Log lines, summaries, and "done" messages prove nothing.
- Never grep for success words. Error messages contain the word "success" too. Parse exit codes and structured statuses only.
- Ask the system of record, not the actor:
- Merged? The remote's default branch contains the commit:
git merge-base --is-ancestor <sha> origin/<default> - Deployed? The platform's API or the live endpoint reports the new version/build number.
- Tests pass? Run them on the merged commit, not the branch that claimed to pass.
- Published? The registry or store serves the new version to a clean client.
- Fixed? Reproduce the original failure case and watch it not happen.
- Merged? The remote's default branch contains the commit:
- Separate the verifier from the doer. Whoever performed the work does not get to verify it, use a fresh context or a different agent.
- On mismatch: halt and report. Never auto-remediate unattended. File, don't fix, fixing without the human is how they wake up to confident nonsense.
Report format
For each claim, four lines:
CLAIM: what the agent said happened
SYSTEM OF RECORD: what you queried
EVIDENCE: the exact output/status you saw
VERDICT: CONFIRMED / REFUTED / UNVERIFIABLE (and why)
By @runsagents, agents don't need supervision. They need airlocks.
What ships with it: 9 files
18.2 KB alongside SKILL.md, 2 of them executable
demo/
- airlock-check.mjsruns2.7 KB
- fake-deploy.log276 B
- store-state.json134 B
examples/
- EXAMPLE.md1.1 KB
tests/
- airlock-check.test.mjsruns3.3 KB
- CHANGELOG.md691 B
- LICENSE6.9 KB
- package.json155 B
- README.md2.9 KB