[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A15ZE1E365V673REFTSY7M":3,"skill-same:01M7A15ZE1E365V673REFTSY7M":47},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":29,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7A15ZE1E365V673REFTSY7M","find-skills",null,"Helps users discover and install agent skills when they ask questions like \"how do I do X\", \"find a skill for X\", \"is there a skill that can...\", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.","openvetta\u002Fopen-vetta","openvetta","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F310452651?v=4","01M7A143Q6S7A6WZEJYZN5TTYM","Open Vetta","01M7A143R600YHMC29N957HQP8",299,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fopenvetta\u002Fopen-vetta\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffind-skills\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: find-skills\ndescription: Helps users discover and install agent skills when they ask questions like \"how do I do X\", \"find a skill for X\", \"is there a skill that can...\", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.\n---\n\n# Find Skills\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`) 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 find [query] [--owner \u003Cowner>]` - Search for skills interactively or by keyword, optionally scoped to a GitHub owner\n- `npx skills add \u003Cpackage>` - Install a skill from GitHub or other sources\n- `npx skills update` - Update all installed skills\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: Check the Leaderboard First\n\nBefore running a CLI search, check the [skills.sh leaderboard](https:\u002F\u002Fskills.sh\u002F) to see if a well-known skill already exists for the domain. The leaderboard ranks skills by total installs, surfacing the most popular and battle-tested options.\n\nFor example, top skills for web development include:\n- `vercel-labs\u002Fagent-skills` — React, Next.js, web design (100K+ installs each)\n- `anthropics\u002Fskills` — Frontend design, document processing (100K+ installs)\n\n### Step 3: Search for Skills\n\nIf the leaderboard doesn't cover the user's need, run the find command:\n\n```bash\nnpx skills find [query] [--owner \u003Cowner>]\n```\n\nFor example:\n\n- User asks \"how do I make my React app faster?\" → `npx skills find react performance`\n- User asks \"can you help me with PR reviews?\" → `npx skills find pr review`\n- User asks \"I need to create a changelog\" → `npx skills find changelog`\n\n### Step 4: Verify Quality Before Recommending\n\n**Do not recommend a skill based solely on search results.** Always verify:\n\n1. **Install count** — Prefer skills with 1K+ installs. Be cautious with anything under 100.\n2. **Source reputation** — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.\n3. **GitHub stars** — Check the source repository. A skill from a repo with \u003C100 stars should be treated with skepticism.\n\n### Step 5: 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 count and source\n3. The install command they can run\n4. A link to learn more at skills.sh\n\nExample response:\n\n```\nI found a skill that might help! The \"react-best-practices\" skill provides\nReact and Next.js performance optimization guidelines from Vercel Engineering.\n(185K installs)\n\nTo install it:\nnpx skills add vercel-labs\u002Fagent-skills@react-best-practices\n\nLearn more: https:\u002F\u002Fskills.sh\u002Fvercel-labs\u002Fagent-skills\u002Freact-best-practices\n```\n\n### Step 6: Offer to Install\n\nIf the user wants to proceed, you can install the skill for them:\n\n```bash\nnpx skills add \u003Cowner\u002Frepo@skill> -g -y\n```\n\nThe `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.\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. Suggest the user could create their own skill with `npx skills init`\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! Would you like me to proceed?\n\nIf this is something you do often, you could create your own skill:\nnpx skills init my-xyz-skill\n```\n","# Find Skills\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`) 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 find [query] [--owner \u003Cowner>]` - Search for skills interactively or by keyword, optionally scoped to a GitHub owner\n- `npx skills add \u003Cpackage>` - Install a skill from GitHub or other sources\n- `npx skills update` - Update all installed skills\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: Check the Leaderboard First\n\nBefore running a CLI search, check the [skills.sh leaderboard](https:\u002F\u002Fskills.sh\u002F) to see if a well-known skill already exists for the domain. The leaderboard ranks skills by total installs, surfacing the most popular and battle-tested options.\n\nFor example, top skills for web development include:\n- `vercel-labs\u002Fagent-skills` — React, Next.js, web design (100K+ installs each)\n- `anthropics\u002Fskills` — Frontend design, document processing (100K+ installs)\n\n### Step 3: Search for Skills\n\nIf the leaderboard doesn't cover the user's need, run the find command:\n\n```bash\nnpx skills find [query] [--owner \u003Cowner>]\n```\n\nFor example:\n\n- User asks \"how do I make my React app faster?\" → `npx skills find react performance`\n- User asks \"can you help me with PR reviews?\" → `npx skills find pr review`\n- User asks \"I need to create a changelog\" → `npx skills find changelog`\n\n### Step 4: Verify Quality Before Recommending\n\n**Do not recommend a skill based solely on search results.** Always verify:\n\n1. **Install count** — Prefer skills with 1K+ installs. Be cautious with anything under 100.\n2. **Source reputation** — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.\n3. **GitHub stars** — Check the source repository. A skill from a repo with \u003C100 stars should be treated with skepticism.\n\n### Step 5: 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 count and source\n3. The install command they can run\n4. A link to learn more at skills.sh\n\nExample response:\n\n```\nI found a skill that might help! The \"react-best-practices\" skill provides\nReact and Next.js performance optimization guidelines from Vercel Engineering.\n(185K installs)\n\nTo install it:\nnpx skills add vercel-labs\u002Fagent-skills@react-best-practices\n\nLearn more: https:\u002F\u002Fskills.sh\u002Fvercel-labs\u002Fagent-skills\u002Freact-best-practices\n```\n\n### Step 6: Offer to Install\n\nIf the user wants to proceed, you can install the skill for them:\n\n```bash\nnpx skills add \u003Cowner\u002Frepo@skill> -g -y\n```\n\nThe `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.\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. Suggest the user could create their own skill with `npx skills init`\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! Would you like me to proceed?\n\nIf this is something you do often, you could create your own skill:\nnpx skills init my-xyz-skill\n```\n",{"name":5,"description":7},"main","a4aeb31ba1b80e809bf4ddc0406287429275e34e",".agents\u002Fskills\u002Ffind-skills",50,"https:\u002F\u002Fgithub.com\u002Fopenvetta\u002Fopen-vetta","https:\u002F\u002Fwww.openvetta.com","https:\u002F\u002Fgithub.com\u002Fopenvetta","Open-source, local-first AI agent for coding and real work.","2026-11-14 00:11:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add openvetta\u002Fopen-vetta --skill find-skills",{"tool":39,"command":40},"bunx","bunx skills add openvetta\u002Fopen-vetta --skill find-skills",{"tool":42,"command":43},"pnpm","pnpm dlx skills add openvetta\u002Fopen-vetta --skill find-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenvetta\u002Fopen-vetta\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffind-skills\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7A1CADNDSES6MRAARA1WXMB","publish-ability","Publish a skill, MCP server, plugin, or bundle to the Vetta ability marketplace. Use when the user asks to upload\u002Fpublish\u002Fsubmit an ability, put a plugin on the marketplace, share a skill with other users, or migrate an existing package into Vetta.","https:\u002F\u002Fgithub.com\u002Fopenvetta\u002Fopen-vetta\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-presets\u002Fpublish-ability\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7A1C5VD4NEZHMZMCXF8J47M","install-ability","在本机 Vetta 中安装能力——插件（plugin）、Skill 与 MCP 服务器。用户说「装一个插件 \u002F install plugin \u002F 从能力市场安装 \u002F 加一个 MCP server \u002F 配置 MCP \u002F 装个 skill」，或插件装完没生效、需要 reload、pending 版本没应用时使用。不用于安装 npm 依赖、IDE 插件、浏览器扩展，也不用于开发插件（那是 plugin-workbench）或创作 Skill（那是 create-skill）。","https:\u002F\u002Fgithub.com\u002Fopenvetta\u002Fopen-vetta\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-presets\u002Finstall-ability\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7A1C0414EPE2EWRD5B26HWC","create-skill","Create or update Vetta-compatible Agent Skills. Use when the user asks to create a skill, add a SKILL.md workflow, register a skill in skills-manifest.json, package a skill in a Vetta plugin, or add a built-in Vetta skill preset.","https:\u002F\u002Fgithub.com\u002Fopenvetta\u002Fopen-vetta\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-presets\u002Fcreate-skill\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7A1BNBJ5XJKWND9XFJKP0FX","vetta-ui-design","Build and edit design documents (.vetd) on the Vetta design canvas — app screens, landing pages, slides, posters, infographics. Use when the user asks for a UI design, mockup, screen, deck, or poster, or attaches a design frame\u002Felement from the canvas. Frames are real React (TSX) routes, not pictures. Do NOT use for ordinary front-end work in the user's own codebase — building, styling or reworking pages of a real app is that repo's job, and none of the vetd_* tools or canvas rules here apply to it.","https:\u002F\u002Fgithub.com\u002Fopenvetta\u002Fopen-vetta\u002Fblob\u002Fmain\u002Fpackages\u002Fplugins\u002Fpresets\u002Fvetta-ui-design\u002Fagent\u002Fskills\u002Fvetta-ui-design\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7A1BFJSH10EZFJ4J56M8E2Z","remotion-video","Create, modify, and render Remotion React video projects in the current Vetta conversation workspace. Use for requests to make programmatic videos, motion graphics, animated explainers, social videos, data videos, or to edit an existing Remotion composition and export it as MP4.","https:\u002F\u002Fgithub.com\u002Fopenvetta\u002Fopen-vetta\u002Fblob\u002Fmain\u002Fpackages\u002Fplugins\u002Fpresets\u002Fremotion-renderer\u002Fagent\u002Fskills\u002Fremotion-video\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7A1B8WD792ETC0XYJV8GNNB","plugin-workbench","Create, implement, build, pack, install, reload, and manage Vetta desktop plugins for non-developers. Use whenever the user wants a Vetta plugin, plugin scaffolding, apply a `.vettapkg` package to Vetta, edit plugin.json name\u002FguidingWords, or debug plugin load\u002Finstall. Requires the Plugin Workbench input-bar toggle (hard isolation). The plugin handbook ships inside the project's own @vetta-org\u002Fplugin-sdk; locate it with the bundled CLI's docs command.","https:\u002F\u002Fgithub.com\u002Fopenvetta\u002Fopen-vetta\u002Fblob\u002Fmain\u002Fpackages\u002Fplugins\u002Fpresets\u002Fplugin-workbench\u002Fagent\u002Fskills\u002Fplugin-workbench\u002FSKILL.md",[],[]]