[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C8V20APFB1JNZRWNMWPHKB":3,"skill-same:01M7C8V20APFB1JNZRWNMWPHKB":70},{"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":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M7C8V20APFB1JNZRWNMWPHKB","create-verification-skill",null,"Create and prove a project-local skill for driving real UI, CLI, or service behavior. Use when asked to create a verification skill or control workflow for a repository.","transitive-bullshit\u002Fskills","transitive-bullshit","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F552829?v=4","01M7C8KS4F4572TZFKR12N2A3W","Travis Fischer","01M7C8KS56YA2KDQHDNXEGS23P",4,"MIT","https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-verification-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-verification-skill\ndescription: \"Create and prove a project-local skill for driving real UI, CLI, or service behavior. Use when asked to create a verification skill or control workflow for a repository.\"\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 (`.agents\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 recipe supported by the current host: its available browser automation for web and Electron, ordinary processes for non-interactive CLIs, tmux\u002FPTY for interactive CLIs or TUIs, and HTTP for services. Do not assume Cursor tools, slash commands, or a specific browser API; preserve the host’s permission controls.\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 an in-scope setup issue or report the blocker 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\nCheck for an existing project verification skill before writing; preserve it or update the identified target rather than creating a duplicate. Write `.agents\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 prompt). Launch must reach a usable state from an empty data dir, including any migrations and seed data. Ready means usable, not just that a process answers. A database health check can pass while its init scripts are still running. 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 with isolated data, using a normal process for a non-interactive CLI or a PTY\u002Ftmux session when the interface requires a terminal.\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. Default the evidence directory outside every scratch or instance directory that cleanup removes; do not rely on an optional override or manual move to preserve it. 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 `.agents\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`. If the seed data lacks a precondition that a journey needs, the journey reports a failure and the reason goes in that feature's `Gotchas`. Never weaken the journey to make it pass. 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 using the documented defaults: 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. Correct the written instructions before rerunning; an undocumented override does not validate their defaults. 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. If you proved it in a stand-in for the real target (a container in place of a fresh VM, a local stack in place of a remote one), list every setup step the stand-in did that the target will not. Those steps stay unverified until a run on the real target covers them.\n\n## 5. Offer the maintenance loop\n\nPoint the user at `maintain-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 (`.agents\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 recipe supported by the current host: its available browser automation for web and Electron, ordinary processes for non-interactive CLIs, tmux\u002FPTY for interactive CLIs or TUIs, and HTTP for services. Do not assume Cursor tools, slash commands, or a specific browser API; preserve the host’s permission controls.\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 an in-scope setup issue or report the blocker 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\nCheck for an existing project verification skill before writing; preserve it or update the identified target rather than creating a duplicate. Write `.agents\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 prompt). Launch must reach a usable state from an empty data dir, including any migrations and seed data. Ready means usable, not just that a process answers. A database health check can pass while its init scripts are still running. 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 with isolated data, using a normal process for a non-interactive CLI or a PTY\u002Ftmux session when the interface requires a terminal.\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. Default the evidence directory outside every scratch or instance directory that cleanup removes; do not rely on an optional override or manual move to preserve it. 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 `.agents\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`. If the seed data lacks a precondition that a journey needs, the journey reports a failure and the reason goes in that feature's `Gotchas`. Never weaken the journey to make it pass. 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 using the documented defaults: 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. Correct the written instructions before rerunning; an undocumented override does not validate their defaults. 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. If you proved it in a stand-in for the real target (a container in place of a fresh VM, a local stack in place of a remote one), list every setup step the stand-in did that the target will not. Those steps stay unverified until a run on the real target covers them.\n\n## 5. Offer the maintenance loop\n\nPoint the user at `maintain-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":25},true,"main","fc9ff73613f4346442defd1318eae264af415d72","skills\u002Fcreate-verification-skill",1,"https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills","https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit","https:\u002F\u002Ftransitivebullsh.it","My heart is open source 💕 ","2026-10-24 01:38:48",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":25},[37,40,43],{"tool":38,"command":39},"npx","npx skills add transitive-bullshit\u002Fskills --skill create-verification-skill",{"tool":41,"command":42},"bunx","bunx skills add transitive-bullshit\u002Fskills --skill create-verification-skill",{"tool":44,"command":45},"pnpm","pnpm dlx skills add transitive-bullshit\u002Fskills --skill create-verification-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[48,54,58,62,66],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",177,"https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-verification-skill\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":16},"LICENSE","许可证",1067,{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Ffeature-map-example\u002Fcreate-note.md",2926,"https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-verification-skill\u002Freferences\u002Ffeature-map-example\u002Fcreate-note.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Ffeature-map-example\u002FREADME.md",2601,"https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-verification-skill\u002Freferences\u002Ffeature-map-example\u002FREADME.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Ffeature-map-example\u002Fsearch.md",3478,"https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-verification-skill\u002Freferences\u002Ffeature-map-example\u002Fsearch.md",[71,78,85,93,100,107],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":20},"01M7C8Z0JQ0VH6YYSJQGXJKVV4","xurl","Paid X API fallback through xurl after cheaper X reads fail, or for authorized account actions unsupported by bird.","https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":20},"01M7C8YY74K2MJYK311R1PG31A","x-data","Read or research X\u002FTwitter posts, URLs, profiles, threads, or the user's X history using the cheapest available source.","https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fx-data\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7C8YV6AAFSCTS39C2MBKTTV","write-skills","Create or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill, improving trigger descriptions, or deciding what belongs in a skill versus references, scripts, assets, or ordinary docs.","https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-skills\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-skills\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M7C8YQFGTFVQQJCH8SPFS3YQ","web-perf","Audit, diagnose, or optimize website loading and interaction performance, Core Web Vitals, and Lighthouse performance scores.","https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M7C8YJ6QFV6QFCJESHGZZ2B8","vercel-react-best-practices","Apply React and Next.js performance guidance. Use for performance work or a specific rendering, data-fetching, or bundle concern.","https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M7C8YBRVCMAZ99D1Y5QXHMG8","vercel-optimize","Audit deployed Vercel cost and performance using project metrics. Use for expensive or slow routes, usage analysis, and caching opportunities.","https:\u002F\u002Fgithub.com\u002Ftransitive-bullshit\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-optimize\u002FSKILL.md",[],[]]