[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CM6RCA6JF2HEVBVJB5WKX8":3,"skill-same:01M7CM6RCA6JF2HEVBVJB5WKX8":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},"01M7CM6RCA6JF2HEVBVJB5WKX8","mixpanel-automation",null,"Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. 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\u002Fmixpanel-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mixpanel-automation\ndescription: \"Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Mixpanel Automation via Rube MCP\n\nAutomate Mixpanel product analytics through Composio's Mixpanel toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Mixpanel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`\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 `mixpanel`\n3. If connection is not ACTIVE, follow the returned auth link to complete Mixpanel authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Aggregate Event Data\n\n**When to use**: User wants to count events, get totals, or track event trends over time\n\n**Tool sequence**:\n1. `MIXPANEL_GET_ALL_PROJECTS` - List projects to get project ID [Prerequisite]\n2. `MIXPANEL_AGGREGATE_EVENT_COUNTS` - Get event counts and aggregations [Required]\n\n**Key parameters**:\n- `event`: Event name or array of event names to aggregate\n- `from_date` \u002F `to_date`: Date range in 'YYYY-MM-DD' format\n- `unit`: Time granularity ('minute', 'hour', 'day', 'week', 'month')\n- `type`: Aggregation type ('general', 'unique', 'average')\n- `where`: Filter expression for event properties\n\n**Pitfalls**:\n- Date format must be 'YYYY-MM-DD'; other formats cause errors\n- Event names are case-sensitive; use exact names from your Mixpanel project\n- `where` filter uses Mixpanel expression syntax (e.g., `properties[\"country\"] == \"US\"`)\n- Maximum date range may be limited depending on your Mixpanel plan\n\n### 2. Run Segmentation Queries\n\n**When to use**: User wants to break down events by properties for detailed analysis\n\n**Tool sequence**:\n1. `MIXPANEL_QUERY_SEGMENTATION` - Run segmentation analysis [Required]\n\n**Key parameters**:\n- `event`: Event name to segment\n- `from_date` \u002F `to_date`: Date range in 'YYYY-MM-DD' format\n- `on`: Property to segment by (e.g., `properties[\"country\"]`)\n- `unit`: Time granularity\n- `type`: Count type ('general', 'unique', 'average')\n- `where`: Filter expression\n- `limit`: Maximum number of segments to return\n\n**Pitfalls**:\n- The `on` parameter uses Mixpanel property expression syntax\n- Property references must use `properties[\"prop_name\"]` format\n- Segmentation on high-cardinality properties returns capped results; use `limit`\n- Results are grouped by the segmentation property and time unit\n\n### 3. Analyze Funnels\n\n**When to use**: User wants to track conversion funnels and identify drop-off points\n\n**Tool sequence**:\n1. `MIXPANEL_LIST_FUNNELS` - List saved funnels to find funnel ID [Prerequisite]\n2. `MIXPANEL_QUERY_FUNNEL` - Execute funnel analysis [Required]\n\n**Key parameters**:\n- `funnel_id`: ID of the saved funnel to query\n- `from_date` \u002F `to_date`: Date range\n- `unit`: Time granularity\n- `where`: Filter expression\n- `on`: Property to segment funnel by\n- `length`: Conversion window in days\n\n**Pitfalls**:\n- `funnel_id` is required; resolve via LIST_FUNNELS first\n- Funnels must be created in Mixpanel UI first; API only queries existing funnels\n- Conversion window (`length`) defaults vary; set explicitly for accuracy\n- Large date ranges with segmentation can produce very large responses\n\n### 4. Manage User Profiles\n\n**When to use**: User wants to query or update user profiles in Mixpanel\n\n**Tool sequence**:\n1. `MIXPANEL_QUERY_PROFILES` - Search and filter user profiles [Required]\n2. `MIXPANEL_PROFILE_BATCH_UPDATE` - Update multiple user profiles [Optional]\n\n**Key parameters**:\n- `where`: Filter expression for profile properties (e.g., `properties[\"plan\"] == \"premium\"`)\n- `output_properties`: Array of property names to include in results\n- `page`: Page number for pagination\n- `session_id`: Session ID for consistent pagination (from first response)\n- For batch update: array of profile updates with `$distinct_id` and property operations\n\n**Pitfalls**:\n- Profile queries return paginated results; use `session_id` from first response for consistent paging\n- `where` uses Mixpanel expression syntax for profile properties\n- BATCH_UPDATE applies operations (`$set`, `$unset`, `$add`, `$append`) to profiles\n- Batch update has a maximum number of profiles per request; chunk larger updates\n- Profile property names are case-sensitive\n\n### 5. Manage Cohorts\n\n**When to use**: User wants to list or analyze user cohorts\n\n**Tool sequence**:\n1. `MIXPANEL_COHORTS_LIST` - List all saved cohorts [Required]\n\n**Key parameters**:\n- No required parameters; returns all accessible cohorts\n- Response includes cohort `id`, `name`, `description`, `count`\n\n**Pitfalls**:\n- Cohorts are created and managed in Mixpanel UI; API provides read access\n- Cohort IDs are numeric; use exact ID from list results\n- Cohort counts may be approximate for very large cohorts\n- Cohorts can be used as filters in other queries via `where` expressions\n\n### 6. Run JQL and Insight Queries\n\n**When to use**: User wants to run custom JQL queries or insight analyses\n\n**Tool sequence**:\n1. `MIXPANEL_JQL_QUERY` - Execute a custom JQL (JavaScript Query Language) query [Optional]\n2. `MIXPANEL_QUERY_INSIGHT` - Run a saved insight query [Optional]\n\n**Key parameters**:\n- For JQL: `script` containing the JQL JavaScript code\n- For Insight: `bookmark_id` of the saved insight\n- `project_id`: Project context for the query\n\n**Pitfalls**:\n- JQL uses JavaScript-like syntax specific to Mixpanel\n- JQL queries have execution time limits; optimize for efficiency\n- Insight `bookmark_id` must reference an existing saved insight\n- JQL is a legacy feature; check Mixpanel documentation for current availability\n\n## Common Patterns\n\n### ID Resolution\n\n**Project name -> Project ID**:\n```\n1. Call MIXPANEL_GET_ALL_PROJECTS\n2. Find project by name in results\n3. Extract project id\n```\n\n**Funnel name -> Funnel ID**:\n```\n1. Call MIXPANEL_LIST_FUNNELS\n2. Find funnel by name\n3. Extract funnel_id\n```\n\n### Mixpanel Expression Syntax\n\nUsed in `where` and `on` parameters:\n- Property reference: `properties[\"property_name\"]`\n- Equality: `properties[\"country\"] == \"US\"`\n- Comparison: `properties[\"age\"] > 25`\n- Boolean: `properties[\"is_premium\"] == true`\n- Contains: `\"search_term\" in properties[\"name\"]`\n- AND\u002FOR: `properties[\"country\"] == \"US\" and properties[\"plan\"] == \"pro\"`\n\n### Pagination\n\n- Event queries: Follow date-based pagination by adjusting date ranges\n- Profile queries: Use `page` number and `session_id` for consistent results\n- Funnel\u002Fcohort lists: Typically return complete results without pagination\n\n## Known Pitfalls\n\n**Date Formats**:\n- Always use 'YYYY-MM-DD' format\n- Date ranges are inclusive on both ends\n- Data freshness depends on Mixpanel ingestion delay (typically minutes)\n\n**Expression Syntax**:\n- Property references always use `properties[\"name\"]` format\n- String values must be quoted: `properties[\"status\"] == \"active\"`\n- Numeric values are unquoted: `properties[\"count\"] > 10`\n- Boolean values: `true` \u002F `false` (lowercase)\n\n**Rate Limits**:\n- Mixpanel API has rate limits per project\n- Large segmentation queries may time out; reduce date range or segments\n- Use batch operations where available to minimize API calls\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Event data is typically grouped by date and segment\n- Numeric values may be returned as strings; parse explicitly\n- Empty date ranges return empty objects, not empty arrays\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | MIXPANEL_GET_ALL_PROJECTS | (none) |\n| Aggregate events | MIXPANEL_AGGREGATE_EVENT_COUNTS | event, from_date, to_date, unit |\n| Segmentation | MIXPANEL_QUERY_SEGMENTATION | event, on, from_date, to_date |\n| List funnels | MIXPANEL_LIST_FUNNELS | (none) |\n| Query funnel | MIXPANEL_QUERY_FUNNEL | funnel_id, from_date, to_date |\n| Query profiles | MIXPANEL_QUERY_PROFILES | where, output_properties, page |\n| Batch update profiles | MIXPANEL_PROFILE_BATCH_UPDATE | (profile update objects) |\n| List cohorts | MIXPANEL_COHORTS_LIST | (none) |\n| JQL query | MIXPANEL_JQL_QUERY | script |\n| Query insight | MIXPANEL_QUERY_INSIGHT | bookmark_id |\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","# Mixpanel Automation via Rube MCP\n\nAutomate Mixpanel product analytics through Composio's Mixpanel toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Mixpanel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`\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 `mixpanel`\n3. If connection is not ACTIVE, follow the returned auth link to complete Mixpanel authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Aggregate Event Data\n\n**When to use**: User wants to count events, get totals, or track event trends over time\n\n**Tool sequence**:\n1. `MIXPANEL_GET_ALL_PROJECTS` - List projects to get project ID [Prerequisite]\n2. `MIXPANEL_AGGREGATE_EVENT_COUNTS` - Get event counts and aggregations [Required]\n\n**Key parameters**:\n- `event`: Event name or array of event names to aggregate\n- `from_date` \u002F `to_date`: Date range in 'YYYY-MM-DD' format\n- `unit`: Time granularity ('minute', 'hour', 'day', 'week', 'month')\n- `type`: Aggregation type ('general', 'unique', 'average')\n- `where`: Filter expression for event properties\n\n**Pitfalls**:\n- Date format must be 'YYYY-MM-DD'; other formats cause errors\n- Event names are case-sensitive; use exact names from your Mixpanel project\n- `where` filter uses Mixpanel expression syntax (e.g., `properties[\"country\"] == \"US\"`)\n- Maximum date range may be limited depending on your Mixpanel plan\n\n### 2. Run Segmentation Queries\n\n**When to use**: User wants to break down events by properties for detailed analysis\n\n**Tool sequence**:\n1. `MIXPANEL_QUERY_SEGMENTATION` - Run segmentation analysis [Required]\n\n**Key parameters**:\n- `event`: Event name to segment\n- `from_date` \u002F `to_date`: Date range in 'YYYY-MM-DD' format\n- `on`: Property to segment by (e.g., `properties[\"country\"]`)\n- `unit`: Time granularity\n- `type`: Count type ('general', 'unique', 'average')\n- `where`: Filter expression\n- `limit`: Maximum number of segments to return\n\n**Pitfalls**:\n- The `on` parameter uses Mixpanel property expression syntax\n- Property references must use `properties[\"prop_name\"]` format\n- Segmentation on high-cardinality properties returns capped results; use `limit`\n- Results are grouped by the segmentation property and time unit\n\n### 3. Analyze Funnels\n\n**When to use**: User wants to track conversion funnels and identify drop-off points\n\n**Tool sequence**:\n1. `MIXPANEL_LIST_FUNNELS` - List saved funnels to find funnel ID [Prerequisite]\n2. `MIXPANEL_QUERY_FUNNEL` - Execute funnel analysis [Required]\n\n**Key parameters**:\n- `funnel_id`: ID of the saved funnel to query\n- `from_date` \u002F `to_date`: Date range\n- `unit`: Time granularity\n- `where`: Filter expression\n- `on`: Property to segment funnel by\n- `length`: Conversion window in days\n\n**Pitfalls**:\n- `funnel_id` is required; resolve via LIST_FUNNELS first\n- Funnels must be created in Mixpanel UI first; API only queries existing funnels\n- Conversion window (`length`) defaults vary; set explicitly for accuracy\n- Large date ranges with segmentation can produce very large responses\n\n### 4. Manage User Profiles\n\n**When to use**: User wants to query or update user profiles in Mixpanel\n\n**Tool sequence**:\n1. `MIXPANEL_QUERY_PROFILES` - Search and filter user profiles [Required]\n2. `MIXPANEL_PROFILE_BATCH_UPDATE` - Update multiple user profiles [Optional]\n\n**Key parameters**:\n- `where`: Filter expression for profile properties (e.g., `properties[\"plan\"] == \"premium\"`)\n- `output_properties`: Array of property names to include in results\n- `page`: Page number for pagination\n- `session_id`: Session ID for consistent pagination (from first response)\n- For batch update: array of profile updates with `$distinct_id` and property operations\n\n**Pitfalls**:\n- Profile queries return paginated results; use `session_id` from first response for consistent paging\n- `where` uses Mixpanel expression syntax for profile properties\n- BATCH_UPDATE applies operations (`$set`, `$unset`, `$add`, `$append`) to profiles\n- Batch update has a maximum number of profiles per request; chunk larger updates\n- Profile property names are case-sensitive\n\n### 5. Manage Cohorts\n\n**When to use**: User wants to list or analyze user cohorts\n\n**Tool sequence**:\n1. `MIXPANEL_COHORTS_LIST` - List all saved cohorts [Required]\n\n**Key parameters**:\n- No required parameters; returns all accessible cohorts\n- Response includes cohort `id`, `name`, `description`, `count`\n\n**Pitfalls**:\n- Cohorts are created and managed in Mixpanel UI; API provides read access\n- Cohort IDs are numeric; use exact ID from list results\n- Cohort counts may be approximate for very large cohorts\n- Cohorts can be used as filters in other queries via `where` expressions\n\n### 6. Run JQL and Insight Queries\n\n**When to use**: User wants to run custom JQL queries or insight analyses\n\n**Tool sequence**:\n1. `MIXPANEL_JQL_QUERY` - Execute a custom JQL (JavaScript Query Language) query [Optional]\n2. `MIXPANEL_QUERY_INSIGHT` - Run a saved insight query [Optional]\n\n**Key parameters**:\n- For JQL: `script` containing the JQL JavaScript code\n- For Insight: `bookmark_id` of the saved insight\n- `project_id`: Project context for the query\n\n**Pitfalls**:\n- JQL uses JavaScript-like syntax specific to Mixpanel\n- JQL queries have execution time limits; optimize for efficiency\n- Insight `bookmark_id` must reference an existing saved insight\n- JQL is a legacy feature; check Mixpanel documentation for current availability\n\n## Common Patterns\n\n### ID Resolution\n\n**Project name -> Project ID**:\n```\n1. Call MIXPANEL_GET_ALL_PROJECTS\n2. Find project by name in results\n3. Extract project id\n```\n\n**Funnel name -> Funnel ID**:\n```\n1. Call MIXPANEL_LIST_FUNNELS\n2. Find funnel by name\n3. Extract funnel_id\n```\n\n### Mixpanel Expression Syntax\n\nUsed in `where` and `on` parameters:\n- Property reference: `properties[\"property_name\"]`\n- Equality: `properties[\"country\"] == \"US\"`\n- Comparison: `properties[\"age\"] > 25`\n- Boolean: `properties[\"is_premium\"] == true`\n- Contains: `\"search_term\" in properties[\"name\"]`\n- AND\u002FOR: `properties[\"country\"] == \"US\" and properties[\"plan\"] == \"pro\"`\n\n### Pagination\n\n- Event queries: Follow date-based pagination by adjusting date ranges\n- Profile queries: Use `page` number and `session_id` for consistent results\n- Funnel\u002Fcohort lists: Typically return complete results without pagination\n\n## Known Pitfalls\n\n**Date Formats**:\n- Always use 'YYYY-MM-DD' format\n- Date ranges are inclusive on both ends\n- Data freshness depends on Mixpanel ingestion delay (typically minutes)\n\n**Expression Syntax**:\n- Property references always use `properties[\"name\"]` format\n- String values must be quoted: `properties[\"status\"] == \"active\"`\n- Numeric values are unquoted: `properties[\"count\"] > 10`\n- Boolean values: `true` \u002F `false` (lowercase)\n\n**Rate Limits**:\n- Mixpanel API has rate limits per project\n- Large segmentation queries may time out; reduce date range or segments\n- Use batch operations where available to minimize API calls\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Event data is typically grouped by date and segment\n- Numeric values may be returned as strings; parse explicitly\n- Empty date ranges return empty objects, not empty arrays\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | MIXPANEL_GET_ALL_PROJECTS | (none) |\n| Aggregate events | MIXPANEL_AGGREGATE_EVENT_COUNTS | event, from_date, to_date, unit |\n| Segmentation | MIXPANEL_QUERY_SEGMENTATION | event, on, from_date, to_date |\n| List funnels | MIXPANEL_LIST_FUNNELS | (none) |\n| Query funnel | MIXPANEL_QUERY_FUNNEL | funnel_id, from_date, to_date |\n| Query profiles | MIXPANEL_QUERY_PROFILES | where, output_properties, page |\n| Batch update profiles | MIXPANEL_PROFILE_BATCH_UPDATE | (profile update objects) |\n| List cohorts | MIXPANEL_COHORTS_LIST | (none) |\n| JQL query | MIXPANEL_JQL_QUERY | script |\n| Query insight | MIXPANEL_QUERY_INSIGHT | bookmark_id |\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\u002Fmixpanel-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 mixpanel-automation",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill mixpanel-automation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill mixpanel-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fmixpanel-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",[],[]]