maintain-verification-skill
Skill2 starsChanged 29 days agoApache-2.0View on GitHub
Keep a repository's verification skill and feature map in step with the app: update them when the app changes or a recipe stops working, and re-prove what you touched.
81 other projects use a version of this.
Adopted by
Most recently taken up by
- TencentBlueKing/bk-litetheir own version, first seen Nov 16, 2026
- clnnn/playbooktheir own version, first seen Nov 16, 2026
- Schramm2/spyglasstheir own version, first seen Nov 16, 2026
- gfunc/skillstheir own version, first seen Nov 16, 2026
- magnusrodseth/dotfilestheir own version, first seen Nov 16, 2026
- shiwenbin1617/pstacktheir own version, first seen Nov 16, 2026
Used with
Projects with it also use setup-pstack, principle-explain-the-number and 9 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.
bnemaSkillsetup-pstack
Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.
Also in 30 projects that use this
shiwenbin1617Skillprinciple-explain-the-number
Apply before you measure, and before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.
Also in 33 projects that use this
shiwenbin1617Skillpoteto-help
Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
Also in 16 projects that use this
eryzerzSkillmake-bot-ui
Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.
Also in 21 projects that use this
drafaelSkillin-your-own-words
Restate the user's goals and the problem they are trying to solve to check understanding. Manual invocation only; use when the user explicitly invokes in-your-own-words or requests this understanding check. Do not solve the task or rewrite the assistant's last answer.
Also in 30 projects that use this
instructureSkillketchup
Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories
Also in 25 projects that use this
- +3 more from shiwenbin1617
Other versions81 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 81
- paperclipai/paperclip★ 114ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- backnotprop/pstack★ 4.2ksame name
- epam/ketcher★ 939same name
- deadlock-mod-manager/deadlock-mod-manager★ 617same name
- openwong2kim/wmux★ 455same name
- jtaroreh/agystack★ 128same name
- uzairansaruzi/p3-stack★ 126same name
- Dimon94/dverity★ 107same name
71 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 repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-laterdogSkill
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-appSkill
- verify-laterdogSkill
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-laterdogSkill
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-laterdogSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 81 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use when a change moves a route, command, screen, label or side effect that a verification skill describes, or when following one of its …
- Distinctive: line 13
Decide what is wrong: If a recipe fails because the product is broken, report the bug with its evidence.
“Common” is measured: kept by at least 6 in 10 of the 81 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
Maintain verification skill
Use when a change moves a route, command, screen, label or side effect that a verification skill describes, or when following one of its recipes fails.
Procedure
- Read what exists first: the verification skill and its feature map. For later.dog itself these are
docs/verification/README.mdand its feature pages,docs/laterdog/verification.md, and the canonicalskills/laterdog/verify-laterdog/(exported bypnpm laterdog:skills; never edit the exports). - Decide what is wrong. If a recipe fails because the product is broken, report the bug with its evidence. Do not rewrite the recipe until it passes.
- Match the change to the map. List the routes, commands, entry points and side effects the change touched, and find each one's entry. Add entries for new surfaces, including second ways in (a menu item, a shortcut, an MCP tool). Before deleting a stale entry, search for anything that links to it or runs it.
- Correct commands by running them against the real app in an isolated instance, not by reading the code alone.
- Re-prove the affected features in an isolated fixture. Keep the evidence where cleanup does not reach, and write down what the fixture cannot show.
- Keep claims in their lane. A fixture passing shows the implementation behaves. Fixture success does not qualify a live provider, a real account or production.
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.

