[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DT6ABQ8TMVEFEFRQ7SP58V":3,"skill-same:01M6DT6ABQ8TMVEFEFRQ7SP58V":86},{"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":23,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":37,"commitSha":60,"skillDirectory":61,"forksCount":14,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":79},"01M6DT6ABQ8TMVEFEFRQ7SP58V","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\".","nicolasLuduena\u002Fskills","nicolasLuduena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47897388?v=4","01M6DT2J6QHQB14SH18EFBKT6D","Nicolás Ludueña","01M6DT2JBREQBVQYEQBR2AC31G",0,"MIT","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002Fmaintain-verification-skill\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"verification","maintain verification skill","maintain","use","normal","weekly","for","true","tree","as","feature","project","map","main","periodic","github","session","implementer","repo","parallel","loop","verify","audit","license","pr","2026-11-10 10:12:30",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\nmetadata:\n  fork:\n    source: https:\u002F\u002Fgithub.com\u002Fcursor\u002Fplugins\u002Ftree\u002Fmain\u002Fpstack (Lauren Tan, poteto; MIT, see ..\u002FLICENSE)\n    copied: cursor\u002Fplugins@9d76bca, 2026-10-11\n    change: \"Looks under .agents\u002Fskills\u002Fverify-*\u002F; the nico-agent loop runs it weekly per Repo as a gardening issue, so `changed` ships through the normal Implementer flow.\"\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 (usually `.agents\u002Fskills\u002Fverify-*\u002F`). Several candidates → ask which one; 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.** One read-only subagent per feature file, launched concurrently. Each explains \"how does this user-facing feature work?\" from source, flags likely doc drift with citations, and returns one concise live-verification recipe. Children never drive the app and never edit files. Return shape: feature summary \u002F source entry points \u002F likely drift or none \u002F one recipe.\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 a scratch location; 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 (usually `.agents\u002Fskills\u002Fverify-*\u002F`). Several candidates → ask which one; 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.** One read-only subagent per feature file, launched concurrently. Each explains \"how does this user-facing feature work?\" from source, flags likely doc drift with citations, and returns one concise live-verification recipe. Children never drive the app and never edit files. Return shape: feature summary \u002F source entry points \u002F likely drift or none \u002F one recipe.\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 a scratch location; don't commit them.\n",{"name":5,"metadata":54,"description":7,"disable-model-invocation":59},{"fork":55},{"change":56,"copied":57,"source":58},"Looks under .agents\u002Fskills\u002Fverify-*\u002F; the nico-agent loop runs it weekly per Repo as a gardening issue, so `changed` ships through the normal Implementer flow.","cursor\u002Fplugins@9d76bca, 2026-10-11","https:\u002F\u002Fgithub.com\u002Fcursor\u002Fplugins\u002Ftree\u002Fmain\u002Fpstack (Lauren Tan, poteto; MIT, see ..\u002FLICENSE)",true,"7ea7cd250b1d6a56795f2f23baf513a21420124b","skills\u002Fverify\u002Fmaintain-verification-skill","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills","https:\u002F\u002Fgithub.com\u002FnicolasLuduena","https:\u002F\u002Fnico-luduena.online","Senior full-stack engineer at @txpipe · Rust, TypeScript, blockchain infrastructure, developer tooling, and privacy-preserving applications.","2026-11-10 04:46:43",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":59},[69,72,75],{"tool":70,"command":71},"npx","npx skills add nicolasLuduena\u002Fskills --skill maintain-verification-skill",{"tool":73,"command":74},"bunx","bunx skills add nicolasLuduena\u002Fskills --skill maintain-verification-skill",{"tool":76,"command":77},"pnpm","pnpm dlx skills add nicolasLuduena\u002Fskills --skill maintain-verification-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002Fmaintain-verification-skill\u002FSKILL.md",[80],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"agents\u002Fopenai.yaml","REFERENCE","参考文档",183,"https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002Fmaintain-verification-skill\u002Fagents\u002Fopenai.yaml",[87,94,113,134,149,173],{"skillNo":88,"name":89,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":49},"01M717YJYMV0G9H52HJ9R259M2","improve","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhand\u002Fimprove\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhand\u002Fimprove\u002FSKILL.md",[],[89],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":101,"publishedAt":49},"01M6DT66VWY2M4VM3J7G2813T6","create-verification-skill","Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for \u002Fcreate-verification-skill, \"make a control skill for this repo\", or when a project has no scripted way to prove UI\u002FCLI\u002Fservice behavior.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002Fcreate-verification-skill\u002FSKILL.md",[100],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[102,103,24,42,104,105,106,35,107,37,108,27,109,45,47,110,111,48,39,112],"create verification skill","create","app","control","platform","local","evidence","generated","harness","generate","cli",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":49},"01M6DT604C3A5GRG03S2XM9QR4","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Ftdd\u002FSKILL.md",[],[115,120,121,122,123,124,125,27,126,127,128,129,130,131,132,133],"build","red","driven","tests","green","user","fix","first","refactor","integration","development","integration tests","test","red-green-refactor",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":49},"01M6DT64EQS172J3GFTSGW6MZR","verdict","The Reviewer's Verdict on a PR: re-run the repo's verification skill at the PR's head, hold the PR's Evidence against it, and record pass or fail with nico-agent.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Fverdict\u002FSKILL.md",[],[136,108,141,142,143,144,145,42,146,24,147,48,31,148],"re","record","head","it","with","reviewer","run","at",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":158,"publishedAt":49},"01M6DT5X7ZAHFMFDSMM1RA2500","research","Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Fresearch\u002FSKILL.md",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[151,42,159,160,161,162,163,164,165,166,167,168,169,170,171,33,172,27,125],"capture","markdown","investigate","api","file","docs","question","when","background","facts","high","reading","sources","trust",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":49},"01M6DT5STG12ET75KKQ4M1CN1Z","quality-scan","Audit a Repo with ponytail-audit and a deepening scan and file the top findings as issues, at most five open at once, without editing code.","https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Floop\u002Fquality-scan\u002FSKILL.md",[],[180,181,182,183,184,148,31,145,33,42,185,186,46,163,187,188,189],"quality","scan","quality scan","top","deepening","editing","open","issues","code","ponytail"]