[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JEE4H8G6DAQDVY4K36WJX":3,"skill-same:01M71JEE4H8G6DAQDVY4K36WJX":91},{"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":24,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":5,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M71JEE4H8G6DAQDVY4K36WJX","create-verification-skill",null,"Create a project-local skill that launches and drives the real app like a user, captures durable proof, and cleans up safely. Use whenever a repo lacks a scripted way to verify UI, CLI, desktop, mobile, API, or service behavior end to end.","caezium\u002Fskills","caezium","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113233555?v=4","01M71JB77ZPBAWEK009Y2W8BP7","Henry Zhang","01M71JB792NVXCWSYD27HQ0964",3,"MIT","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fcreate-verification-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fcreate-verification-skill\u002FSKILL.md",[19],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"create","verification","create verification skill","ui","service","proof","mobile","behavior","desktop","verify","cli","api","verify ui","use","local","up","end","repo","project","app","2026-11-10 10:12:30",false,"---\nname: create-verification-skill\ndescription: Create a project-local skill that launches and drives the real app like a user, captures durable proof, and cleans up safely. Use whenever a repo lacks a scripted way to verify UI, CLI, desktop, mobile, API, or service behavior end to end.\n---\n\n# Create a verification skill\n\nGenerate a cold-startable project skill that another agent can use to launch the real product, exercise a user path, and retain proof. A generated skill that has not run successfully is a draft.\n\n## Choose one canonical location\n\nRespect the repository's established convention. If none exists, use this table and keep one source of truth—never duplicate editable copies.\n\n| Repository target | Canonical root | Compatibility action |\n|---|---|---|\n| Multi-harness or Codex\u002FT3-first | `.agents\u002Fskills\u002Fverify-\u003Capp>\u002F` | Add relative links under `.claude\u002Fskills\u002F` or `.cursor\u002Fskills\u002F` only if that harness does not discover `.agents\u002Fskills\u002F` and the repo accepts symlinks |\n| Claude Code-only | `.claude\u002Fskills\u002Fverify-\u003Capp>\u002F` | No duplicate |\n| Cursor-only | `.cursor\u002Fskills\u002Fverify-\u003Capp>\u002F` | No duplicate |\n\nRecord the chosen root in the generated skill so its maintenance pass can find it.\n\n## 1. Interview the repository\n\nAnswer from code and docs before asking the user:\n\n- **Surface:** what users touch—web UI, CLI\u002FTUI, desktop\u002Fmobile app, API, service, or library.\n- **Run:** the repository's real local start\u002Fbuild command, readiness signal, ports, environment, fixtures, and auth.\n- **Drive:** existing harnesses first: browser tests, app automation, PTY helpers, CLI scripts, or HTTP clients.\n- **Observe:** screenshots, accessibility snapshots, terminal transcripts, response bodies, exit codes, logs, and persisted side effects.\n- **Isolate:** ports, profiles, and data directories that permit concurrent runs. If isolation is impossible, require exclusive ownership and refuse to drive a user's live instance.\n\n| Surface | Preferred driver | Fallback |\n|---|---|---|\n| Web \u002F Electron | Attached collaborative browser or existing Playwright\u002FCypress harness | Repository-approved browser automation; avoid coordinates when stable roles\u002Fselectors exist |\n| CLI \u002F TUI | Existing expect, PTY, or tmux harness | Isolated shell session with captured stdout, stderr, and exit code |\n| API \u002F service | Existing integration client or tests | Literal HTTP requests against an isolated local instance |\n| Desktop \u002F mobile | Existing platform UI harness | Platform-native automation available in the current harness; otherwise report the missing capability |\n\nIf the checkout cannot start as documented, fix or precisely report the base problem before generating instructions against it.\n\n## 2. Generate the skill\n\nCreate `SKILL.md` at the selected root with `name: verify-\u003Capp>` and a description naming the app, surface, and trigger. Ground every section in this repository; leave no placeholders.\n\n- **Launch:** exact start command, readiness predicate, ownership marker, and teardown. Short-lived CLIs start in a fresh isolated session per drive.\n- **Doctor:** one read-only check for process\u002Fbuild identity, endpoint, profile\u002Fdata directory, and auth as relevant.\n- **Drive:** exact commands and stable handles from this repo. Prefer accessible names, prompt strings, route paths, and documented flags over coordinates or tab order.\n- **Evidence:** prove the real user path and resulting state. Capture the action and outcome, then verify side effects from a second read-only view. Use mocks only at an existing production boundary.\n- **Cleanup:** stop only processes the run started and remove only its scratch state. Preserve evidence.\n- **Helpers:** make scripts executable and document literal invocations.\n\n## 3. Seed the feature map\n\nCreate `features\u002FREADME.md` plus files for the top three to five user-facing features discovered from routes, commands, menus, or docs. Read [`references\u002Ffeature-map-example\u002F`](references\u002Ffeature-map-example\u002F) for the exact shape. Each feature file uses these four H2 headings:\n\n1. `Sub-features`\n2. `How to get to it (user POV)`\n3. `Driving it with \u003Charness>`\n4. `Gotchas`\n\nMap every user entry point separately; proving one convenient path does not prove its siblings.\n\n## 4. Prove the generated skill\n\nRun launch, doctor, one mapped feature, evidence capture, and cleanup end to end. Confirm the evidence still exists after cleanup. Clean failed attempts too, then fix the instructions and rerun until green.\n\nPoint future maintainers to `maintain-verification-skill` and report the canonical location, tested feature, proof paths, and any unsupported surface.\n\n\u003C!-- Adapted from poteto\u002Fpstack create-verification-skill, MIT License, Lauren Tan, cursor\u002Fplugins@51a96e0. -->\n","# Create a verification skill\n\nGenerate a cold-startable project skill that another agent can use to launch the real product, exercise a user path, and retain proof. A generated skill that has not run successfully is a draft.\n\n## Choose one canonical location\n\nRespect the repository's established convention. If none exists, use this table and keep one source of truth—never duplicate editable copies.\n\n| Repository target | Canonical root | Compatibility action |\n|---|---|---|\n| Multi-harness or Codex\u002FT3-first | `.agents\u002Fskills\u002Fverify-\u003Capp>\u002F` | Add relative links under `.claude\u002Fskills\u002F` or `.cursor\u002Fskills\u002F` only if that harness does not discover `.agents\u002Fskills\u002F` and the repo accepts symlinks |\n| Claude Code-only | `.claude\u002Fskills\u002Fverify-\u003Capp>\u002F` | No duplicate |\n| Cursor-only | `.cursor\u002Fskills\u002Fverify-\u003Capp>\u002F` | No duplicate |\n\nRecord the chosen root in the generated skill so its maintenance pass can find it.\n\n## 1. Interview the repository\n\nAnswer from code and docs before asking the user:\n\n- **Surface:** what users touch—web UI, CLI\u002FTUI, desktop\u002Fmobile app, API, service, or library.\n- **Run:** the repository's real local start\u002Fbuild command, readiness signal, ports, environment, fixtures, and auth.\n- **Drive:** existing harnesses first: browser tests, app automation, PTY helpers, CLI scripts, or HTTP clients.\n- **Observe:** screenshots, accessibility snapshots, terminal transcripts, response bodies, exit codes, logs, and persisted side effects.\n- **Isolate:** ports, profiles, and data directories that permit concurrent runs. If isolation is impossible, require exclusive ownership and refuse to drive a user's live instance.\n\n| Surface | Preferred driver | Fallback |\n|---|---|---|\n| Web \u002F Electron | Attached collaborative browser or existing Playwright\u002FCypress harness | Repository-approved browser automation; avoid coordinates when stable roles\u002Fselectors exist |\n| CLI \u002F TUI | Existing expect, PTY, or tmux harness | Isolated shell session with captured stdout, stderr, and exit code |\n| API \u002F service | Existing integration client or tests | Literal HTTP requests against an isolated local instance |\n| Desktop \u002F mobile | Existing platform UI harness | Platform-native automation available in the current harness; otherwise report the missing capability |\n\nIf the checkout cannot start as documented, fix or precisely report the base problem before generating instructions against it.\n\n## 2. Generate the skill\n\nCreate `SKILL.md` at the selected root with `name: verify-\u003Capp>` and a description naming the app, surface, and trigger. Ground every section in this repository; leave no placeholders.\n\n- **Launch:** exact start command, readiness predicate, ownership marker, and teardown. Short-lived CLIs start in a fresh isolated session per drive.\n- **Doctor:** one read-only check for process\u002Fbuild identity, endpoint, profile\u002Fdata directory, and auth as relevant.\n- **Drive:** exact commands and stable handles from this repo. Prefer accessible names, prompt strings, route paths, and documented flags over coordinates or tab order.\n- **Evidence:** prove the real user path and resulting state. Capture the action and outcome, then verify side effects from a second read-only view. Use mocks only at an existing production boundary.\n- **Cleanup:** stop only processes the run started and remove only its scratch state. Preserve evidence.\n- **Helpers:** make scripts executable and document literal invocations.\n\n## 3. Seed the feature map\n\nCreate `features\u002FREADME.md` plus files for the top three to five user-facing features discovered from routes, commands, menus, or docs. Read [`references\u002Ffeature-map-example\u002F`](references\u002Ffeature-map-example\u002F) for the exact shape. Each feature file uses these four H2 headings:\n\n1. `Sub-features`\n2. `How to get to it (user POV)`\n3. `Driving it with \u003Charness>`\n4. `Gotchas`\n\nMap every user entry point separately; proving one convenient path does not prove its siblings.\n\n## 4. Prove the generated skill\n\nRun launch, doctor, one mapped feature, evidence capture, and cleanup end to end. Confirm the evidence still exists after cleanup. Clean failed attempts too, then fix the instructions and rerun until green.\n\nPoint future maintainers to `maintain-verification-skill` and report the canonical location, tested feature, proof paths, and any unsupported surface.\n\n\u003C!-- Adapted from poteto\u002Fpstack create-verification-skill, MIT License, Lauren Tan, cursor\u002Fplugins@51a96e0. -->\n",{"name":5,"description":7},"main","6ef866230c1ba3459fd08fc65141dfd37fffd41a",0,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills","https:\u002F\u002Fskills.henryzh.dev","https:\u002F\u002Fgithub.com\u002Fcaezium","henryzh.dev","quant, data science, full-stack, robotics.\r\nbuilding cool stuff","2026-08-24 19:21:44",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add caezium\u002Fskills --skill create-verification-skill",{"tool":65,"command":66},"bunx","bunx skills add caezium\u002Fskills --skill create-verification-skill",{"tool":68,"command":69},"pnpm","pnpm dlx skills add caezium\u002Fskills --skill create-verification-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fcreate-verification-skill\u002FSKILL.md",true,[73,77,83,87],{"path":74,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":16},"LICENSE","许可证",1067,{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Ffeature-map-example\u002Fcreate-note.md","REFERENCE","参考文档",2926,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fcreate-verification-skill\u002Freferences\u002Ffeature-map-example\u002Fcreate-note.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Ffeature-map-example\u002FREADME.md",2601,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fcreate-verification-skill\u002Freferences\u002Ffeature-map-example\u002FREADME.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Ffeature-map-example\u002Fsearch.md",3478,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fcreate-verification-skill\u002Freferences\u002Ffeature-map-example\u002Fsearch.md",[92,113,140,158,178,199],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":106,"publishedAt":45},"01M71JT4RYCAS18RF6003YYR1D","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FSKILL.md",[98,101],{"categoryNo":99,"categoryName":100,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[107,108,109,110,38,111,112],"writing for agents","for","writing","editing","documents","when",{"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":122,"publishedAt":45},"01M71JT0GES4AZ5ADH8EADNN1Z","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwrangler\u002FSKILL.md",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000010","后端与接口",[115,123,124,125,126,35,127,128,129,130,131,132,133,108,134,135,136,137,138,139],"cloudflare","d1","knowledge","workflows","secrets","commands","syntax","cloudflare workers","r2","queues","running","containers","correct","load","workers","best practices","store",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":45},"01M71JSWX4R203M32K9A18AAW8","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fworkers-best-practices\u002FSKILL.md",[],[147,137,138,148,149,150,108,123,151,125,152,115,109,136,112,153,154,155,156,157],"workers best practices","observability","reviews","promises","worker","new","code","common","streaming","state","anti-patterns",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":45},"01M71JST6P88MXGT2MWDTPJGEG","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwizard\u002FSKILL.md",[],[160,133,165,108,40,166,167,168,38,169,112,170,171,172,173,174,175,176,177,127],"setting","ci","provisioning infrastructure","only","invoke","Bash","one","interactive","can","credentials","dashboard","generate","human",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":182,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":45},"01M71JSQ95S7BQ61DAPN95X2W4","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available evidence sources, searches each relevant category, and returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwhy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwhy\u002FSKILL.md",[],[180,186,187,188,189,108,190,191,38,192,193,194,32,195,196,197,198],"sources","thresholds","evidence","relevant","runtime","design","decisions","work","how","read","data","rationale","returns",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":45},"01M71JSMHFVSH8HK8GXN6YAX6J","week-prep","Generate a briefing with calendar, tasks, and attention flags. Use for \"week prep\", \"briefing\", or \"what's on this week\".","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fweek-prep\u002FSKILL.md",[205],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},[207,208,209,210,211,108,212,213,214,215,38,170,216,217,218,176,219,195,220,221],"week prep","prep","deep","attention","get","search","messages","briefing","MCP","tasks","with","slack","calendar","flags","grep"]