[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SYJTF6HTDRZX9KSDMXPBG":3,"skill-same:01M71SYJTF6HTDRZX9KSDMXPBG":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":72},"01M71SYJTF6HTDRZX9KSDMXPBG","find-skills",null,"Use when the user asks about finding, discovering, or installing agent skills from the public ecosystem, or asks how to do something that might exist as an installable skill. For raiding a specific repo's patterns into clauDNA, use \u002Fclaudna:heist.","Claudfather\u002FclauDNA","Claudfather","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281278891?v=4","01M71SX82K0TBGQ394AB2G1T5Z","01M71SX83CE1S8YC06K9P3P962",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Ffind-skills\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"find","find skills","node","about","how","cli","to do","when","use","package","skills cli","npx","how to","true","repo","for","runner","ecosystem","do","as","2026-11-10 13:02:02",false,"---\nname: find-skills\nuser-invocable: true\ndescription: \"Use when the user asks about finding, discovering, or installing agent skills from the public ecosystem, or asks how to do something that might exist as an installable skill. For raiding a specific repo's patterns into clauDNA, use \u002Fclaudna:heist.\"\nrequires:\n  - cli: npx\n    reason: \"Node package runner for skills CLI\"\n---\n\n# Find Skills\n\n> **Codex:** Read `..\u002F_shared\u002Fcodex-tools.md` before following this skill. Apply its tool, root and dispatch mappings throughout.\n\nThis skill helps you discover and install skills from the open agent skills ecosystem.\n\n## When to Use This Skill\n\nUse this skill when the user:\n\n- Asks \"how do I do X\" where X might be a common task with an existing skill\n- Says \"find a skill for X\" or \"is there a skill for X\"\n- Asks \"can you do X\" where X is a specialized capability\n- Expresses interest in extending agent capabilities\n- Wants to search for tools, templates, or workflows\n- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)\n\n## What is the Skills CLI?\n\nThe Skills CLI (`npx skills@1.7.0`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.\n\n**Key commands:**\n\n- `npx skills@1.7.0 find [query]` - Search for skills interactively or by keyword\n- `npx skills@1.7.0 add \u003Cpackage>` - Install a skill from GitHub or other sources\n- `npx skills@1.7.0 check` - Check for skill updates\n- `npx skills@1.7.0 update` - Update all installed skills (refreshes EVERY installed skill to its repository head; review what changed, and prefer updating a named skill to a reviewed commit over a blanket refresh)\n\n**Browse skills at:** https:\u002F\u002Fskills.sh\u002F\n\n## How to Help Users Find Skills\n\n### Step 1: Understand What They Need\n\nWhen a user asks for help with something, identify:\n\n1. The domain (e.g., React, testing, design, deployment)\n2. The specific task (e.g., writing tests, creating animations, reviewing PRs)\n3. Whether this is a common enough task that a skill likely exists\n\n### Step 2: Search for Skills\n\nRun the find command with a relevant query:\n\n```bash\nnpx skills@1.7.0 find [query]\n```\n\nFor example:\n\n- User asks \"how do I make my React app faster?\" → `npx skills@1.7.0 find react performance`\n- User asks \"can you help me with PR reviews?\" → `npx skills@1.7.0 find pr review`\n- User asks \"I need to create a changelog\" → `npx skills@1.7.0 find changelog`\n\nThe command will return results like:\n\n```\nInstall with npx skills@1.7.0 add \u003Cowner\u002Frepo@skill>\n\nvercel-labs\u002Fagent-skills@vercel-react-best-practices\n└ https:\u002F\u002Fskills.sh\u002Fvercel-labs\u002Fagent-skills\u002Fvercel-react-best-practices\n```\n\n### Step 3: Present Options to the User\n\nWhen you find relevant skills, present them to the user with:\n\n1. The skill name and what it does\n2. The install command they can run\n3. A link to learn more at skills.sh\n\nExample response:\n\n```\nI found a skill that might help! The \"vercel-react-best-practices\" skill provides\nReact and Next.js performance optimization guidelines from Vercel Engineering.\n\nTo install it:\nnpx skills@1.7.0 add vercel-labs\u002Fagent-skills@vercel-react-best-practices\n\nLearn more: https:\u002F\u002Fskills.sh\u002Fvercel-labs\u002Fagent-skills\u002Fvercel-react-best-practices\n```\n\n### Step 4: Offer to Install\n\nBefore installing, **show the user the skill's contents** — fetch and display its `SKILL.md` (and any hook or script it ships) so an install is an informed choice, not a blind fetch. Then:\n\n```bash\nnpx skills@1.7.0 add \u003Cowner\u002Frepo@skill>\n```\n\n- **Keep the confirmation prompt** — do not pass `-y`. The prompt is the user's last look before third-party content lands.\n- **Default to project scope** — omit `-g`. Install globally (`-g`, user-level, every project) only when the user explicitly asks for that reach.\n- **Pin to a reviewed commit, not the moving head** — a bare `owner\u002Frepo@skill` takes the repository head at fetch time; where the tool supports a ref, name the commit the user reviewed (see the tool's ref syntax), so a later push to that repo cannot change what is installed.\n\n## Common Skill Categories\n\nWhen searching, consider these common categories:\n\n| Category        | Example Queries                          |\n| --------------- | ---------------------------------------- |\n| Web Development | react, nextjs, typescript, css, tailwind |\n| Testing         | testing, jest, playwright, e2e           |\n| DevOps          | deploy, docker, kubernetes, ci-cd        |\n| Documentation   | docs, readme, changelog, api-docs        |\n| Code Quality    | review, lint, refactor, best-practices   |\n| Design          | ui, ux, design-system, accessibility     |\n| Productivity    | workflow, automation, git                |\n\n## Tips for Effective Searches\n\n1. **Use specific keywords**: \"react testing\" is better than just \"testing\"\n2. **Try alternative terms**: If \"deploy\" doesn't work, try \"deployment\" or \"ci-cd\"\n3. **Check popular sources**: Many skills come from `vercel-labs\u002Fagent-skills` or `ComposioHQ\u002Fawesome-claude-skills`\n\n## When No Skills Are Found\n\nIf no relevant skills exist:\n\n1. Acknowledge that no existing skill was found\n2. Offer to help with the task directly using your general capabilities\n3. If the workflow recurs, first consider extending an existing clauDNA skill, lens or mode. For a pack contribution, use a clauDNA source checkout and the [contribution workflow](https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002FCONTRIBUTING.md) and [authoring guide](https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fdocumentation\u002Fguides\u002FSKILL_AUTHORING_GUIDE.md). The source-only `skill-scaffold` requires that checkout context and is excluded from the installed Codex catalog.\n\nExample:\n\n```\nI searched for skills related to \"xyz\" but didn't find any matches.\nI can still help you with this task directly.\n\nIf this becomes a repeatable clauDNA workflow, we can extend an existing skill\nor propose an addition through clauDNA's source-checkout contribution workflow.\n```\n","# Find Skills\n\n> **Codex:** Read `..\u002F_shared\u002Fcodex-tools.md` before following this skill. Apply its tool, root and dispatch mappings throughout.\n\nThis skill helps you discover and install skills from the open agent skills ecosystem.\n\n## When to Use This Skill\n\nUse this skill when the user:\n\n- Asks \"how do I do X\" where X might be a common task with an existing skill\n- Says \"find a skill for X\" or \"is there a skill for X\"\n- Asks \"can you do X\" where X is a specialized capability\n- Expresses interest in extending agent capabilities\n- Wants to search for tools, templates, or workflows\n- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)\n\n## What is the Skills CLI?\n\nThe Skills CLI (`npx skills@1.7.0`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.\n\n**Key commands:**\n\n- `npx skills@1.7.0 find [query]` - Search for skills interactively or by keyword\n- `npx skills@1.7.0 add \u003Cpackage>` - Install a skill from GitHub or other sources\n- `npx skills@1.7.0 check` - Check for skill updates\n- `npx skills@1.7.0 update` - Update all installed skills (refreshes EVERY installed skill to its repository head; review what changed, and prefer updating a named skill to a reviewed commit over a blanket refresh)\n\n**Browse skills at:** https:\u002F\u002Fskills.sh\u002F\n\n## How to Help Users Find Skills\n\n### Step 1: Understand What They Need\n\nWhen a user asks for help with something, identify:\n\n1. The domain (e.g., React, testing, design, deployment)\n2. The specific task (e.g., writing tests, creating animations, reviewing PRs)\n3. Whether this is a common enough task that a skill likely exists\n\n### Step 2: Search for Skills\n\nRun the find command with a relevant query:\n\n```bash\nnpx skills@1.7.0 find [query]\n```\n\nFor example:\n\n- User asks \"how do I make my React app faster?\" → `npx skills@1.7.0 find react performance`\n- User asks \"can you help me with PR reviews?\" → `npx skills@1.7.0 find pr review`\n- User asks \"I need to create a changelog\" → `npx skills@1.7.0 find changelog`\n\nThe command will return results like:\n\n```\nInstall with npx skills@1.7.0 add \u003Cowner\u002Frepo@skill>\n\nvercel-labs\u002Fagent-skills@vercel-react-best-practices\n└ https:\u002F\u002Fskills.sh\u002Fvercel-labs\u002Fagent-skills\u002Fvercel-react-best-practices\n```\n\n### Step 3: Present Options to the User\n\nWhen you find relevant skills, present them to the user with:\n\n1. The skill name and what it does\n2. The install command they can run\n3. A link to learn more at skills.sh\n\nExample response:\n\n```\nI found a skill that might help! The \"vercel-react-best-practices\" skill provides\nReact and Next.js performance optimization guidelines from Vercel Engineering.\n\nTo install it:\nnpx skills@1.7.0 add vercel-labs\u002Fagent-skills@vercel-react-best-practices\n\nLearn more: https:\u002F\u002Fskills.sh\u002Fvercel-labs\u002Fagent-skills\u002Fvercel-react-best-practices\n```\n\n### Step 4: Offer to Install\n\nBefore installing, **show the user the skill's contents** — fetch and display its `SKILL.md` (and any hook or script it ships) so an install is an informed choice, not a blind fetch. Then:\n\n```bash\nnpx skills@1.7.0 add \u003Cowner\u002Frepo@skill>\n```\n\n- **Keep the confirmation prompt** — do not pass `-y`. The prompt is the user's last look before third-party content lands.\n- **Default to project scope** — omit `-g`. Install globally (`-g`, user-level, every project) only when the user explicitly asks for that reach.\n- **Pin to a reviewed commit, not the moving head** — a bare `owner\u002Frepo@skill` takes the repository head at fetch time; where the tool supports a ref, name the commit the user reviewed (see the tool's ref syntax), so a later push to that repo cannot change what is installed.\n\n## Common Skill Categories\n\nWhen searching, consider these common categories:\n\n| Category        | Example Queries                          |\n| --------------- | ---------------------------------------- |\n| Web Development | react, nextjs, typescript, css, tailwind |\n| Testing         | testing, jest, playwright, e2e           |\n| DevOps          | deploy, docker, kubernetes, ci-cd        |\n| Documentation   | docs, readme, changelog, api-docs        |\n| Code Quality    | review, lint, refactor, best-practices   |\n| Design          | ui, ux, design-system, accessibility     |\n| Productivity    | workflow, automation, git                |\n\n## Tips for Effective Searches\n\n1. **Use specific keywords**: \"react testing\" is better than just \"testing\"\n2. **Try alternative terms**: If \"deploy\" doesn't work, try \"deployment\" or \"ci-cd\"\n3. **Check popular sources**: Many skills come from `vercel-labs\u002Fagent-skills` or `ComposioHQ\u002Fawesome-claude-skills`\n\n## When No Skills Are Found\n\nIf no relevant skills exist:\n\n1. Acknowledge that no existing skill was found\n2. Offer to help with the task directly using your general capabilities\n3. If the workflow recurs, first consider extending an existing clauDNA skill, lens or mode. For a pack contribution, use a clauDNA source checkout and the [contribution workflow](https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002FCONTRIBUTING.md) and [authoring guide](https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fdocumentation\u002Fguides\u002FSKILL_AUTHORING_GUIDE.md). The source-only `skill-scaffold` requires that checkout context and is excluded from the installed Codex catalog.\n\nExample:\n\n```\nI searched for skills related to \"xyz\" but didn't find any matches.\nI can still help you with this task directly.\n\nIf this becomes a repeatable clauDNA workflow, we can extend an existing skill\nor propose an addition through clauDNA's source-checkout contribution workflow.\n```\n",{"name":5,"requires":48,"description":7,"user-invocable":51},[49],{"cli":34,"reason":50},"Node package runner for skills CLI",true,"main","fc776f04574726e261087dbb521c1831bf0ea9d5","skills\u002Ffind-skills",1,"https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA","https:\u002F\u002Fgithub.com\u002FClaudfather","https:\u002F\u002Fcrog.gg","Rise of the machines","2026-11-08 21:32:41",{"source":8,"skillName":5,"commands":62,"prompt":71,"zipAvailable":51},[63,65,68],{"tool":34,"command":64},"npx skills add Claudfather\u002FclauDNA --skill find-skills",{"tool":66,"command":67},"bunx","bunx skills add Claudfather\u002FclauDNA --skill find-skills",{"tool":69,"command":70},"pnpm","pnpm dlx skills add Claudfather\u002FclauDNA --skill find-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Ffind-skills\u002FSKILL.md",[],[74,99,109,132,156,171],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":43},"01M71T1STJ99BE1C0JYHCQW0XN","example-review","Use when you want to review pull requests with detailed, actionable feedback on code quality, correctness, and maintainability.","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalid-package\u002FSKILL.md",[],[81,82,83,84,85,86,87,88,89,90,30,31,91,92,93,94,95,96,97,98],"review","example","example review","actionable","pull requests","with","code","correctness","Bash","you","gh","gh pr","diff","view","pr","code quality","feedback","pull",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":43},"01M71T1RMCD30MAJC954JC7580","bad-skill","Too short","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Ffailing-package\u002FSKILL.md",[],[106,107,108],"bad","bad skill","short",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":43},"01M71T1NS97NJ2MQ993V7FBES7","worktree","Use when starting feature work that needs isolation from the current workspace, or when running multiple Claude sessions in parallel on different branches — creates and manages git worktrees. For fetching latest main into every existing worktree and branch across your sibling repos, use \u002Fclaudna:sync-branches instead.","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Fworktree\u002FSKILL.md",[],[111,116,117,118,119,120,121,122,123,124,125,126,30,127,52,128,129,130,38,131],"sync","repos","git","isolation","running","sessions","worktrees","work","across","needs","git worktrees","claude sessions","branches","branch","parallel","feature",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":43},"01M71T1HNVG1CZY8P904P6RB7P","weigh-development-paths","Use when at a development junction with multiple viable approaches — architecture choices, refactoring strategies, where to put new code, or which pattern to follow. Triggers on 'which approach', 'how should I', 'Option A vs B', or any point where the next step isn't obvious and the wrong choice creates rework.","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Fweigh-development-paths\u002FSKILL.md",[],[139,140,141,142,143,144,145,146,147,27,148,149,150,87,30,151,152,153,154,155],"development","weigh development paths","paths","next step","path","refactoring","choice","pattern","at","next","strategies","architecture","auto","new","junction","option","which",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":43},"01M71T1ECV1T5E168GH70AY5B3","verify-completion","Use when about to claim work is complete, fixed, or passing -- requires running verification commands and confirming output before making any success claims.","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Fverify-completion\u002FSKILL.md",[],[163,164,165,166,120,36,167,26,123,168,169,170,30,31],"verify completion","verify","claim","complete","commands","verification","claims","output",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":180,"publishedAt":43},"01M71T1BC1HA7XQH0Q1H574FYS","vercel","Use for Vercel operations — deploy to production or preview (or roll back), view, filter, or debug deployment logs, or check project status (deployments, domains, env vars, config). Replaces \u002Fvercel-deploy, \u002Fvercel-logs, \u002Fvercel-status.","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Fvercel\u002FSKILL.md",[177],{"categoryNo":178,"categoryName":179,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[173,181,182,183,184,185,186,187,188,31,189,36,190,191,192,193,38,94,194,195],"inspection","check","filter","env","logs","preview","debug deployment","debug","deployments","domains","deployment","env vars","project","project status","back"]