prove
Skill358 starsChanged 4 months agoApache-2.0View on GitHub
Per-surface verification loops for wenlan — daemon, cli, mcp, plugin, suite strength (mutation), behavior trace, weekly sweep. Routes to scripts; every check records evidence via attest. Deeper than the built-in verify skill — use prove for mutation audits, behavior tracing, and the weekly sweep; built-in /verify handles generic runtime observation.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- Belweave/hstacktheir own version, first seen Nov 8, 2026
- parcadei/Continuous-Claudetheir own version, first seen Oct 17, 2026
- sdvsignal/done-needs-prooftheir own version, first seen Oct 15, 2026
- pavelsimo/skillstheir own version, first seen Oct 13, 2026
- ilamanov/skillstheir own version, first seen Oct 13, 2026
- wenlan-app/wenlanword for word, first seen Oct 13, 2026
Other versions13 projects use a version of this.
Word for word · 1
- wenlan-app/wenlan★ 351100% same
Edited · 0
None found.
Wrote their own version · 12
- Z3Prover/z3★ 13ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- dtiger1889-ops/claude-harness-toolbox★ 33same name
- grove/promise-to-proof★ 4same name
- Belweave/hstack★ 1same name
- corygabrielsen/skills★ 1same name
- ilamanov/skills★ 1same name
- pavelsimo/skills★ 1same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- app/AGENTS.mdAGENTS.md
- e2e/AGENTS.mdAGENTS.md
- preview/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- src/AGENTS.mdAGENTS.md
- app/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- e2e/CLAUDE.mdCLAUDE.md
- preview/CLAUDE.mdCLAUDE.md
- scripts/CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- run-wenlan-appSkill
- run-wenlanSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Run every check through the evidence wrapper (records to .claude/attest.jsonl, which the weekly sweep audits): bash scripts/attest.sh …
- Distinctive: line 26
No argument → pick the surfaces the current diff touches (server/core → daemon.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/prove [surface] — wenlan verification loops
Run every check through the evidence wrapper (records to .claude/attest.jsonl,
which the weekly sweep audits): bash scripts/attest.sh <command>. That wrapper
ships in the repo and runs on macOS, Linux and Windows (Git Bash); the older
~/.claude/bin/attest.sh is a personal copy that does not exist on every
machine, and a missing wrapper means the run is unrecorded, which the sweep
reads as "the smoke never ran". Sandboxed local runs need TMPDIR=/tmp/claude
prefixed (macOS mktemp gotcha).
| Surface | Command | Proves |
daemon | read references/daemon.md | HTTP behavior on an isolated daemon |
cli | attest.sh bash scripts/smoke-cli.sh | shipped CLI black-box round-trip |
mcp | attest.sh bash scripts/smoke-mcp.sh | stdio JSON-RPC round-trip |
plugin | /wenlan setup verify path | plugin → MCP → daemon wiring |
suite | breadth: cargo mutants -f <file> (auto-generated mutants, lib-test oracle); depth: read references/mutprove.md | tests can actually go red (mutation audit) |
behaviors | attest.sh python3 scripts/check-behavior-trace.py <plan.md> <tests...> | tests trace to intent, both directions |
sweep | read references/sweep.md | weekly verify-the-verifier |
No argument → pick the surfaces the current diff touches (server/core → daemon;
cli crate → cli; mcp crate → mcp; new/changed tests → behaviors + suite).
App/UI surface (app/, src/, or anything rendered): rendered evidence
required — drive the running app and look at the screen; unit/build green is
not proof of visible correctness.
Live-smoke legs that need the real GPU model (L7) stay manual:
scripts/live-smoke-*.sh — run before merging features whose e2e stubs the LLM.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

