[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BGPBPCYCSTSZG8QB9NTWHD":3,"skill-same:01M7BGPBPCYCSTSZG8QB9NTWHD":51},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7BGPBPCYCSTSZG8QB9NTWHD","jira-automation",null,"Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.","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-AI-应用工具\u002FYYC3-AI-应用工具-buildwithclaude\u002Fplugins\u002Fall-skills\u002Fskills\u002Fjira-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: jira-automation\ndescription: \"Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\ncategory: project-management\n---\n\n# Jira Automation via Rube MCP\n\nAutomate Jira operations through Composio's Jira toolkit via Rube MCP.\n\n**Toolkit docs**: [composio.dev\u002Ftoolkits\u002Fjira](https:\u002F\u002Fcomposio.dev\u002Ftoolkits\u002Fjira)\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Jira connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\n3. If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Search and Filter Issues\n\n**When to use**: User wants to find issues using JQL or browse project issues\n\n**Tool sequence**:\n1. `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` - Search with JQL query [Required]\n2. `JIRA_GET_ISSUE` - Get full details of a specific issue [Optional]\n\n**Key parameters**:\n- `jql`: JQL query string (e.g., `project = PROJ AND status = \"In Progress\"`)\n- `maxResults`: Max results per page (default 50, max 100)\n- `startAt`: Pagination offset\n- `fields`: Array of field names to return\n- `issueIdOrKey`: Issue key like 'PROJ-123' for GET_ISSUE\n\n**Pitfalls**:\n- JQL field names are case-sensitive and must match Jira configuration\n- Custom fields use IDs like `customfield_10001`, not display names\n- Results are paginated; check `total` vs `startAt + maxResults` to continue\n\n### 2. Create and Edit Issues\n\n**When to use**: User wants to create new issues or update existing ones\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List projects to find project key [Prerequisite]\n2. `JIRA_GET_FIELDS` - Get available fields and their IDs [Prerequisite]\n3. `JIRA_CREATE_ISSUE` - Create a new issue [Required]\n4. `JIRA_EDIT_ISSUE` - Update fields on an existing issue [Optional]\n5. `JIRA_ASSIGN_ISSUE` - Assign issue to a user [Optional]\n\n**Key parameters**:\n- `project`: Project key (e.g., 'PROJ')\n- `issuetype`: Issue type name (e.g., 'Bug', 'Story', 'Task')\n- `summary`: Issue title\n- `description`: Issue description (Atlassian Document Format or plain text)\n- `issueIdOrKey`: Issue key for edits\n\n**Pitfalls**:\n- Issue types and required fields vary by project; use GET_FIELDS to check\n- Custom fields require exact field IDs, not display names\n- Description may need Atlassian Document Format (ADF) for rich content\n\n### 3. Manage Sprints and Boards\n\n**When to use**: User wants to work with agile boards, sprints, and backlogs\n\n**Tool sequence**:\n1. `JIRA_LIST_BOARDS` - List all boards [Prerequisite]\n2. `JIRA_LIST_SPRINTS` - List sprints for a board [Required]\n3. `JIRA_MOVE_ISSUE_TO_SPRINT` - Move issue to a sprint [Optional]\n4. `JIRA_CREATE_SPRINT` - Create a new sprint [Optional]\n\n**Key parameters**:\n- `boardId`: Board ID from LIST_BOARDS\n- `sprintId`: Sprint ID for move operations\n- `name`: Sprint name for creation\n- `startDate`\u002F`endDate`: Sprint dates in ISO format\n\n**Pitfalls**:\n- Boards and sprints are specific to Jira Software (not Jira Core)\n- Only one sprint can be active at a time per board\n\n### 4. Manage Comments\n\n**When to use**: User wants to add or view comments on issues\n\n**Tool sequence**:\n1. `JIRA_LIST_ISSUE_COMMENTS` - List existing comments [Optional]\n2. `JIRA_ADD_COMMENT` - Add a comment to an issue [Required]\n\n**Key parameters**:\n- `issueIdOrKey`: Issue key like 'PROJ-123'\n- `body`: Comment body (supports ADF for rich text)\n\n**Pitfalls**:\n- Comments support ADF (Atlassian Document Format) for formatting\n- Mentions use account IDs, not usernames\n\n### 5. Manage Projects and Users\n\n**When to use**: User wants to list projects, find users, or manage project roles\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List all projects [Optional]\n2. `JIRA_GET_PROJECT` - Get project details [Optional]\n3. `JIRA_FIND_USERS` \u002F `JIRA_GET_ALL_USERS` - Search for users [Optional]\n4. `JIRA_GET_PROJECT_ROLES` - List project roles [Optional]\n5. `JIRA_ADD_USERS_TO_PROJECT_ROLE` - Add user to role [Optional]\n\n**Key parameters**:\n- `projectIdOrKey`: Project key\n- `query`: Search text for FIND_USERS\n- `roleId`: Role ID for role operations\n\n**Pitfalls**:\n- User operations use account IDs (not email or display name)\n- Project roles differ from global permissions\n\n## Common Patterns\n\n### JQL Syntax\n\n**Common operators**:\n- `project = \"PROJ\"` - Filter by project\n- `status = \"In Progress\"` - Filter by status\n- `assignee = currentUser()` - Current user's issues\n- `created >= -7d` - Created in last 7 days\n- `labels = \"bug\"` - Filter by label\n- `priority = High` - Filter by priority\n- `ORDER BY created DESC` - Sort results\n\n**Combinators**:\n- `AND` - Both conditions\n- `OR` - Either condition\n- `NOT` - Negate condition\n\n### Pagination\n\n- Use `startAt` and `maxResults` parameters\n- Check `total` in response to determine remaining pages\n- Continue until `startAt + maxResults >= total`\n\n## Known Pitfalls\n\n**Field Names**:\n- Custom fields use IDs like `customfield_10001`\n- Use JIRA_GET_FIELDS to discover field IDs and names\n- Field names in JQL may differ from API field names\n\n**Authentication**:\n- Jira Cloud uses account IDs, not usernames\n- Site URL must be configured correctly in the connection\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Search issues (JQL) | JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST | jql, maxResults |\n| Get issue | JIRA_GET_ISSUE | issueIdOrKey |\n| Create issue | JIRA_CREATE_ISSUE | project, issuetype, summary |\n| Edit issue | JIRA_EDIT_ISSUE | issueIdOrKey, fields |\n| Assign issue | JIRA_ASSIGN_ISSUE | issueIdOrKey, accountId |\n| Add comment | JIRA_ADD_COMMENT | issueIdOrKey, body |\n| List comments | JIRA_LIST_ISSUE_COMMENTS | issueIdOrKey |\n| List projects | JIRA_GET_ALL_PROJECTS | (none) |\n| Get project | JIRA_GET_PROJECT | projectIdOrKey |\n| List boards | JIRA_LIST_BOARDS | (none) |\n| List sprints | JIRA_LIST_SPRINTS | boardId |\n| Move to sprint | JIRA_MOVE_ISSUE_TO_SPRINT | sprintId, issues |\n| Create sprint | JIRA_CREATE_SPRINT | name, boardId |\n| Find users | JIRA_FIND_USERS | query |\n| Get fields | JIRA_GET_FIELDS | (none) |\n| List filters | JIRA_LIST_FILTERS | (none) |\n| Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey |\n| Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey |\n\n---\n*Powered by [Composio](https:\u002F\u002Fcomposio.dev)*\n","# Jira Automation via Rube MCP\n\nAutomate Jira operations through Composio's Jira toolkit via Rube MCP.\n\n**Toolkit docs**: [composio.dev\u002Ftoolkits\u002Fjira](https:\u002F\u002Fcomposio.dev\u002Ftoolkits\u002Fjira)\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Jira connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\n3. If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Search and Filter Issues\n\n**When to use**: User wants to find issues using JQL or browse project issues\n\n**Tool sequence**:\n1. `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` - Search with JQL query [Required]\n2. `JIRA_GET_ISSUE` - Get full details of a specific issue [Optional]\n\n**Key parameters**:\n- `jql`: JQL query string (e.g., `project = PROJ AND status = \"In Progress\"`)\n- `maxResults`: Max results per page (default 50, max 100)\n- `startAt`: Pagination offset\n- `fields`: Array of field names to return\n- `issueIdOrKey`: Issue key like 'PROJ-123' for GET_ISSUE\n\n**Pitfalls**:\n- JQL field names are case-sensitive and must match Jira configuration\n- Custom fields use IDs like `customfield_10001`, not display names\n- Results are paginated; check `total` vs `startAt + maxResults` to continue\n\n### 2. Create and Edit Issues\n\n**When to use**: User wants to create new issues or update existing ones\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List projects to find project key [Prerequisite]\n2. `JIRA_GET_FIELDS` - Get available fields and their IDs [Prerequisite]\n3. `JIRA_CREATE_ISSUE` - Create a new issue [Required]\n4. `JIRA_EDIT_ISSUE` - Update fields on an existing issue [Optional]\n5. `JIRA_ASSIGN_ISSUE` - Assign issue to a user [Optional]\n\n**Key parameters**:\n- `project`: Project key (e.g., 'PROJ')\n- `issuetype`: Issue type name (e.g., 'Bug', 'Story', 'Task')\n- `summary`: Issue title\n- `description`: Issue description (Atlassian Document Format or plain text)\n- `issueIdOrKey`: Issue key for edits\n\n**Pitfalls**:\n- Issue types and required fields vary by project; use GET_FIELDS to check\n- Custom fields require exact field IDs, not display names\n- Description may need Atlassian Document Format (ADF) for rich content\n\n### 3. Manage Sprints and Boards\n\n**When to use**: User wants to work with agile boards, sprints, and backlogs\n\n**Tool sequence**:\n1. `JIRA_LIST_BOARDS` - List all boards [Prerequisite]\n2. `JIRA_LIST_SPRINTS` - List sprints for a board [Required]\n3. `JIRA_MOVE_ISSUE_TO_SPRINT` - Move issue to a sprint [Optional]\n4. `JIRA_CREATE_SPRINT` - Create a new sprint [Optional]\n\n**Key parameters**:\n- `boardId`: Board ID from LIST_BOARDS\n- `sprintId`: Sprint ID for move operations\n- `name`: Sprint name for creation\n- `startDate`\u002F`endDate`: Sprint dates in ISO format\n\n**Pitfalls**:\n- Boards and sprints are specific to Jira Software (not Jira Core)\n- Only one sprint can be active at a time per board\n\n### 4. Manage Comments\n\n**When to use**: User wants to add or view comments on issues\n\n**Tool sequence**:\n1. `JIRA_LIST_ISSUE_COMMENTS` - List existing comments [Optional]\n2. `JIRA_ADD_COMMENT` - Add a comment to an issue [Required]\n\n**Key parameters**:\n- `issueIdOrKey`: Issue key like 'PROJ-123'\n- `body`: Comment body (supports ADF for rich text)\n\n**Pitfalls**:\n- Comments support ADF (Atlassian Document Format) for formatting\n- Mentions use account IDs, not usernames\n\n### 5. Manage Projects and Users\n\n**When to use**: User wants to list projects, find users, or manage project roles\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List all projects [Optional]\n2. `JIRA_GET_PROJECT` - Get project details [Optional]\n3. `JIRA_FIND_USERS` \u002F `JIRA_GET_ALL_USERS` - Search for users [Optional]\n4. `JIRA_GET_PROJECT_ROLES` - List project roles [Optional]\n5. `JIRA_ADD_USERS_TO_PROJECT_ROLE` - Add user to role [Optional]\n\n**Key parameters**:\n- `projectIdOrKey`: Project key\n- `query`: Search text for FIND_USERS\n- `roleId`: Role ID for role operations\n\n**Pitfalls**:\n- User operations use account IDs (not email or display name)\n- Project roles differ from global permissions\n\n## Common Patterns\n\n### JQL Syntax\n\n**Common operators**:\n- `project = \"PROJ\"` - Filter by project\n- `status = \"In Progress\"` - Filter by status\n- `assignee = currentUser()` - Current user's issues\n- `created >= -7d` - Created in last 7 days\n- `labels = \"bug\"` - Filter by label\n- `priority = High` - Filter by priority\n- `ORDER BY created DESC` - Sort results\n\n**Combinators**:\n- `AND` - Both conditions\n- `OR` - Either condition\n- `NOT` - Negate condition\n\n### Pagination\n\n- Use `startAt` and `maxResults` parameters\n- Check `total` in response to determine remaining pages\n- Continue until `startAt + maxResults >= total`\n\n## Known Pitfalls\n\n**Field Names**:\n- Custom fields use IDs like `customfield_10001`\n- Use JIRA_GET_FIELDS to discover field IDs and names\n- Field names in JQL may differ from API field names\n\n**Authentication**:\n- Jira Cloud uses account IDs, not usernames\n- Site URL must be configured correctly in the connection\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Search issues (JQL) | JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST | jql, maxResults |\n| Get issue | JIRA_GET_ISSUE | issueIdOrKey |\n| Create issue | JIRA_CREATE_ISSUE | project, issuetype, summary |\n| Edit issue | JIRA_EDIT_ISSUE | issueIdOrKey, fields |\n| Assign issue | JIRA_ASSIGN_ISSUE | issueIdOrKey, accountId |\n| Add comment | JIRA_ADD_COMMENT | issueIdOrKey, body |\n| List comments | JIRA_LIST_ISSUE_COMMENTS | issueIdOrKey |\n| List projects | JIRA_GET_ALL_PROJECTS | (none) |\n| Get project | JIRA_GET_PROJECT | projectIdOrKey |\n| List boards | JIRA_LIST_BOARDS | (none) |\n| List sprints | JIRA_LIST_SPRINTS | boardId |\n| Move to sprint | JIRA_MOVE_ISSUE_TO_SPRINT | sprintId, issues |\n| Create sprint | JIRA_CREATE_SPRINT | name, boardId |\n| Find users | JIRA_FIND_USERS | query |\n| Get fields | JIRA_GET_FIELDS | (none) |\n| List filters | JIRA_LIST_FILTERS | (none) |\n| Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey |\n| Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey |\n\n---\n*Powered by [Composio](https:\u002F\u002Fcomposio.dev)*\n",{"name":5,"category":24,"requires":25,"description":7},"project-management",{"mcp":26},[27],"rube","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-AI-应用工具\u002FYYC3-AI-应用工具-buildwithclaude\u002Fplugins\u002Fall-skills\u002Fskills\u002Fjira-automation",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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill jira-automation",{"tool":43,"command":44},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill jira-automation",{"tool":46,"command":47},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill jira-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-buildwithclaude\u002Fplugins\u002Fall-skills\u002Fskills\u002Fjira-automation\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[]]