verify
Skill351 starsChanged 4 months agoApache-2.0View on GitHub
Drive/evidence recipe for verifying wenlan changes at their real surfaces (daemon HTTP, CLI, MCP stdio). The handle file the built-in verify protocol expects; launch primitives live in the run-wenlan skill, deeper machinery (mutation audit, behavior trace, weekly sweep) in the prove skill.
189 other projects use a version of this.
Adopted by
Most recently taken up by
- Automattic/wp-calypsotheir own version, first seen Nov 16, 2026
- abe238/hotinaitheir own version, first seen Nov 16, 2026
- SmartStudio/baize-bottheir own version, first seen Nov 15, 2026
- YuBan834/vrma-labtheir own version, first seen Nov 15, 2026
- Ju571nK/lodelinetheir own version, first seen Nov 15, 2026
- ericbust/namedroptheir own version, first seen Nov 15, 2026
Used with
Projects with it also use instinct-export, instinct-import and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
TheKREATORSSkillinstinct-export
Export instincts from project/global scope to a file
Also in 3 projects that use this
TheKREATORSSkillinstinct-import
Import instincts from file or URL into project/global scope
Also in 3 projects that use this
AviadPSkillrisk-assess
Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).
Also in 3 projects that use this
diego-tobalinaSkillbuild-fix
Fix build and compilation errors systematically. Run when build fails.
Also in 6 projects that use this
AaravChadhaSkillsecure
Security review with a confidence gate - a finding exists only with a concrete exploit scenario and a high/medium/low confidence rating; everything else goes to a worth-hardening list, never inflated. Sweeps five surfaces: auth gates, secrets hygiene, injection and unsafe sinks, unsafe deserialization/crypto/transport, and LLM tool-use trust boundaries. Reports only, never fixes. Use when the user asks for a security review or to check vulnerabilities, secrets, or auth.
Also in 3 projects that use this
ArvorCoSkillspecify
Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.
Also in 10 projects that use this
- +1 more from TheKREATORS
Other versions189 projects use a version of this.
Word for word · 1
- 7xuanlu/wenlan★ 358100% same
Edited · 0
None found.
Wrote their own version · 188
- react/react★ 253ksame name
- facebook/react★ 253ksame name
- garrytan/gstack★ 142ksame name
- oven-sh/bun★ 97ksame name
- anthropics/financial-services-plugins★ 41ksame name
- anthropics/financial-services★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- anthropics/claude-quickstarts★ 19ksame name
- NVIDIA-NeMo/NeMo★ 19ksame name
178 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
- proveSkill
- run-wenlan-appSkill
- run-wenlanSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 166 edited versions we read keep these.
0
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 44
No
TMPDIR: Always give mktemp -d an explicit template.
“Common” is measured: kept by at least 6 in 10 of the 166 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
Verifying wenlan — drive the real surfaces
Launch: use the run-wenlan skill — build, isolated boot, stop, the port
allocation (manual instance :17878, smoke-cli.sh :17881, smoke-mcp.sh
:17882 — they are not interchangeable), and the daemon lifecycle checklist all
live there. Never verify against the shared prod daemon on :7878.
Drive by surface — these scripts ARE the drive recipes (read them for the flow, run them for a full round-trip):
- Daemon HTTP: curl the changed route on the isolated port; recipe in
.claude/skills/prove/references/daemon.md. - CLI:
bash scripts/smoke-cli.sh(capture → memories → search, black-box). - MCP:
bash scripts/smoke-mcp.sh(stdio JSON-RPC initialize → capture → recall).
Gotchas (drive-time):
- Ingest is async (batcher + embedding): poll search up to ~60s before calling a miss a failure.
- Record evidence: prefix any check with
bash scripts/attest.sh. It appends one JSON line to.claude/attest.jsonl— the ledger the weekly sweep audits — and passes the command's exit status through unchanged. If it cannot write the ledger it exits non-zero even when the command passed: an unrecorded run reads to the sweep as "the smoke never ran", so it must never be reported as a pass. (~/.claude/bin/attest.shis a personal macOS helper; it is optional, and it does not exist on Windows or in a fresh checkout. Use the repo script.) WENLAN_NO_AUTOSTART=1on every command that talks to a daemon. Without it a connect failure starts the user's registered background service, and the check then passes against the wrong instance.
Windows (Git Bash)
Both smokes run here as-is; the platform differences are handled inside them via
scripts/lib/host-process.sh. What changes for hand-driven checks:
- No
lsof. Port checks go throughnetstat -ano(seerun-wenlan). A probe that could not run is not a free port — treat a failed probe as fatal, never as "nothing is listening". - No
TMPDIR. Always givemktemp -dan explicit template. - MSYS paths are not daemon paths. Convert with
cygpath -mat the daemon boundary only, into a second variable; the shell keeps the MSYS spelling for its own cleanup. $!is not the OS pid, and killing by pid alone can kill a recycled pid's new owner. Resolve the WINPID and compare the image path before killing.python3may not exist —pythonis the usual spelling.scripts/smoke-mcp.shresolves it; do the same in ad-hoc checks rather than assuming.bash scripts/attest.shworks here, so Windows/verifysatisfies its own evidence contract..claude/skills/prove/SKILL.mdnames the same repo wrapper.
Deeper verification — mutation audit (suite), behavior trace (behaviors),
weekly verify-the-verifier (sweep): invoke the prove skill.
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.

