[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C11DF4560QZ8FHTM38HPYN":3,"skill-same:01M7C11DF4560QZ8FHTM38HPYN":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":44},"01M7C11DF4560QZ8FHTM38HPYN","maintain-verification-skill",null,"Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for \u002Fmaintain-verification-skill or \"audit the verify skill\".","jlisam\u002Fpstack-copilot","jlisam","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1156793?v=4","01M7C10GBQZPWYDKZ8FBXAXXZ2","Javier Li Sam","01M7C10GCCMXMK85C3CJR8DA08",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjlisam\u002Fpstack-copilot\u002Fblob\u002Fmain\u002Fpstack\u002Fskills\u002Fmaintain-verification-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: maintain-verification-skill\ndescription: \"Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for \u002Fmaintain-verification-skill or \\\"audit the verify skill\\\".\"\ndisable-model-invocation: true\n---\n\n# Maintain a verification skill\n\nA feature map rots the moment the app changes. This skill is the upkeep loop for a skill generated by `\u002Fcreate-verification-skill` (or any project-local verification skill with a feature map). The unit of rigor is the feature, not every sentence: cover every feature file from source and exercise every feature live, without terminalising every bullet.\n\n## Outcomes\n\nPick one, and say which:\n\n- **clean** — every feature got source and live coverage; nothing worth shipping. No branch, no PR.\n- **changed** — one PR ships proven doc, harness, or map corrections.\n- **blocked** — coverage could not finish or a proven fix could not ship safely. Say exactly what blocked it.\n\n## Edit scope\n\nOnly edit the verification skill's own directory (its SKILL.md, features\u002F, and any harness scripts it owns). Never edit product code during a run: a behavior the map describes that the app no longer does is either doc drift (fix the map) or a product regression (report it, don't paper over it in docs).\n\n## Pass\n\n0. **Locate the target.** Find the verification skill to maintain: the project-local skill whose body has launch\u002Fdrive sections and a feature map, normally `.github\u002Fskills\u002Fverify-*\u002F`. For several candidates, follow [User decisions](..\u002Fpoteto-mode\u002Freferences\u002Ftask-contract.md#user-decisions). Use `ask_user` when available. Otherwise ask one concise plain-text question with the candidates as numbered choices and end the turn. For none, stop and point at `\u002Fcreate-verification-skill` instead of inventing a target.\n\n1. **Index hygiene.** Read the feature map README and glob its sibling files. Fix missing, extra, duplicate, or dead entries. Lightweight; no generated inventory.\n\n2. **Source wave.** Read [`..\u002Fpoteto-mode\u002Freferences\u002Ftask-contract.md`](..\u002Fpoteto-mode\u002Freferences\u002Ftask-contract.md). Issue one `explore` task per feature file together, using `how explorer`, default `grok-4.6@high`, split into task fields. Use the default `sync` mode. Each self-contained prompt names the repository, assigned feature file, source scope, no-writes boundary, and return shape: feature summary \u002F source entry points \u002F likely drift or none \u002F one live-verification recipe. Children never drive the app and never edit files.\n\n3. **Reconcile.** Every feature file has a returned summary. Merge overlapping recipes into as few app states as practical. Spot-check cited drift; don't re-prove clean claims. Sweep recent churn for user-facing surfaces missing from the map — require a concrete source path before calling one missing.\n\n4. **Live pass.** Required even when source looks clean. The coordinator owns all driving; follow the verification skill's own launch model — one long-lived instance driven serially for servers and UIs, or a fresh isolated session per drive for short-lived CLIs (the skill's Launch section decides, not this one). Exercise every feature at least once, and hold three invariants the whole pass, whatever the failure: (1) never drive an instance you haven't health-checked since it last did something surprising — doctor before first drive, doctor on each fresh session where sessions are the unit, doctor again after any failed drive, and where doctor can't see the failure (a wedged UI state on a healthy process), reset to a known state or relaunch rather than hoping; (2) evidence captured so far survives every cleanup, checked at its named location, not assumed; (3) nothing a drive started outlives that drive's usefulness — failed-iteration residue is cleaned whether the session is stuck, exited, or shared (for a shared instance, clean the residue, not the instance). A doctor failure caused by skill drift is drift: fix it under edit scope and retry once — restart whatever the fix invalidated, nothing more — before calling the pass `blocked`. A feature that can't be reached is `verified-unreachable` only with the concrete prerequisite (auth, entitlement, OS, external state) and the route attempted; if the map omits that prerequisite, that's drift. Any harness fix from triage gets re-driven live before it ships. Final teardown happens after the last drive of the run — including those re-proofs — so nothing outlives the run (evidence stays, per the skill).\n\n5. **Triage.** Wrong or missing user-POV description → doc drift, fix it. Working behavior the harness can't drive → harness gap, fix it; a harness fix follows the same helpers rule as generation (scripts executable, invocation documented in the skill body). App behavior that's actually broken → product gap; record it for the user, keep it out of this PR.\n\n6. **Ship or stop.** For changed: one PR of proven corrections, re-read every changed file first. For clean or blocked: no PR, report the outcome and the coverage honestly.\n\nKeep concise run notes (features covered, unreachable prerequisites, confirmed drift, outcome) in the active session workspace; don't commit them.\n","# Maintain a verification skill\n\nA feature map rots the moment the app changes. This skill is the upkeep loop for a skill generated by `\u002Fcreate-verification-skill` (or any project-local verification skill with a feature map). The unit of rigor is the feature, not every sentence: cover every feature file from source and exercise every feature live, without terminalising every bullet.\n\n## Outcomes\n\nPick one, and say which:\n\n- **clean** — every feature got source and live coverage; nothing worth shipping. No branch, no PR.\n- **changed** — one PR ships proven doc, harness, or map corrections.\n- **blocked** — coverage could not finish or a proven fix could not ship safely. Say exactly what blocked it.\n\n## Edit scope\n\nOnly edit the verification skill's own directory (its SKILL.md, features\u002F, and any harness scripts it owns). Never edit product code during a run: a behavior the map describes that the app no longer does is either doc drift (fix the map) or a product regression (report it, don't paper over it in docs).\n\n## Pass\n\n0. **Locate the target.** Find the verification skill to maintain: the project-local skill whose body has launch\u002Fdrive sections and a feature map, normally `.github\u002Fskills\u002Fverify-*\u002F`. For several candidates, follow [User decisions](..\u002Fpoteto-mode\u002Freferences\u002Ftask-contract.md#user-decisions). Use `ask_user` when available. Otherwise ask one concise plain-text question with the candidates as numbered choices and end the turn. For none, stop and point at `\u002Fcreate-verification-skill` instead of inventing a target.\n\n1. **Index hygiene.** Read the feature map README and glob its sibling files. Fix missing, extra, duplicate, or dead entries. Lightweight; no generated inventory.\n\n2. **Source wave.** Read [`..\u002Fpoteto-mode\u002Freferences\u002Ftask-contract.md`](..\u002Fpoteto-mode\u002Freferences\u002Ftask-contract.md). Issue one `explore` task per feature file together, using `how explorer`, default `grok-4.6@high`, split into task fields. Use the default `sync` mode. Each self-contained prompt names the repository, assigned feature file, source scope, no-writes boundary, and return shape: feature summary \u002F source entry points \u002F likely drift or none \u002F one live-verification recipe. Children never drive the app and never edit files.\n\n3. **Reconcile.** Every feature file has a returned summary. Merge overlapping recipes into as few app states as practical. Spot-check cited drift; don't re-prove clean claims. Sweep recent churn for user-facing surfaces missing from the map — require a concrete source path before calling one missing.\n\n4. **Live pass.** Required even when source looks clean. The coordinator owns all driving; follow the verification skill's own launch model — one long-lived instance driven serially for servers and UIs, or a fresh isolated session per drive for short-lived CLIs (the skill's Launch section decides, not this one). Exercise every feature at least once, and hold three invariants the whole pass, whatever the failure: (1) never drive an instance you haven't health-checked since it last did something surprising — doctor before first drive, doctor on each fresh session where sessions are the unit, doctor again after any failed drive, and where doctor can't see the failure (a wedged UI state on a healthy process), reset to a known state or relaunch rather than hoping; (2) evidence captured so far survives every cleanup, checked at its named location, not assumed; (3) nothing a drive started outlives that drive's usefulness — failed-iteration residue is cleaned whether the session is stuck, exited, or shared (for a shared instance, clean the residue, not the instance). A doctor failure caused by skill drift is drift: fix it under edit scope and retry once — restart whatever the fix invalidated, nothing more — before calling the pass `blocked`. A feature that can't be reached is `verified-unreachable` only with the concrete prerequisite (auth, entitlement, OS, external state) and the route attempted; if the map omits that prerequisite, that's drift. Any harness fix from triage gets re-driven live before it ships. Final teardown happens after the last drive of the run — including those re-proofs — so nothing outlives the run (evidence stays, per the skill).\n\n5. **Triage.** Wrong or missing user-POV description → doc drift, fix it. Working behavior the harness can't drive → harness gap, fix it; a harness fix follows the same helpers rule as generation (scripts executable, invocation documented in the skill body). App behavior that's actually broken → product gap; record it for the user, keep it out of this PR.\n\n6. **Ship or stop.** For changed: one PR of proven corrections, re-read every changed file first. For clean or blocked: no PR, report the outcome and the coverage honestly.\n\nKeep concise run notes (features covered, unreachable prerequisites, confirmed drift, outcome) in the active session workspace; don't commit them.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","1c6ba00d6128b78c78e6359a884b129590c4b45d","pstack\u002Fskills\u002Fmaintain-verification-skill","https:\u002F\u002Fgithub.com\u002Fjlisam\u002Fpstack-copilot","https:\u002F\u002Fgithub.com\u002Fjlisam","Internet Janitor","2026-11-04 02:18:46",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add jlisam\u002Fpstack-copilot --skill maintain-verification-skill",{"tool":38,"command":39},"bunx","bunx skills add jlisam\u002Fpstack-copilot --skill maintain-verification-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add jlisam\u002Fpstack-copilot --skill maintain-verification-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjlisam\u002Fpstack-copilot\u002Fblob\u002Fmain\u002Fpstack\u002Fskills\u002Fmaintain-verification-skill\u002FSKILL.md",[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7C14J4MH5CFMQMK25NMPKJ0","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fjlisam\u002Fpstack-copilot\u002Fblob\u002Fmain\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7C14GB154790GFM27QN3HDP","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Fjlisam\u002Fpstack-copilot\u002Fblob\u002Fmain\u002Fpstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7C14DCMHYPT2HB28JXPT02H","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fjlisam\u002Fpstack-copilot\u002Fblob\u002Fmain\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7C149PGJGZMMAN4F8S5Z2PM","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Fjlisam\u002Fpstack-copilot\u002Fblob\u002Fmain\u002Fpstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7C1472ZANW52KY30ZQC5P4B","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002Fjlisam\u002Fpstack-copilot\u002Fblob\u002Fmain\u002Fpstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7C144D3BXGPSBP5M6GRRJWY","tdd","Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.","https:\u002F\u002Fgithub.com\u002Fjlisam\u002Fpstack-copilot\u002Fblob\u002Fmain\u002Fpstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]