[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CHPB1XK62FQYN1WP4WDQQB":3,"skill-same:01M7CHPB1XK62FQYN1WP4WDQQB":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CHPB1XK62FQYN1WP4WDQQB","cal-com-automation",null,"Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. 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-技能包-antigravity-awesome-skills\u002Fskills\u002Fcal-com-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cal-com-automation\ndescription: \"Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Cal.com Automation via Rube MCP\n\nAutomate Cal.com scheduling operations through Composio's Cal toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Cal.com connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cal`\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 `cal`\n3. If connection is not ACTIVE, follow the returned auth link to complete Cal.com authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Bookings\n\n**When to use**: User wants to list, create, or review bookings\n\n**Tool sequence**:\n1. `CAL_FETCH_ALL_BOOKINGS` - List all bookings with filters [Required]\n2. `CAL_POST_NEW_BOOKING_REQUEST` - Create a new booking [Optional]\n\n**Key parameters for listing**:\n- `status`: Filter by booking status ('upcoming', 'recurring', 'past', 'cancelled', 'unconfirmed')\n- `afterStart`: Filter bookings after this date (ISO 8601)\n- `beforeEnd`: Filter bookings before this date (ISO 8601)\n\n**Key parameters for creation**:\n- `eventTypeId`: Event type ID for the booking\n- `start`: Booking start time (ISO 8601)\n- `end`: Booking end time (ISO 8601)\n- `name`: Attendee name\n- `email`: Attendee email\n- `timeZone`: Attendee timezone (IANA format)\n- `language`: Attendee language code\n- `metadata`: Additional metadata object\n\n**Pitfalls**:\n- Date filters use ISO 8601 format with timezone (e.g., '2024-01-15T09:00:00Z')\n- `eventTypeId` must reference a valid, active event type\n- Booking creation requires matching an available slot; check availability first\n- Time zone must be a valid IANA timezone string (e.g., 'America\u002FNew_York')\n- Status filter values are specific strings; invalid values return empty results\n\n### 2. Check Availability\n\n**When to use**: User wants to find free\u002Fbusy times or available booking slots\n\n**Tool sequence**:\n1. `CAL_RETRIEVE_CALENDAR_BUSY_TIMES` - Get busy time blocks [Required]\n2. `CAL_GET_AVAILABLE_SLOTS_INFO` - Get specific available slots [Required]\n\n**Key parameters**:\n- `dateFrom`: Start date for availability check (YYYY-MM-DD)\n- `dateTo`: End date for availability check (YYYY-MM-DD)\n- `eventTypeId`: Event type to check slots for\n- `timeZone`: Timezone for the availability response\n- `loggedInUsersTz`: Timezone of the requesting user\n\n**Pitfalls**:\n- Busy times show when the user is NOT available\n- Available slots are specific to an event type's duration and configuration\n- Date range should be reasonable (not months in advance) to get accurate results\n- Timezone affects how slots are displayed; always specify explicitly\n- Availability reflects calendar integrations (Google Calendar, Outlook, etc.)\n\n### 3. Configure Webhooks\n\n**When to use**: User wants to set up or manage webhook notifications for booking events\n\n**Tool sequence**:\n1. `CAL_RETRIEVE_WEBHOOKS_LIST` - List existing webhooks [Required]\n2. `CAL_GET_WEBHOOK_BY_ID` - Get specific webhook details [Optional]\n3. `CAL_UPDATE_WEBHOOK_BY_ID` - Update webhook configuration [Optional]\n4. `CAL_DELETE_WEBHOOK_BY_ID` - Remove a webhook [Optional]\n\n**Key parameters**:\n- `id`: Webhook ID for GET\u002FUPDATE\u002FDELETE operations\n- `subscriberUrl`: Webhook endpoint URL\n- `eventTriggers`: Array of event types to trigger on\n- `active`: Whether the webhook is active\n- `secret`: Webhook signing secret\n\n**Pitfalls**:\n- Webhook URLs must be publicly accessible HTTPS endpoints\n- Event triggers include: 'BOOKING_CREATED', 'BOOKING_RESCHEDULED', 'BOOKING_CANCELLED', etc.\n- Inactive webhooks do not fire; toggle `active` to enable\u002Fdisable\n- Webhook secrets are used for payload signature verification\n\n### 4. Manage Teams\n\n**When to use**: User wants to create, view, or manage teams and team event types\n\n**Tool sequence**:\n1. `CAL_GET_TEAMS_LIST` - List all teams [Required]\n2. `CAL_GET_TEAM_INFORMATION_BY_TEAM_ID` - Get specific team details [Optional]\n3. `CAL_CREATE_TEAM_IN_ORGANIZATION` - Create a new team [Optional]\n4. `CAL_RETRIEVE_TEAM_EVENT_TYPES` - List event types for a team [Optional]\n\n**Key parameters**:\n- `teamId`: Team identifier\n- `name`: Team name (for creation)\n- `slug`: URL-friendly team identifier\n\n**Pitfalls**:\n- Team creation may require organization-level permissions\n- Team event types are separate from personal event types\n- Team slugs must be URL-safe and unique within the organization\n\n### 5. Organization Management\n\n**When to use**: User wants to view organization details\n\n**Tool sequence**:\n1. `CAL_GET_ORGANIZATION_ID` - Get the organization ID [Required]\n\n**Key parameters**: (none required)\n\n**Pitfalls**:\n- Organization ID is needed for team creation and org-level operations\n- Not all Cal.com accounts have organizations; personal plans may return errors\n\n## Common Patterns\n\n### Booking Creation Flow\n\n```\n1. Call CAL_GET_AVAILABLE_SLOTS_INFO to find open slots\n2. Present available times to the user\n3. Call CAL_POST_NEW_BOOKING_REQUEST with selected slot\n4. Confirm booking creation response\n```\n\n### ID Resolution\n\n**Team name -> Team ID**:\n```\n1. Call CAL_GET_TEAMS_LIST\n2. Find team by name in response\n3. Extract id field\n```\n\n### Webhook Setup\n\n```\n1. Call CAL_RETRIEVE_WEBHOOKS_LIST to check existing hooks\n2. Create or update webhook with desired triggers\n3. Verify webhook fires on test booking\n```\n\n## Known Pitfalls\n\n**Date\u002FTime Formats**:\n- Booking times: ISO 8601 with timezone (e.g., '2024-01-15T09:00:00Z')\n- Availability dates: YYYY-MM-DD format\n- Always specify timezone explicitly to avoid confusion\n\n**Event Types**:\n- Event type IDs are numeric integers\n- Event types define duration, location, and booking rules\n- Disabled event types cannot accept new bookings\n\n**Permissions**:\n- Team operations require team membership or admin access\n- Organization operations require org-level permissions\n- Webhook management requires appropriate access level\n\n**Rate Limits**:\n- Cal.com API has rate limits per API key\n- Implement backoff on 429 responses\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List bookings | CAL_FETCH_ALL_BOOKINGS | status, afterStart, beforeEnd |\n| Create booking | CAL_POST_NEW_BOOKING_REQUEST | eventTypeId, start, end, name, email |\n| Get busy times | CAL_RETRIEVE_CALENDAR_BUSY_TIMES | dateFrom, dateTo |\n| Get available slots | CAL_GET_AVAILABLE_SLOTS_INFO | eventTypeId, dateFrom, dateTo |\n| List webhooks | CAL_RETRIEVE_WEBHOOKS_LIST | (none) |\n| Get webhook | CAL_GET_WEBHOOK_BY_ID | id |\n| Update webhook | CAL_UPDATE_WEBHOOK_BY_ID | id, subscriberUrl, eventTriggers |\n| Delete webhook | CAL_DELETE_WEBHOOK_BY_ID | id |\n| List teams | CAL_GET_TEAMS_LIST | (none) |\n| Get team | CAL_GET_TEAM_INFORMATION_BY_TEAM_ID | teamId |\n| Create team | CAL_CREATE_TEAM_IN_ORGANIZATION | name, slug |\n| Team event types | CAL_RETRIEVE_TEAM_EVENT_TYPES | teamId |\n| Get org ID | CAL_GET_ORGANIZATION_ID | (none) |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\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","# Cal.com Automation via Rube MCP\n\nAutomate Cal.com scheduling operations through Composio's Cal toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Cal.com connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cal`\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 `cal`\n3. If connection is not ACTIVE, follow the returned auth link to complete Cal.com authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Bookings\n\n**When to use**: User wants to list, create, or review bookings\n\n**Tool sequence**:\n1. `CAL_FETCH_ALL_BOOKINGS` - List all bookings with filters [Required]\n2. `CAL_POST_NEW_BOOKING_REQUEST` - Create a new booking [Optional]\n\n**Key parameters for listing**:\n- `status`: Filter by booking status ('upcoming', 'recurring', 'past', 'cancelled', 'unconfirmed')\n- `afterStart`: Filter bookings after this date (ISO 8601)\n- `beforeEnd`: Filter bookings before this date (ISO 8601)\n\n**Key parameters for creation**:\n- `eventTypeId`: Event type ID for the booking\n- `start`: Booking start time (ISO 8601)\n- `end`: Booking end time (ISO 8601)\n- `name`: Attendee name\n- `email`: Attendee email\n- `timeZone`: Attendee timezone (IANA format)\n- `language`: Attendee language code\n- `metadata`: Additional metadata object\n\n**Pitfalls**:\n- Date filters use ISO 8601 format with timezone (e.g., '2024-01-15T09:00:00Z')\n- `eventTypeId` must reference a valid, active event type\n- Booking creation requires matching an available slot; check availability first\n- Time zone must be a valid IANA timezone string (e.g., 'America\u002FNew_York')\n- Status filter values are specific strings; invalid values return empty results\n\n### 2. Check Availability\n\n**When to use**: User wants to find free\u002Fbusy times or available booking slots\n\n**Tool sequence**:\n1. `CAL_RETRIEVE_CALENDAR_BUSY_TIMES` - Get busy time blocks [Required]\n2. `CAL_GET_AVAILABLE_SLOTS_INFO` - Get specific available slots [Required]\n\n**Key parameters**:\n- `dateFrom`: Start date for availability check (YYYY-MM-DD)\n- `dateTo`: End date for availability check (YYYY-MM-DD)\n- `eventTypeId`: Event type to check slots for\n- `timeZone`: Timezone for the availability response\n- `loggedInUsersTz`: Timezone of the requesting user\n\n**Pitfalls**:\n- Busy times show when the user is NOT available\n- Available slots are specific to an event type's duration and configuration\n- Date range should be reasonable (not months in advance) to get accurate results\n- Timezone affects how slots are displayed; always specify explicitly\n- Availability reflects calendar integrations (Google Calendar, Outlook, etc.)\n\n### 3. Configure Webhooks\n\n**When to use**: User wants to set up or manage webhook notifications for booking events\n\n**Tool sequence**:\n1. `CAL_RETRIEVE_WEBHOOKS_LIST` - List existing webhooks [Required]\n2. `CAL_GET_WEBHOOK_BY_ID` - Get specific webhook details [Optional]\n3. `CAL_UPDATE_WEBHOOK_BY_ID` - Update webhook configuration [Optional]\n4. `CAL_DELETE_WEBHOOK_BY_ID` - Remove a webhook [Optional]\n\n**Key parameters**:\n- `id`: Webhook ID for GET\u002FUPDATE\u002FDELETE operations\n- `subscriberUrl`: Webhook endpoint URL\n- `eventTriggers`: Array of event types to trigger on\n- `active`: Whether the webhook is active\n- `secret`: Webhook signing secret\n\n**Pitfalls**:\n- Webhook URLs must be publicly accessible HTTPS endpoints\n- Event triggers include: 'BOOKING_CREATED', 'BOOKING_RESCHEDULED', 'BOOKING_CANCELLED', etc.\n- Inactive webhooks do not fire; toggle `active` to enable\u002Fdisable\n- Webhook secrets are used for payload signature verification\n\n### 4. Manage Teams\n\n**When to use**: User wants to create, view, or manage teams and team event types\n\n**Tool sequence**:\n1. `CAL_GET_TEAMS_LIST` - List all teams [Required]\n2. `CAL_GET_TEAM_INFORMATION_BY_TEAM_ID` - Get specific team details [Optional]\n3. `CAL_CREATE_TEAM_IN_ORGANIZATION` - Create a new team [Optional]\n4. `CAL_RETRIEVE_TEAM_EVENT_TYPES` - List event types for a team [Optional]\n\n**Key parameters**:\n- `teamId`: Team identifier\n- `name`: Team name (for creation)\n- `slug`: URL-friendly team identifier\n\n**Pitfalls**:\n- Team creation may require organization-level permissions\n- Team event types are separate from personal event types\n- Team slugs must be URL-safe and unique within the organization\n\n### 5. Organization Management\n\n**When to use**: User wants to view organization details\n\n**Tool sequence**:\n1. `CAL_GET_ORGANIZATION_ID` - Get the organization ID [Required]\n\n**Key parameters**: (none required)\n\n**Pitfalls**:\n- Organization ID is needed for team creation and org-level operations\n- Not all Cal.com accounts have organizations; personal plans may return errors\n\n## Common Patterns\n\n### Booking Creation Flow\n\n```\n1. Call CAL_GET_AVAILABLE_SLOTS_INFO to find open slots\n2. Present available times to the user\n3. Call CAL_POST_NEW_BOOKING_REQUEST with selected slot\n4. Confirm booking creation response\n```\n\n### ID Resolution\n\n**Team name -> Team ID**:\n```\n1. Call CAL_GET_TEAMS_LIST\n2. Find team by name in response\n3. Extract id field\n```\n\n### Webhook Setup\n\n```\n1. Call CAL_RETRIEVE_WEBHOOKS_LIST to check existing hooks\n2. Create or update webhook with desired triggers\n3. Verify webhook fires on test booking\n```\n\n## Known Pitfalls\n\n**Date\u002FTime Formats**:\n- Booking times: ISO 8601 with timezone (e.g., '2024-01-15T09:00:00Z')\n- Availability dates: YYYY-MM-DD format\n- Always specify timezone explicitly to avoid confusion\n\n**Event Types**:\n- Event type IDs are numeric integers\n- Event types define duration, location, and booking rules\n- Disabled event types cannot accept new bookings\n\n**Permissions**:\n- Team operations require team membership or admin access\n- Organization operations require org-level permissions\n- Webhook management requires appropriate access level\n\n**Rate Limits**:\n- Cal.com API has rate limits per API key\n- Implement backoff on 429 responses\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List bookings | CAL_FETCH_ALL_BOOKINGS | status, afterStart, beforeEnd |\n| Create booking | CAL_POST_NEW_BOOKING_REQUEST | eventTypeId, start, end, name, email |\n| Get busy times | CAL_RETRIEVE_CALENDAR_BUSY_TIMES | dateFrom, dateTo |\n| Get available slots | CAL_GET_AVAILABLE_SLOTS_INFO | eventTypeId, dateFrom, dateTo |\n| List webhooks | CAL_RETRIEVE_WEBHOOKS_LIST | (none) |\n| Get webhook | CAL_GET_WEBHOOK_BY_ID | id |\n| Update webhook | CAL_UPDATE_WEBHOOK_BY_ID | id, subscriberUrl, eventTriggers |\n| Delete webhook | CAL_DELETE_WEBHOOK_BY_ID | id |\n| List teams | CAL_GET_TEAMS_LIST | (none) |\n| Get team | CAL_GET_TEAM_INFORMATION_BY_TEAM_ID | teamId |\n| Create team | CAL_CREATE_TEAM_IN_ORGANIZATION | name, slug |\n| Team event types | CAL_RETRIEVE_TEAM_EVENT_TYPES | teamId |\n| Get org ID | CAL_GET_ORGANIZATION_ID | (none) |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\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,"date_added":26,"description":7},"critical","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fcal-com-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":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill cal-com-automation",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill cal-com-automation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill cal-com-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fcal-com-automation\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"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":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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",[],[]]