[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BWYBZ7XMZTHMPQD9XTWFAV":3,"skill-same:01M7BWYBZ7XMZTHMPQD9XTWFAV":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":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BWYBZ7XMZTHMPQD9XTWFAV","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.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Plugin-插件协议\u002FYYC3-Plugin-插件协议-plugins\u002Ffind-skills\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]` - Search for skills interactively or by keyword\n- `npx skills add \u003Cpackage>` - Install a skill from GitHub or other sources\n- `npx skills check` - Check for skill updates\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: Search for Skills\n\nRun the find command with a relevant query:\n\n```bash\nnpx skills find [query]\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\nThe command will return results like:\n\n```\nInstall with npx skills 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\nIf no relevant results are found, try ClawHub as a fallback (see \"ClawHub Fallback\" section below).\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 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: Detect Current Client\n\nBefore installing, detect which client is running by checking the `__CFBundleIdentifier` environment variable:\n\n```bash\necho $__CFBundleIdentifier\n```\n\nDetermine the target skills directory based on the result:\n\n| `__CFBundleIdentifier` contains | Client    | Target skills dir        |\n| ------------------------------- | --------- | ------------------------ |\n| `codebuddy`                     | CodeBuddy | `~\u002F.codebuddy\u002Fskills\u002F`   |\n| anything else \u002F empty \u002F unset   | WorkBuddy | `~\u002F.workbuddy\u002Fskills\u002F`   |\n\n**Default to WorkBuddy**: If the variable is empty, unset, or contains any value other than `codebuddy`, treat the current client as WorkBuddy.\n\n### Step 5: Install the Skill\n\nIf the user wants to proceed, install the skill:\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### Step 6: Ensure Skill Is in the Correct Directory\n\nAfter installation, if the current client is WorkBuddy (detected in Step 4), verify the skill exists at `~\u002F.workbuddy\u002Fskills\u002F\u003Cskill-name>`. The CLI typically installs to `~\u002F.agents\u002Fskills\u002F\u003Cskill-name>\u002F` and may not automatically link to WorkBuddy's directory.\n\n```bash\n# Check if skill already exists in WorkBuddy's directory\nls -la ~\u002F.workbuddy\u002Fskills\u002F\u003Cskill-name>\n```\n\nIf the skill is missing from `~\u002F.workbuddy\u002Fskills\u002F`, check `~\u002F.agents\u002Fskills\u002F\u003Cskill-name>\u002F` and create a symlink:\n\n```bash\n# If installed at ~\u002F.agents\u002Fskills\u002F\u003Cskill-name>, create symlink\nln -s ..\u002F..\u002F.agents\u002Fskills\u002F\u003Cskill-name> ~\u002F.workbuddy\u002Fskills\u002F\u003Cskill-name>\n```\n\nIf the skill is not in `~\u002F.agents\u002Fskills\u002F` either, find where it was actually installed (e.g., `~\u002F.codebuddy\u002Fskills\u002F\u003Cskill-name>`) and copy it:\n\n```bash\ncp -r \u003Cinstalled-path> ~\u002F.workbuddy\u002Fskills\u002F\u003Cskill-name>\n```\n\nAlways confirm the skill is accessible at the target directory before reporting success to the user.\n\n## ClawHub Fallback\n\nIf `npx skills find` returns no relevant results, try ClawHub (the OpenClaw skill registry) as a secondary source:\n\n```bash\nnpx clawhub search [query]\n```\n\nIf a match is found, install it directly to the target directory (detected in Step 4):\n\n```bash\n# For WorkBuddy (default):\nnpx clawhub install \u003Cslug> --workdir ~ --dir .workbuddy\u002Fskills\n\n# For CodeBuddy:\nnpx clawhub install \u003Cslug> --workdir ~ --dir .codebuddy\u002Fskills\n```\n\nAfter ClawHub installation, verify the skill is in the target directory (same as Step 6).\n\n**Browse ClawHub skills at:** https:\u002F\u002Fclawhub.com\u002F\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 neither Vercel Skills nor ClawHub has relevant results:\n\n1. Acknowledge that no existing skill was found in either registry\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\" in both Vercel Skills and ClawHub\nbut 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]` - Search for skills interactively or by keyword\n- `npx skills add \u003Cpackage>` - Install a skill from GitHub or other sources\n- `npx skills check` - Check for skill updates\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: Search for Skills\n\nRun the find command with a relevant query:\n\n```bash\nnpx skills find [query]\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\nThe command will return results like:\n\n```\nInstall with npx skills 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\nIf no relevant results are found, try ClawHub as a fallback (see \"ClawHub Fallback\" section below).\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 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: Detect Current Client\n\nBefore installing, detect which client is running by checking the `__CFBundleIdentifier` environment variable:\n\n```bash\necho $__CFBundleIdentifier\n```\n\nDetermine the target skills directory based on the result:\n\n| `__CFBundleIdentifier` contains | Client    | Target skills dir        |\n| ------------------------------- | --------- | ------------------------ |\n| `codebuddy`                     | CodeBuddy | `~\u002F.codebuddy\u002Fskills\u002F`   |\n| anything else \u002F empty \u002F unset   | WorkBuddy | `~\u002F.workbuddy\u002Fskills\u002F`   |\n\n**Default to WorkBuddy**: If the variable is empty, unset, or contains any value other than `codebuddy`, treat the current client as WorkBuddy.\n\n### Step 5: Install the Skill\n\nIf the user wants to proceed, install the skill:\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### Step 6: Ensure Skill Is in the Correct Directory\n\nAfter installation, if the current client is WorkBuddy (detected in Step 4), verify the skill exists at `~\u002F.workbuddy\u002Fskills\u002F\u003Cskill-name>`. The CLI typically installs to `~\u002F.agents\u002Fskills\u002F\u003Cskill-name>\u002F` and may not automatically link to WorkBuddy's directory.\n\n```bash\n# Check if skill already exists in WorkBuddy's directory\nls -la ~\u002F.workbuddy\u002Fskills\u002F\u003Cskill-name>\n```\n\nIf the skill is missing from `~\u002F.workbuddy\u002Fskills\u002F`, check `~\u002F.agents\u002Fskills\u002F\u003Cskill-name>\u002F` and create a symlink:\n\n```bash\n# If installed at ~\u002F.agents\u002Fskills\u002F\u003Cskill-name>, create symlink\nln -s ..\u002F..\u002F.agents\u002Fskills\u002F\u003Cskill-name> ~\u002F.workbuddy\u002Fskills\u002F\u003Cskill-name>\n```\n\nIf the skill is not in `~\u002F.agents\u002Fskills\u002F` either, find where it was actually installed (e.g., `~\u002F.codebuddy\u002Fskills\u002F\u003Cskill-name>`) and copy it:\n\n```bash\ncp -r \u003Cinstalled-path> ~\u002F.workbuddy\u002Fskills\u002F\u003Cskill-name>\n```\n\nAlways confirm the skill is accessible at the target directory before reporting success to the user.\n\n## ClawHub Fallback\n\nIf `npx skills find` returns no relevant results, try ClawHub (the OpenClaw skill registry) as a secondary source:\n\n```bash\nnpx clawhub search [query]\n```\n\nIf a match is found, install it directly to the target directory (detected in Step 4):\n\n```bash\n# For WorkBuddy (default):\nnpx clawhub install \u003Cslug> --workdir ~ --dir .workbuddy\u002Fskills\n\n# For CodeBuddy:\nnpx clawhub install \u003Cslug> --workdir ~ --dir .codebuddy\u002Fskills\n```\n\nAfter ClawHub installation, verify the skill is in the target directory (same as Step 6).\n\n**Browse ClawHub skills at:** https:\u002F\u002Fclawhub.com\u002F\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 neither Vercel Skills nor ClawHub has relevant results:\n\n1. Acknowledge that no existing skill was found in either registry\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\" in both Vercel Skills and ClawHub\nbut 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","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Plugin-插件协议\u002FYYC3-Plugin-插件协议-plugins\u002Ffind-skills\u002Fskills\u002Ffind-skills",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill find-skills",{"tool":39,"command":40},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill find-skills",{"tool":42,"command":43},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill find-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Plugin-插件协议\u002FYYC3-Plugin-插件协议-plugins\u002Ffind-skills\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},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\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},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\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},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\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},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\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},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\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},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]