[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E5FVR97RWBMZSRHT37J2KA":3,"skill-same:01M7E5FVR97RWBMZSRHT37J2KA":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":43},"01M7E5FVR97RWBMZSRHT37J2KA","create-verification-skill",null,"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.","hasegama\u002Fpstack-claude","hasegama","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F40445443?v=4","01M7E58WENS57JDNDXCV1QVSP9","01M7E58WF9D5V2CNS2ZNF62AXD",0,"MIT","https:\u002F\u002Fgithub.com\u002Fhasegama\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack-claude\u002Fupstream\u002Fpstack\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-verification-skill\ndescription: \"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.\"\ndisable-model-invocation: true\n---\n\n# Create a verification skill\n\nEvery serious project needs a scripted way to drive the real app and prove behavior: launch it, exercise a feature the way a user would, and capture evidence. This skill generates that as a project-local skill (`.cursor\u002Fskills\u002Fverify-\u003Capp>\u002F`) tailored to the repo. You write the generator's output for the next agent, not for a human: it will be read cold, mid-task, by an agent that has never seen the app.\n\n## 1. Interview the repo, not the user\n\nAnswer these from the codebase and only ask the user what you cannot observe:\n\n- **Surface:** what does a user actually touch? A web UI, a CLI\u002FTUI, a desktop app, an API, a mobile app, a library? A repo can have several; pick the primary one and note the rest.\n- **Run:** how does the app start locally? Prefer the repo's own documented dev command (package scripts, Makefile, README quickstart). Note ports, env vars, seed data, auth.\n- **Drive:** how can an agent interact with it programmatically? Existing harnesses first — Playwright\u002FCypress specs, expect scripts, PTY helpers, curl-able endpoints, a debug port. Only then pick a generic recipe: browser\u002FCDP for web and Electron, a tmux\u002FPTY harness for CLI\u002FTUI, plain HTTP for services.\n- **Observe:** what evidence can be captured? Screenshots, terminal transcripts, response bodies, logs, exit codes, DB state.\n- **Isolate:** can two instances run side by side (ports, data dirs, profiles)? If not, say so in the generated skill: refusing to double-drive a shared instance beats corrupting the user's session.\n\nIf the checkout doesn't build or start as-is, fix that first (or report it precisely) before generating; a skill written against a broken base teaches wrong steps. When an irrelevant missing asset blocks startup (a static dir the API never serves, a sample config), the generated skill may create it, clearly marked as verification scaffolding, and remove it in cleanup.\n\n## 2. Generate the skill\n\nWrite `.cursor\u002Fskills\u002Fverify-\u003Capp>\u002FSKILL.md` with YAML frontmatter (`name: verify-\u003Capp>` and a `description` that names the app, the surface, and when to reach for it — without frontmatter the skill never registers) and these sections, each grounded in what the interview actually found (no placeholders left):\n\n- **Launch:** the exact command that starts the app for verification, and how to tell it's ready (a log line, a port answering, a prompt). Include teardown. For a short-lived CLI or TUI there is no server to keep alive: launch means build the binary (or install deps) once, then start each drive in its own isolated PTY or tmux session.\n- **Doctor:** one read-only check that answers \"is this instance worth driving?\" — process up, right version\u002Fbuild, port owned by us, auth valid. An agent runs this first whenever anything looks off.\n- **Drive:** the harness recipe with real selectors\u002Fcommands from this repo, not examples. Prefer stable handles (ARIA labels, data attributes, prompt strings, route paths) over coordinates and tab order.\n- **Evidence:** what to capture for a proof and where it goes. State the proof standards: exercise the real user path, not internal setters or test-only endpoints; capture the action and the resulting state, not just the final screen; verify side effects (files written, rows inserted, messages sent) alongside what's visible; mocks only where a production boundary already isolates the external system. When the safe path is a dry-run or test mode, verify what it actually skips by observing (files, network, git refs) rather than trusting its name: some dry-runs still touch the network or open a browser.\n- **Cleanup:** how to tear down instances the run created. Never kill by process name; kill what you started. Cleanup removes instances and scratch state, never the evidence: proof artifacts survive the teardown, in a location the skill names.\n- **Helpers:** any script the skill ships is executable and its invocation is shown in the skill body. A helper the reader has to reverse-engineer is not a helper.\n\n## 3. Seed the feature map\n\nCreate `.cursor\u002Fskills\u002Fverify-\u003Capp>\u002Ffeatures\u002FREADME.md` plus one file per user-facing feature you can identify (aim for the top 3-5 to start, from routes, commands, menus, or docs). Follow the shape in [`references\u002Ffeature-map-example\u002F`](references\u002Ffeature-map-example\u002F), with a README index and one file per feature. Each file answers, from the user's point of view: what the feature is, how to reach it, how to drive it with the harness, and what observable end state proves it works. The four H2s are `Sub-features`, `How to get to it (user POV)`, `Driving it with \u003Charness>`, and `Gotchas`. The map is the repo's maintained verification source; a proof that drives one convenient entry point is incomplete when the map lists others.\n\n## 4. Prove the generated skill before handing it over\n\nRun its own instructions end to end once: launch, doctor, drive ONE mapped feature (one is enough; the map exists so later runs can cover the rest), capture evidence, clean up. After cleanup, confirm the evidence still exists at the named location — a cleanup that eats the proof fails this step. Fix what fails, and run the generated cleanup after every failed iteration too, so broken attempts don't strand processes and ports. A generated skill that was never executed is a draft, not a deliverable.\n\n## 5. Offer the maintenance loop\n\nPoint the user at `\u002Fmaintain-verification-skill` for keeping the map honest as the app changes. Suggest a cadence only if they ask.\n","# Create a verification skill\n\nEvery serious project needs a scripted way to drive the real app and prove behavior: launch it, exercise a feature the way a user would, and capture evidence. This skill generates that as a project-local skill (`.cursor\u002Fskills\u002Fverify-\u003Capp>\u002F`) tailored to the repo. You write the generator's output for the next agent, not for a human: it will be read cold, mid-task, by an agent that has never seen the app.\n\n## 1. Interview the repo, not the user\n\nAnswer these from the codebase and only ask the user what you cannot observe:\n\n- **Surface:** what does a user actually touch? A web UI, a CLI\u002FTUI, a desktop app, an API, a mobile app, a library? A repo can have several; pick the primary one and note the rest.\n- **Run:** how does the app start locally? Prefer the repo's own documented dev command (package scripts, Makefile, README quickstart). Note ports, env vars, seed data, auth.\n- **Drive:** how can an agent interact with it programmatically? Existing harnesses first — Playwright\u002FCypress specs, expect scripts, PTY helpers, curl-able endpoints, a debug port. Only then pick a generic recipe: browser\u002FCDP for web and Electron, a tmux\u002FPTY harness for CLI\u002FTUI, plain HTTP for services.\n- **Observe:** what evidence can be captured? Screenshots, terminal transcripts, response bodies, logs, exit codes, DB state.\n- **Isolate:** can two instances run side by side (ports, data dirs, profiles)? If not, say so in the generated skill: refusing to double-drive a shared instance beats corrupting the user's session.\n\nIf the checkout doesn't build or start as-is, fix that first (or report it precisely) before generating; a skill written against a broken base teaches wrong steps. When an irrelevant missing asset blocks startup (a static dir the API never serves, a sample config), the generated skill may create it, clearly marked as verification scaffolding, and remove it in cleanup.\n\n## 2. Generate the skill\n\nWrite `.cursor\u002Fskills\u002Fverify-\u003Capp>\u002FSKILL.md` with YAML frontmatter (`name: verify-\u003Capp>` and a `description` that names the app, the surface, and when to reach for it — without frontmatter the skill never registers) and these sections, each grounded in what the interview actually found (no placeholders left):\n\n- **Launch:** the exact command that starts the app for verification, and how to tell it's ready (a log line, a port answering, a prompt). Include teardown. For a short-lived CLI or TUI there is no server to keep alive: launch means build the binary (or install deps) once, then start each drive in its own isolated PTY or tmux session.\n- **Doctor:** one read-only check that answers \"is this instance worth driving?\" — process up, right version\u002Fbuild, port owned by us, auth valid. An agent runs this first whenever anything looks off.\n- **Drive:** the harness recipe with real selectors\u002Fcommands from this repo, not examples. Prefer stable handles (ARIA labels, data attributes, prompt strings, route paths) over coordinates and tab order.\n- **Evidence:** what to capture for a proof and where it goes. State the proof standards: exercise the real user path, not internal setters or test-only endpoints; capture the action and the resulting state, not just the final screen; verify side effects (files written, rows inserted, messages sent) alongside what's visible; mocks only where a production boundary already isolates the external system. When the safe path is a dry-run or test mode, verify what it actually skips by observing (files, network, git refs) rather than trusting its name: some dry-runs still touch the network or open a browser.\n- **Cleanup:** how to tear down instances the run created. Never kill by process name; kill what you started. Cleanup removes instances and scratch state, never the evidence: proof artifacts survive the teardown, in a location the skill names.\n- **Helpers:** any script the skill ships is executable and its invocation is shown in the skill body. A helper the reader has to reverse-engineer is not a helper.\n\n## 3. Seed the feature map\n\nCreate `.cursor\u002Fskills\u002Fverify-\u003Capp>\u002Ffeatures\u002FREADME.md` plus one file per user-facing feature you can identify (aim for the top 3-5 to start, from routes, commands, menus, or docs). Follow the shape in [`references\u002Ffeature-map-example\u002F`](references\u002Ffeature-map-example\u002F), with a README index and one file per feature. Each file answers, from the user's point of view: what the feature is, how to reach it, how to drive it with the harness, and what observable end state proves it works. The four H2s are `Sub-features`, `How to get to it (user POV)`, `Driving it with \u003Charness>`, and `Gotchas`. The map is the repo's maintained verification source; a proof that drives one convenient entry point is incomplete when the map lists others.\n\n## 4. Prove the generated skill before handing it over\n\nRun its own instructions end to end once: launch, doctor, drive ONE mapped feature (one is enough; the map exists so later runs can cover the rest), capture evidence, clean up. After cleanup, confirm the evidence still exists at the named location — a cleanup that eats the proof fails this step. Fix what fails, and run the generated cleanup after every failed iteration too, so broken attempts don't strand processes and ports. A generated skill that was never executed is a draft, not a deliverable.\n\n## 5. Offer the maintenance loop\n\nPoint the user at `\u002Fmaintain-verification-skill` for keeping the map honest as the app changes. Suggest a cadence only if they ask.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","36262efad28c7be938a3b1bca81646ed163ae64f","plugins\u002Fpstack-claude\u002Fupstream\u002Fpstack\u002Fskills\u002Fcreate-verification-skill","https:\u002F\u002Fgithub.com\u002Fhasegama\u002Fpstack-claude","https:\u002F\u002Fgithub.com\u002Fhasegama","Computer Vision","2026-10-16 17:52:03",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":23},[33,36,39],{"tool":34,"command":35},"npx","npx skills add hasegama\u002Fpstack-claude --skill create-verification-skill",{"tool":37,"command":38},"bunx","bunx skills add hasegama\u002Fpstack-claude --skill create-verification-skill",{"tool":40,"command":41},"pnpm","pnpm dlx skills add hasegama\u002Fpstack-claude --skill create-verification-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhasegama\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack-claude\u002Fupstream\u002Fpstack\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[44,50,54],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Ffeature-map-example\u002Fcreate-note.md","REFERENCE","参考文档",2926,"https:\u002F\u002Fgithub.com\u002Fhasegama\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack-claude\u002Fupstream\u002Fpstack\u002Fskills\u002Fcreate-verification-skill\u002Freferences\u002Ffeature-map-example\u002Fcreate-note.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Ffeature-map-example\u002FREADME.md",2601,"https:\u002F\u002Fgithub.com\u002Fhasegama\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack-claude\u002Fupstream\u002Fpstack\u002Fskills\u002Fcreate-verification-skill\u002Freferences\u002Ffeature-map-example\u002FREADME.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Ffeature-map-example\u002Fsearch.md",3478,"https:\u002F\u002Fgithub.com\u002Fhasegama\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack-claude\u002Fupstream\u002Fpstack\u002Fskills\u002Fcreate-verification-skill\u002Freferences\u002Ffeature-map-example\u002Fsearch.md",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7E5KFP59WKAWKDNA3ST1VH1","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\u002Fhasegama\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack-claude\u002Fupstream\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7E5KE3VW28EDY5ZXRWEPMDG","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Fhasegama\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack-claude\u002Fupstream\u002Fpstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7E5KCCQZQMYFY07AB8C8484","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fhasegama\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack-claude\u002Fupstream\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7E5K947AWBZ57BGK8GSTS88","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\u002Fhasegama\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack-claude\u002Fupstream\u002Fpstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M7E5K4TQHAWA192CKQAW17JG","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\u002Fhasegama\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack-claude\u002Fupstream\u002Fpstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M7E5K1AYSFJG3G729YMPFH8P","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\u002Fhasegama\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack-claude\u002Fupstream\u002Fpstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]