[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CKNP5F6EYY2S7SVDW00ACD":3,"skill-same:01M7CKNP5F6EYY2S7SVDW00ACD":53},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7CKNP5F6EYY2S7SVDW00ACD","issues",null,"Interact with GitHub issues - create, list, and view issues.","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-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fissues\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: issues\ndescription: Interact with GitHub issues - create, list, and view issues.\nallowed-tools: Bash(gh *)\nrisk: unknown\nsource: community\nmetadata:\n  author: Shpigford\n  version: \"1.0\"\n---\n\nInteract with GitHub issues - create, list, and view issues.\n\n## When to Use\n- The user wants to create, list, inspect, or otherwise work with GitHub issues.\n- The task involves issue intake or repository issue management through the GitHub CLI workflow.\n- You need a guided issue flow that gathers titles, descriptions, and action selection before running commands.\n\n## Instructions\n\nThis command helps you work with GitHub issues using the `gh` CLI.\n\n### Step 1: Determine Action\n\nUse AskUserQuestion to ask what the user wants to do:\n\n**Question:**\n- question: \"What would you like to do with GitHub issues?\"\n- header: \"Action\"\n- multiSelect: false\n- options:\n  - label: \"Create new issue\"\n    description: \"Open a new issue with title, body, and optional labels\"\n  - label: \"List issues\"\n    description: \"View open issues in the current repository\"\n  - label: \"View issue\"\n    description: \"See details of a specific issue by number\"\n\n---\n\n## If \"Create new issue\" selected:\n\n### Step 2a: Get Issue Title\n\nUse AskUserQuestion to get the issue title:\n\n**Question:**\n- question: \"What's a short, scannable title for this issue? Keep it brief (5-10 words max) - details go in the body. (Use 'Other' to type your title)\"\n- header: \"Title\"\n- multiSelect: false\n- options:\n  - label: \"I'll type a title\"\n    description: \"Enter a concise title like 'Login button unresponsive' or 'Add dark mode support'\"\n\n**Title guidelines:**\n- Keep titles SHORT and scannable (5-10 words max)\n- Good: \"Fix broken password reset flow\"\n- Bad: \"When I try to reset my password and click the button nothing happens and I get an error\"\n- The description\u002Fbody is where details belong, not the title\n\nIf the user provides a long title, help them shorten it and move the details to the body.\n\n### Step 3a: Get Issue Body\n\nUse AskUserQuestion to gather the issue body content:\n\n**Question 1 - Issue type context:**\n- question: \"What type of issue is this?\"\n- header: \"Type\"\n- multiSelect: false\n- options:\n  - label: \"Bug\"\n    description: \"Something broken that needs fixing\"\n  - label: \"Enhancement\"\n    description: \"Improvement to existing functionality\"\n  - label: \"New feature\"\n    description: \"Brand new functionality\"\n  - label: \"Task\"\n    description: \"General work item or chore\"\n\n**Question 2 - Description:**\n- question: \"Now provide the full details. This is where you explain context, background, and specifics that didn't fit in the title. (Use 'Other' to type your description)\"\n- header: \"Description\"\n- multiSelect: false\n- options:\n  - label: \"I'll describe it in detail\"\n    description: \"Provide context, steps, examples, and any relevant information\"\n\nThe user will select \"Other\" here to provide their full description.\n\n**Description guidelines:**\n- This is where ALL the detail goes - be thorough\n- Include context: what were you doing, what's the background?\n- Include specifics: error messages, URLs, versions, etc.\n- The more detail here, the better - unlike the title which should be brief\n\n**Question 3 - For bugs, ask about reproduction:**\nIf issue type is \"Bug\", use AskUserQuestion:\n\n- question: \"Can you provide steps to reproduce this bug? (Use 'Other' to type steps)\"\n- header: \"Repro steps\"\n- multiSelect: false\n- options:\n  - label: \"Provide steps\"\n    description: \"I'll describe how to reproduce the issue\"\n  - label: \"Not reproducible\"\n    description: \"The bug is intermittent or hard to reproduce\"\n\n**Question 4 - Expected vs actual behavior (for bugs):**\nIf issue type is \"Bug\", use AskUserQuestion:\n\n- question: \"What did you expect to happen vs what actually happened? (Use 'Other' to describe)\"\n- header: \"Behavior\"\n- multiSelect: false\n- options:\n  - label: \"Describe behavior\"\n    description: \"I'll explain expected vs actual behavior\"\n\n### Step 4a: Get Labels (Optional)\n\nUse AskUserQuestion to select labels:\n\n- question: \"Which labels should we add? (if any)\"\n- header: \"Labels\"\n- multiSelect: true\n- options:\n  - label: \"bug\"\n    description: \"Something isn't working\"\n  - label: \"enhancement\"\n    description: \"New feature or request\"\n  - label: \"documentation\"\n    description: \"Improvements to docs\"\n  - label: \"good first issue\"\n    description: \"Good for newcomers\"\n\n### Step 5a: Create the Issue\n\nConstruct the issue body based on the type:\n\n**For Bug reports:**\n```\n## Description\n[User's description]\n\n## Steps to Reproduce\n[User's reproduction steps or \"Not easily reproducible\"]\n\n## Expected Behavior\n[What should happen]\n\n## Actual Behavior\n[What actually happens]\n```\n\n**For Feature requests\u002FEnhancements:**\n```\n## Description\n[User's description]\n\n## Use Case\n[Why this would be useful]\n```\n\n**For Tasks\u002FOther:**\n```\n## Description\n[User's description]\n```\n\nRun the gh command to create the issue:\n```bash\ngh issue create --title \"[title]\" --body \"[constructed body]\" --label \"[labels]\"\n```\n\nReport the issue URL back to the user.\n\n---\n\n## If \"List issues\" selected:\n\n### Step 2b: Filter Options\n\nUse AskUserQuestion to determine filtering:\n\n- question: \"How would you like to filter issues?\"\n- header: \"Filter\"\n- multiSelect: false\n- options:\n  - label: \"All open issues\"\n    description: \"Show all open issues\"\n  - label: \"Assigned to me\"\n    description: \"Issues assigned to the current user\"\n  - label: \"Created by me\"\n    description: \"Issues I created\"\n  - label: \"With specific label\"\n    description: \"Filter by a label\"\n\nIf \"With specific label\" selected, use AskUserQuestion:\n\n- question: \"Which label to filter by? (Use 'Other' for custom label)\"\n- header: \"Label\"\n- multiSelect: false\n- options:\n  - label: \"bug\"\n    description: \"Bug reports\"\n  - label: \"enhancement\"\n    description: \"Feature requests\"\n  - label: \"documentation\"\n    description: \"Documentation issues\"\n\n### Step 3b: List Issues\n\nRun the appropriate gh command:\n- All open: `gh issue list`\n- Assigned to me: `gh issue list --assignee @me`\n- Created by me: `gh issue list --author @me`\n- With label: `gh issue list --label \"[label]\"`\n\nDisplay the results in a clean format.\n\n---\n\n## If \"View issue\" selected:\n\n### Step 2c: Get Issue Number\n\nUse AskUserQuestion:\n\n- question: \"Which issue number would you like to view? (Use 'Other' to enter the number)\"\n- header: \"Issue #\"\n- multiSelect: false\n- options:\n  - label: \"Enter issue number\"\n    description: \"I'll type the issue number\"\n\n### Step 3c: View Issue\n\nRun: `gh issue view [number]`\n\nDisplay the issue details including title, body, labels, assignees, and comments.\n\n---\n\n## Error Handling\n\nIf `gh` command fails:\n1. Check if user is authenticated: `gh auth status`\n2. If not authenticated, inform user to run `gh auth login`\n3. Check if in a git repository with a GitHub remote\n4. Report specific error message to user\n\n## Important Notes\n\n- **Titles should be succinct** (5-10 words) - if a user provides a long title, help shorten it and move details to body\n- **Bodies should be detailed** - encourage users to provide thorough context, steps, and specifics\n- Always confirm the issue was created successfully by showing the URL\n- For issue bodies, preserve user's formatting and newlines\n- If the user provides minimal information, that's okay - create the issue with what they gave\n- Use HEREDOC for the body to preserve formatting:\n  ```bash\n  gh issue create --title \"Title\" --body \"$(cat \u003C\u003C'EOF'\n  Body content here\n  EOF\n  )\"\n  ```\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","Interact with GitHub issues - create, list, and view issues.\n\n## When to Use\n- The user wants to create, list, inspect, or otherwise work with GitHub issues.\n- The task involves issue intake or repository issue management through the GitHub CLI workflow.\n- You need a guided issue flow that gathers titles, descriptions, and action selection before running commands.\n\n## Instructions\n\nThis command helps you work with GitHub issues using the `gh` CLI.\n\n### Step 1: Determine Action\n\nUse AskUserQuestion to ask what the user wants to do:\n\n**Question:**\n- question: \"What would you like to do with GitHub issues?\"\n- header: \"Action\"\n- multiSelect: false\n- options:\n  - label: \"Create new issue\"\n    description: \"Open a new issue with title, body, and optional labels\"\n  - label: \"List issues\"\n    description: \"View open issues in the current repository\"\n  - label: \"View issue\"\n    description: \"See details of a specific issue by number\"\n\n---\n\n## If \"Create new issue\" selected:\n\n### Step 2a: Get Issue Title\n\nUse AskUserQuestion to get the issue title:\n\n**Question:**\n- question: \"What's a short, scannable title for this issue? Keep it brief (5-10 words max) - details go in the body. (Use 'Other' to type your title)\"\n- header: \"Title\"\n- multiSelect: false\n- options:\n  - label: \"I'll type a title\"\n    description: \"Enter a concise title like 'Login button unresponsive' or 'Add dark mode support'\"\n\n**Title guidelines:**\n- Keep titles SHORT and scannable (5-10 words max)\n- Good: \"Fix broken password reset flow\"\n- Bad: \"When I try to reset my password and click the button nothing happens and I get an error\"\n- The description\u002Fbody is where details belong, not the title\n\nIf the user provides a long title, help them shorten it and move the details to the body.\n\n### Step 3a: Get Issue Body\n\nUse AskUserQuestion to gather the issue body content:\n\n**Question 1 - Issue type context:**\n- question: \"What type of issue is this?\"\n- header: \"Type\"\n- multiSelect: false\n- options:\n  - label: \"Bug\"\n    description: \"Something broken that needs fixing\"\n  - label: \"Enhancement\"\n    description: \"Improvement to existing functionality\"\n  - label: \"New feature\"\n    description: \"Brand new functionality\"\n  - label: \"Task\"\n    description: \"General work item or chore\"\n\n**Question 2 - Description:**\n- question: \"Now provide the full details. This is where you explain context, background, and specifics that didn't fit in the title. (Use 'Other' to type your description)\"\n- header: \"Description\"\n- multiSelect: false\n- options:\n  - label: \"I'll describe it in detail\"\n    description: \"Provide context, steps, examples, and any relevant information\"\n\nThe user will select \"Other\" here to provide their full description.\n\n**Description guidelines:**\n- This is where ALL the detail goes - be thorough\n- Include context: what were you doing, what's the background?\n- Include specifics: error messages, URLs, versions, etc.\n- The more detail here, the better - unlike the title which should be brief\n\n**Question 3 - For bugs, ask about reproduction:**\nIf issue type is \"Bug\", use AskUserQuestion:\n\n- question: \"Can you provide steps to reproduce this bug? (Use 'Other' to type steps)\"\n- header: \"Repro steps\"\n- multiSelect: false\n- options:\n  - label: \"Provide steps\"\n    description: \"I'll describe how to reproduce the issue\"\n  - label: \"Not reproducible\"\n    description: \"The bug is intermittent or hard to reproduce\"\n\n**Question 4 - Expected vs actual behavior (for bugs):**\nIf issue type is \"Bug\", use AskUserQuestion:\n\n- question: \"What did you expect to happen vs what actually happened? (Use 'Other' to describe)\"\n- header: \"Behavior\"\n- multiSelect: false\n- options:\n  - label: \"Describe behavior\"\n    description: \"I'll explain expected vs actual behavior\"\n\n### Step 4a: Get Labels (Optional)\n\nUse AskUserQuestion to select labels:\n\n- question: \"Which labels should we add? (if any)\"\n- header: \"Labels\"\n- multiSelect: true\n- options:\n  - label: \"bug\"\n    description: \"Something isn't working\"\n  - label: \"enhancement\"\n    description: \"New feature or request\"\n  - label: \"documentation\"\n    description: \"Improvements to docs\"\n  - label: \"good first issue\"\n    description: \"Good for newcomers\"\n\n### Step 5a: Create the Issue\n\nConstruct the issue body based on the type:\n\n**For Bug reports:**\n```\n## Description\n[User's description]\n\n## Steps to Reproduce\n[User's reproduction steps or \"Not easily reproducible\"]\n\n## Expected Behavior\n[What should happen]\n\n## Actual Behavior\n[What actually happens]\n```\n\n**For Feature requests\u002FEnhancements:**\n```\n## Description\n[User's description]\n\n## Use Case\n[Why this would be useful]\n```\n\n**For Tasks\u002FOther:**\n```\n## Description\n[User's description]\n```\n\nRun the gh command to create the issue:\n```bash\ngh issue create --title \"[title]\" --body \"[constructed body]\" --label \"[labels]\"\n```\n\nReport the issue URL back to the user.\n\n---\n\n## If \"List issues\" selected:\n\n### Step 2b: Filter Options\n\nUse AskUserQuestion to determine filtering:\n\n- question: \"How would you like to filter issues?\"\n- header: \"Filter\"\n- multiSelect: false\n- options:\n  - label: \"All open issues\"\n    description: \"Show all open issues\"\n  - label: \"Assigned to me\"\n    description: \"Issues assigned to the current user\"\n  - label: \"Created by me\"\n    description: \"Issues I created\"\n  - label: \"With specific label\"\n    description: \"Filter by a label\"\n\nIf \"With specific label\" selected, use AskUserQuestion:\n\n- question: \"Which label to filter by? (Use 'Other' for custom label)\"\n- header: \"Label\"\n- multiSelect: false\n- options:\n  - label: \"bug\"\n    description: \"Bug reports\"\n  - label: \"enhancement\"\n    description: \"Feature requests\"\n  - label: \"documentation\"\n    description: \"Documentation issues\"\n\n### Step 3b: List Issues\n\nRun the appropriate gh command:\n- All open: `gh issue list`\n- Assigned to me: `gh issue list --assignee @me`\n- Created by me: `gh issue list --author @me`\n- With label: `gh issue list --label \"[label]\"`\n\nDisplay the results in a clean format.\n\n---\n\n## If \"View issue\" selected:\n\n### Step 2c: Get Issue Number\n\nUse AskUserQuestion:\n\n- question: \"Which issue number would you like to view? (Use 'Other' to enter the number)\"\n- header: \"Issue #\"\n- multiSelect: false\n- options:\n  - label: \"Enter issue number\"\n    description: \"I'll type the issue number\"\n\n### Step 3c: View Issue\n\nRun: `gh issue view [number]`\n\nDisplay the issue details including title, body, labels, assignees, and comments.\n\n---\n\n## Error Handling\n\nIf `gh` command fails:\n1. Check if user is authenticated: `gh auth status`\n2. If not authenticated, inform user to run `gh auth login`\n3. Check if in a git repository with a GitHub remote\n4. Report specific error message to user\n\n## Important Notes\n\n- **Titles should be succinct** (5-10 words) - if a user provides a long title, help shorten it and move details to body\n- **Bodies should be detailed** - encourage users to provide thorough context, steps, and specifics\n- Always confirm the issue was created successfully by showing the URL\n- For issue bodies, preserve user's formatting and newlines\n- If the user provides minimal information, that's okay - create the issue with what they gave\n- Use HEREDOC for the body to preserve formatting:\n  ```bash\n  gh issue create --title \"Title\" --body \"$(cat \u003C\u003C'EOF'\n  Body content here\n  EOF\n  )\"\n  ```\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"metadata":26,"description":7,"allowed-tools":29},"unknown","community",{"author":27,"version":28},"Shpigford","1.0","Bash(gh *)","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fissues",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":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill issues",{"tool":45,"command":46},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill issues",{"tool":48,"command":49},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fissues\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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",[],[]]