[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78D1WDZQMM780T4XYHDP62G":3,"skill-same:01M78D1WDZQMM780T4XYHDP62G":50},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M78D1WDZQMM780T4XYHDP62G","maintain-verification-skill",null,"Keep an installed OMP or Pi verification skill and feature map aligned with source and live behavior. Use for \u002Fmaintain-verification-skill or \"audit the verify skill\".","emo-eth\u002Fskills","emo-eth","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6371847?v=4","01M78CWE28WS3JH2WXYPRNC26K","James","01M78CWE2YS6Y5883W8J0D60XA",0,"MIT","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fmaintain-verification-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fmaintain-verification-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: maintain-verification-skill\ndescription: \"Keep an installed OMP or Pi verification skill and feature map aligned with source and live behavior. Use for \u002Fmaintain-verification-skill or \\\"audit the verify skill\\\".\"\ndisable-model-invocation: true\n---\n\n# Maintain a verification skill\n\nRead `pstack-runtime` before the first host-specific operation.\n\nA feature map rots when the app changes. This workflow maintains a `verify-*` skill whose source lives under `~\u002Fdev\u002Fskills\u002Fskills\u002F`. Cover every feature file from source and exercise every feature on its real user surface.\n\n## Outcomes\n\nPick one, and say which:\n\n- **clean**: every feature has source and live coverage; no source change.\n- **changed**: one committed and pushed skill update contains proven corrections.\n- **blocked**: coverage could not finish or a correction could not ship safely. Name the blocker.\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 `~\u002Fdev\u002Fskills\u002Fskills\u002Fverify-*\u002FSKILL.md` files with launch, drive, and feature-map sections. If several match the active project and the tools cannot determine which one owns it, use `ask`. If none match, route to `\u002Fcreate-verification-skill`.\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.** Launch one read-only `scout` per feature file in one OMP `task` batch. Each explains how the user-facing feature works from source, cites likely doc drift, and returns one concise live-verification recipe. Scouts never drive the app or 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 drives the real surface. Use OMP `browser` for web UI, the actual program in a PTY or managed process for CLI\u002FTUI, and the verification skill's launch contract for other surfaces. Exercise every mapped feature. Run doctor before the first drive, after a failed drive, and for every fresh short-lived session. Reset or relaunch any instance whose visible state is wedged even when its process is healthy. Preserve evidence after cleanup.\n\n5. **Triage.** Wrong user description is doc drift. An undrivable working feature is a harness gap. Fix only the verification skill. Broken product behavior is a product gap; report it without changing product code in this run.\n\n6. **Ship or stop.** For changed, follow `~\u002Fdev\u002Fskills\u002FAGENTS.md`: re-read changed files, commit, push `main`, and run `npx skills update`. For clean or blocked, make no commit and report 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\nRead `pstack-runtime` before the first host-specific operation.\n\nA feature map rots when the app changes. This workflow maintains a `verify-*` skill whose source lives under `~\u002Fdev\u002Fskills\u002Fskills\u002F`. Cover every feature file from source and exercise every feature on its real user surface.\n\n## Outcomes\n\nPick one, and say which:\n\n- **clean**: every feature has source and live coverage; no source change.\n- **changed**: one committed and pushed skill update contains proven corrections.\n- **blocked**: coverage could not finish or a correction could not ship safely. Name the blocker.\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 `~\u002Fdev\u002Fskills\u002Fskills\u002Fverify-*\u002FSKILL.md` files with launch, drive, and feature-map sections. If several match the active project and the tools cannot determine which one owns it, use `ask`. If none match, route to `\u002Fcreate-verification-skill`.\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.** Launch one read-only `scout` per feature file in one OMP `task` batch. Each explains how the user-facing feature works from source, cites likely doc drift, and returns one concise live-verification recipe. Scouts never drive the app or 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 drives the real surface. Use OMP `browser` for web UI, the actual program in a PTY or managed process for CLI\u002FTUI, and the verification skill's launch contract for other surfaces. Exercise every mapped feature. Run doctor before the first drive, after a failed drive, and for every fresh short-lived session. Reset or relaunch any instance whose visible state is wedged even when its process is healthy. Preserve evidence after cleanup.\n\n5. **Triage.** Wrong user description is doc drift. An undrivable working feature is a harness gap. Fix only the verification skill. Broken product behavior is a product gap; report it without changing product code in this run.\n\n6. **Ship or stop.** For changed, follow `~\u002Fdev\u002Fskills\u002FAGENTS.md`: re-read changed files, commit, push `main`, and run `npx skills update`. For clean or blocked, make no commit and report 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,"description":7,"disable-model-invocation":25},true,"main","556c6b2a01f1f75137a940333ffc8bd95cf0756e","skills\u002Fpstack\u002Fmaintain-verification-skill","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills","https:\u002F\u002Fgithub.com\u002Femo-eth","I make music and write code","2026-11-13 05:13:04",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add emo-eth\u002Fskills --skill maintain-verification-skill",{"tool":39,"command":40},"bunx","bunx skills add emo-eth\u002Fskills --skill maintain-verification-skill",{"tool":42,"command":43},"pnpm","pnpm dlx skills add emo-eth\u002Fskills --skill maintain-verification-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fmaintain-verification-skill\u002FSKILL.md",[46],{"path":47,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":16},"LICENSE","许可证",1067,[51,58,66,74,82,90],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":20},"01M78D75SMNM5JJXJGN9W6Z304","system-vibe","Personal operating-system contract for the home fleet, sync, SSH, skills, Herdr, and local inference. Use when diagnosing or changing machines, chezmoi, SSH, skill distribution, Windows sleep\u002Fwake, or the local model router. This is the qualitative list of what must stay true; agents invent enforcement from the clauses, not from tribal setup lore.","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsystem-vibe\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":62,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":20},"01M78D65Z8HK3VTSAWKC59TR94","rubber-stamp-travel-field-note","Use for rubber-stamp travel field-note photo posters.","CC-BY-4.0","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Frubber-stamp-travel-field-note\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":20},"01M78D5VXYSJZVTGETSYGZWQPQ","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\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fwhy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fwhy\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":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":20},"01M78D5SMN2NTGT19B2T5WY83T","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":20},"01M78D5PN73KA6B88JVHABNTKY","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftypescript-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M78D5JHTG4B6YPZ8TNN18Y6D","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\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FSKILL.md",[],[]]