[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BY6PGFD9W5THJ3BWAFB2DS":3,"skill-same:01M7BY6PGFD9W5THJ3BWAFB2DS":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},"01M7BY6PGFD9W5THJ3BWAFB2DS","zendesk-automation",null,"Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. 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-Skills-技能包\u002FYYC3-Skills-技能包-all-skills\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: zendesk-automation\ndescription: \"Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\ncategory: customer-support\n---\n\n# Zendesk Automation via Rube MCP\n\nAutomate Zendesk operations through Composio's Zendesk toolkit via Rube MCP.\n\n**Toolkit docs**: [composio.dev\u002Ftoolkits\u002Fzendesk](https:\u002F\u002Fcomposio.dev\u002Ftoolkits\u002Fzendesk)\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Zendesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zendesk`\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 `zendesk`\n3. If connection is not ACTIVE, follow the returned auth link to complete Zendesk auth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Search Tickets\n\n**When to use**: User wants to view, filter, or search support tickets\n\n**Tool sequence**:\n1. `ZENDESK_LIST_ZENDESK_TICKETS` - List all tickets with pagination [Required]\n2. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get specific ticket details [Optional]\n\n**Key parameters**:\n- `page`: Page number (1-based)\n- `per_page`: Results per page (max 100)\n- `sort_by`: Sort field ('created_at', 'updated_at', 'priority', 'status')\n- `sort_order`: 'asc' or 'desc'\n- `ticket_id`: Ticket ID for single retrieval\n\n**Pitfalls**:\n- LIST uses `page`\u002F`per_page` pagination, NOT offset-based; check `next_page` in response\n- Maximum 100 results per page; iterate with page numbers until `next_page` is null\n- Deleted tickets are not returned by LIST; use GET_BY_ID which returns status 'deleted'\n- Ticket comments and audits are included in GET_BY_ID but not in LIST responses\n\n### 2. Create and Update Tickets\n\n**When to use**: User wants to create new tickets or modify existing ones\n\n**Tool sequence**:\n1. `ZENDESK_SEARCH_ZENDESK_USERS` - Find requester\u002Fassignee [Prerequisite]\n2. `ZENDESK_CREATE_ZENDESK_TICKET` - Create a new ticket [Required]\n3. `ZENDESK_UPDATE_ZENDESK_TICKET` - Update ticket fields [Optional]\n4. `ZENDESK_DELETE_ZENDESK_TICKET` - Delete a ticket [Optional]\n\n**Key parameters**:\n- `subject`: Ticket subject line\n- `description`: Ticket body (for creation; becomes first comment)\n- `priority`: 'urgent', 'high', 'normal', 'low'\n- `status`: 'new', 'open', 'pending', 'hold', 'solved', 'closed'\n- `type`: 'problem', 'incident', 'question', 'task'\n- `assignee_id`: Agent user ID to assign\n- `requester_id`: Requester user ID\n- `tags`: Array of tag strings\n- `ticket_id`: Ticket ID (for update\u002Fdelete)\n\n**Pitfalls**:\n- Tags on UPDATE REPLACE existing tags entirely; merge with current tags to preserve them\n- Use `safe_update` with `updated_stamp` to prevent concurrent modification conflicts\n- DELETE is permanent and irreversible; tickets cannot be recovered\n- `description` is only used on creation; use REPLY_ZENDESK_TICKET to add comments after creation\n- Closed tickets cannot be updated; create a follow-up ticket instead\n\n### 3. Reply to Tickets\n\n**When to use**: User wants to add comments or replies to tickets\n\n**Tool sequence**:\n1. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get current ticket state [Prerequisite]\n2. `ZENDESK_REPLY_ZENDESK_TICKET` - Add a reply\u002Fcomment [Required]\n\n**Key parameters**:\n- `ticket_id`: Ticket ID to reply to\n- `body`: Reply text content\n- `public`: Boolean; true for public reply, false for internal note\n- `author_id`: Author user ID (defaults to authenticated user)\n\n**Pitfalls**:\n- Set `public: false` for internal notes visible only to agents\n- Default is public reply which sends email to requester\n- HTML is supported in body text\n- Replying can also update ticket status simultaneously\n\n### 4. Manage Users\n\n**When to use**: User wants to find or create Zendesk users (agents, end-users)\n\n**Tool sequence**:\n1. `ZENDESK_SEARCH_ZENDESK_USERS` - Search for users [Required]\n2. `ZENDESK_CREATE_ZENDESK_USER` - Create a new user [Optional]\n3. `ZENDESK_GET_ABOUT_ME` - Get authenticated user info [Optional]\n\n**Key parameters**:\n- `query`: Search string (matches name, email, phone, etc.)\n- `name`: User's full name (required for creation)\n- `email`: User's email address\n- `role`: 'end-user', 'agent', or 'admin'\n- `verified`: Whether email is verified\n\n**Pitfalls**:\n- User search is fuzzy; may return partial matches\n- Creating a user with an existing email returns the existing user (upsert behavior)\n- Agent and admin roles may require specific plan features\n\n### 5. Manage Organizations\n\n**When to use**: User wants to list, create, or manage organizations\n\n**Tool sequence**:\n1. `ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS` - List all organizations [Required]\n2. `ZENDESK_GET_ZENDESK_ORGANIZATION` - Get specific organization [Optional]\n3. `ZENDESK_CREATE_ZENDESK_ORGANIZATION` - Create organization [Optional]\n4. `ZENDESK_UPDATE_ZENDESK_ORGANIZATION` - Update organization [Optional]\n5. `ZENDESK_COUNT_ZENDESK_ORGANIZATIONS` - Get total count [Optional]\n\n**Key parameters**:\n- `name`: Organization name (unique, required for creation)\n- `organization_id`: Organization ID for get\u002Fupdate\n- `details`: Organization details text\n- `notes`: Internal notes\n- `domain_names`: Array of associated domains\n- `tags`: Array of tag strings\n\n**Pitfalls**:\n- Organization names must be unique; duplicate names cause creation errors\n- Tags on UPDATE REPLACE existing tags (same behavior as tickets)\n- Domain names can be used for automatic user association\n\n## Common Patterns\n\n### Pagination\n\n**List endpoints**:\n- Use `page` (1-based) and `per_page` (max 100)\n- Check `next_page` URL in response; null means last page\n- `count` field gives total results\n\n### Ticket Lifecycle\n\n```\nnew -> open -> pending -> solved -> closed\n                  |          ^\n                  v          |\n                hold --------+\n```\n\n- `new`: Unassigned ticket\n- `open`: Assigned, being worked on\n- `pending`: Waiting for customer response\n- `hold`: Waiting for internal action\n- `solved`: Resolved, can be reopened\n- `closed`: Permanently closed, cannot be modified\n\n### User Search for Assignment\n\n```\n1. Call ZENDESK_SEARCH_ZENDESK_USERS with query (name or email)\n2. Extract user ID from results\n3. Use user ID as assignee_id in ticket creation\u002Fupdate\n```\n\n## Known Pitfalls\n\n**Tags Behavior**:\n- Tags on update REPLACE all existing tags\n- Always fetch current tags first and merge before updating\n- Tags are lowercase, no spaces (use underscores)\n\n**Safe Updates**:\n- Use `safe_update: true` with `updated_stamp` (ISO 8601) to prevent conflicts\n- Returns 409 if ticket was modified since the stamp\n\n**Deletion**:\n- Ticket deletion is permanent and irreversible\n- Consider setting status to 'closed' instead of deleting\n- Deleted tickets cannot be recovered via API\n\n**Rate Limits**:\n- Default: 400 requests per minute\n- Varies by plan tier\n- 429 responses include Retry-After header\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List tickets | ZENDESK_LIST_ZENDESK_TICKETS | page, per_page, sort_by |\n| Get ticket | ZENDESK_GET_ZENDESK_TICKET_BY_ID | ticket_id |\n| Create ticket | ZENDESK_CREATE_ZENDESK_TICKET | subject, description, priority |\n| Update ticket | ZENDESK_UPDATE_ZENDESK_TICKET | ticket_id, status, tags |\n| Reply to ticket | ZENDESK_REPLY_ZENDESK_TICKET | ticket_id, body, public |\n| Delete ticket | ZENDESK_DELETE_ZENDESK_TICKET | ticket_id |\n| Search users | ZENDESK_SEARCH_ZENDESK_USERS | query |\n| Create user | ZENDESK_CREATE_ZENDESK_USER | name, email |\n| My profile | ZENDESK_GET_ABOUT_ME | (none) |\n| List orgs | ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS | page, per_page |\n| Get org | ZENDESK_GET_ZENDESK_ORGANIZATION | organization_id |\n| Create org | ZENDESK_CREATE_ZENDESK_ORGANIZATION | name |\n| Update org | ZENDESK_UPDATE_ZENDESK_ORGANIZATION | organization_id, name |\n| Count orgs | ZENDESK_COUNT_ZENDESK_ORGANIZATIONS | (none) |\n\n---\n*Powered by [Composio](https:\u002F\u002Fcomposio.dev)*\n","# Zendesk Automation via Rube MCP\n\nAutomate Zendesk operations through Composio's Zendesk toolkit via Rube MCP.\n\n**Toolkit docs**: [composio.dev\u002Ftoolkits\u002Fzendesk](https:\u002F\u002Fcomposio.dev\u002Ftoolkits\u002Fzendesk)\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Zendesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zendesk`\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 `zendesk`\n3. If connection is not ACTIVE, follow the returned auth link to complete Zendesk auth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Search Tickets\n\n**When to use**: User wants to view, filter, or search support tickets\n\n**Tool sequence**:\n1. `ZENDESK_LIST_ZENDESK_TICKETS` - List all tickets with pagination [Required]\n2. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get specific ticket details [Optional]\n\n**Key parameters**:\n- `page`: Page number (1-based)\n- `per_page`: Results per page (max 100)\n- `sort_by`: Sort field ('created_at', 'updated_at', 'priority', 'status')\n- `sort_order`: 'asc' or 'desc'\n- `ticket_id`: Ticket ID for single retrieval\n\n**Pitfalls**:\n- LIST uses `page`\u002F`per_page` pagination, NOT offset-based; check `next_page` in response\n- Maximum 100 results per page; iterate with page numbers until `next_page` is null\n- Deleted tickets are not returned by LIST; use GET_BY_ID which returns status 'deleted'\n- Ticket comments and audits are included in GET_BY_ID but not in LIST responses\n\n### 2. Create and Update Tickets\n\n**When to use**: User wants to create new tickets or modify existing ones\n\n**Tool sequence**:\n1. `ZENDESK_SEARCH_ZENDESK_USERS` - Find requester\u002Fassignee [Prerequisite]\n2. `ZENDESK_CREATE_ZENDESK_TICKET` - Create a new ticket [Required]\n3. `ZENDESK_UPDATE_ZENDESK_TICKET` - Update ticket fields [Optional]\n4. `ZENDESK_DELETE_ZENDESK_TICKET` - Delete a ticket [Optional]\n\n**Key parameters**:\n- `subject`: Ticket subject line\n- `description`: Ticket body (for creation; becomes first comment)\n- `priority`: 'urgent', 'high', 'normal', 'low'\n- `status`: 'new', 'open', 'pending', 'hold', 'solved', 'closed'\n- `type`: 'problem', 'incident', 'question', 'task'\n- `assignee_id`: Agent user ID to assign\n- `requester_id`: Requester user ID\n- `tags`: Array of tag strings\n- `ticket_id`: Ticket ID (for update\u002Fdelete)\n\n**Pitfalls**:\n- Tags on UPDATE REPLACE existing tags entirely; merge with current tags to preserve them\n- Use `safe_update` with `updated_stamp` to prevent concurrent modification conflicts\n- DELETE is permanent and irreversible; tickets cannot be recovered\n- `description` is only used on creation; use REPLY_ZENDESK_TICKET to add comments after creation\n- Closed tickets cannot be updated; create a follow-up ticket instead\n\n### 3. Reply to Tickets\n\n**When to use**: User wants to add comments or replies to tickets\n\n**Tool sequence**:\n1. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get current ticket state [Prerequisite]\n2. `ZENDESK_REPLY_ZENDESK_TICKET` - Add a reply\u002Fcomment [Required]\n\n**Key parameters**:\n- `ticket_id`: Ticket ID to reply to\n- `body`: Reply text content\n- `public`: Boolean; true for public reply, false for internal note\n- `author_id`: Author user ID (defaults to authenticated user)\n\n**Pitfalls**:\n- Set `public: false` for internal notes visible only to agents\n- Default is public reply which sends email to requester\n- HTML is supported in body text\n- Replying can also update ticket status simultaneously\n\n### 4. Manage Users\n\n**When to use**: User wants to find or create Zendesk users (agents, end-users)\n\n**Tool sequence**:\n1. `ZENDESK_SEARCH_ZENDESK_USERS` - Search for users [Required]\n2. `ZENDESK_CREATE_ZENDESK_USER` - Create a new user [Optional]\n3. `ZENDESK_GET_ABOUT_ME` - Get authenticated user info [Optional]\n\n**Key parameters**:\n- `query`: Search string (matches name, email, phone, etc.)\n- `name`: User's full name (required for creation)\n- `email`: User's email address\n- `role`: 'end-user', 'agent', or 'admin'\n- `verified`: Whether email is verified\n\n**Pitfalls**:\n- User search is fuzzy; may return partial matches\n- Creating a user with an existing email returns the existing user (upsert behavior)\n- Agent and admin roles may require specific plan features\n\n### 5. Manage Organizations\n\n**When to use**: User wants to list, create, or manage organizations\n\n**Tool sequence**:\n1. `ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS` - List all organizations [Required]\n2. `ZENDESK_GET_ZENDESK_ORGANIZATION` - Get specific organization [Optional]\n3. `ZENDESK_CREATE_ZENDESK_ORGANIZATION` - Create organization [Optional]\n4. `ZENDESK_UPDATE_ZENDESK_ORGANIZATION` - Update organization [Optional]\n5. `ZENDESK_COUNT_ZENDESK_ORGANIZATIONS` - Get total count [Optional]\n\n**Key parameters**:\n- `name`: Organization name (unique, required for creation)\n- `organization_id`: Organization ID for get\u002Fupdate\n- `details`: Organization details text\n- `notes`: Internal notes\n- `domain_names`: Array of associated domains\n- `tags`: Array of tag strings\n\n**Pitfalls**:\n- Organization names must be unique; duplicate names cause creation errors\n- Tags on UPDATE REPLACE existing tags (same behavior as tickets)\n- Domain names can be used for automatic user association\n\n## Common Patterns\n\n### Pagination\n\n**List endpoints**:\n- Use `page` (1-based) and `per_page` (max 100)\n- Check `next_page` URL in response; null means last page\n- `count` field gives total results\n\n### Ticket Lifecycle\n\n```\nnew -> open -> pending -> solved -> closed\n                  |          ^\n                  v          |\n                hold --------+\n```\n\n- `new`: Unassigned ticket\n- `open`: Assigned, being worked on\n- `pending`: Waiting for customer response\n- `hold`: Waiting for internal action\n- `solved`: Resolved, can be reopened\n- `closed`: Permanently closed, cannot be modified\n\n### User Search for Assignment\n\n```\n1. Call ZENDESK_SEARCH_ZENDESK_USERS with query (name or email)\n2. Extract user ID from results\n3. Use user ID as assignee_id in ticket creation\u002Fupdate\n```\n\n## Known Pitfalls\n\n**Tags Behavior**:\n- Tags on update REPLACE all existing tags\n- Always fetch current tags first and merge before updating\n- Tags are lowercase, no spaces (use underscores)\n\n**Safe Updates**:\n- Use `safe_update: true` with `updated_stamp` (ISO 8601) to prevent conflicts\n- Returns 409 if ticket was modified since the stamp\n\n**Deletion**:\n- Ticket deletion is permanent and irreversible\n- Consider setting status to 'closed' instead of deleting\n- Deleted tickets cannot be recovered via API\n\n**Rate Limits**:\n- Default: 400 requests per minute\n- Varies by plan tier\n- 429 responses include Retry-After header\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List tickets | ZENDESK_LIST_ZENDESK_TICKETS | page, per_page, sort_by |\n| Get ticket | ZENDESK_GET_ZENDESK_TICKET_BY_ID | ticket_id |\n| Create ticket | ZENDESK_CREATE_ZENDESK_TICKET | subject, description, priority |\n| Update ticket | ZENDESK_UPDATE_ZENDESK_TICKET | ticket_id, status, tags |\n| Reply to ticket | ZENDESK_REPLY_ZENDESK_TICKET | ticket_id, body, public |\n| Delete ticket | ZENDESK_DELETE_ZENDESK_TICKET | ticket_id |\n| Search users | ZENDESK_SEARCH_ZENDESK_USERS | query |\n| Create user | ZENDESK_CREATE_ZENDESK_USER | name, email |\n| My profile | ZENDESK_GET_ABOUT_ME | (none) |\n| List orgs | ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS | page, per_page |\n| Get org | ZENDESK_GET_ZENDESK_ORGANIZATION | organization_id |\n| Create org | ZENDESK_CREATE_ZENDESK_ORGANIZATION | name |\n| Update org | ZENDESK_UPDATE_ZENDESK_ORGANIZATION | organization_id, name |\n| Count orgs | ZENDESK_COUNT_ZENDESK_ORGANIZATIONS | (none) |\n\n---\n*Powered by [Composio](https:\u002F\u002Fcomposio.dev)*\n",{"name":5,"category":24,"requires":25,"description":7},"customer-support",{"mcp":26},[27],"rube","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-all-skills\u002Fskills\u002Fzendesk-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 zendesk-automation",{"tool":43,"command":44},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill zendesk-automation",{"tool":46,"command":47},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill zendesk-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-all-skills\u002Fskills\u002Fzendesk-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",[],[]]