maintain-verification-skill

We split this skill into the rules it gives an agent

3 rules. 3 are common, 0 are distinctive, and 0 are very specific to this project.

• 3

  Common

  Most of the 58 edited versions we read keep these.

• 0

  Distinctive

  This author's own choices. Worth a look.

• 0

  Very specific

  Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 58 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.

• Other versions59 projects use a version of this.

  Word for word · 1

  1. Dimon94/skills★ 107100% same

  Edited · 52

  1. backnotprop/pstack★ 3.3k97% same
  2. openwong2kim/wmux★ 44058% same
  3. jtaroreh/agystack★ 12877% same
  4. uzairansaruzi/p3-stack★ 12691% same
  5. dsebban/skills★ 7192% same
  6. The-AIE/the-gibson★ 4397% same
  7. Scino/fstack★ 1887% same
  8. creedants/pstack-t3★ 1782% same
  9. kkgogogo17/pi-pstack★ 997% same
  10. mariusflorescu/pstack-t3★ 978% same

  42 more not listed

  Wrote their own version · 6

  1. paperclipai/paperclip★ 110ksame name
  2. TheOnlyFusionCube/potetos-for-everyone★ 18same name
  3. malinskibeniamin/skills★ 4same name
  4. matiopala/skills★ 2same name
  5. woodbeary/later-dog★ 2same name
  6. 3metaJun/mstack★ 0same name

  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.

• Used alongsideProjects with it also use principle-explain-the-number, poteto-help and 7 more.

  Other files people use alongside this one.

  How we pick theseFiles 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.

  • juancamiloqhzSkill

    principle-explain-the-number

    Apply 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 18 projects that use this

  • ianclearySkill

    poteto-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 9 projects that use this

  • jtarorehSkill

    poteto-mode

    poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

    Also in 5 projects that use this

  • bnemaSkill

    setup-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 23 projects that use this

  • Xia-AtaraxiaSkill

    make-bot-ui

    Builds a small web page whose buttons wake an agent over a webhook: a local server keeps the sender key server-side and POSTs JSON to a webhook-triggered routine, and the page is exposed on the existing Tailscale node. Use for \"make a bot UI\", \"a dashboard with buttons that trigger the agent\", \"wake the bot from a page\", handing a webhook sender key to the server without pasting it in chat, or putting that UI on the tailnet. Not for general frontend work - use principle-frontend; not for tailnet health or reachability - use tailscale.

    Also in 16 projects that use this

  • Xia-AtaraxiaSkill

    benchmark-checklist

    Vets performance measurements for the limiter, tuning, physical limits, errors, repeatability, relevance, and proof that timed work happened. It applies to 'check this benchmark', 'report this speedup', measured regressions, and choosing a library or configuration from numbers. It reports spread and gaps before drawing a conclusion. Not for general testing policy or choosing test oracles - use principle-testing.

    Also in 17 projects that use this

• In this repository40 other files it gives its agents.

  • AGENTS.mdAGENTS.md
  • skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
  • CLAUDE.mdCLAUDE.md
  • avoid-overengineeringSkill
  • best-practice-scoutSkill
  • better-accessibilitySkill
  • better-colorsSkill
  • better-interfaceSkill
  • better-layoutSkill
  • better-typographySkill
  • better-uiSkill
  • better-writingSkill
  • blast-radiusSkill
  • code-reviewSkill
  • create-formal-verification-skillSkill
  • create-verification-skillSkill
  • do-not-repeat-yourselfSkill
  • epic-plannerSkill
  • gh-merge-prSkill
  • git-commitSkill
  • git-push-prSkill
  • git-rebase-mainSkill
  • howSkill
  • investigateSkill
  • in-your-own-wordsSkill
  • maintain-formal-verification-skillSkill
  • no-commentsSkill
  • pi-loopSkill
  • postmortemSkill
  • productionize-app-with-servicesSkill
  • resolving-merge-conflictsSkill
  • show-meSkill
  • supabase-postgres-best-practicesSkill
  • sync-upstream-skillsSkill
  • test-disciplineSkill
  • test-reviewSkill
  • thermo-nuclear-code-quality-reviewSkill
  • vercel-react-best-practicesSkill
  • vertical-slicingSkill
  • whySkill