[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMVEN9W751NRTX1W2X2WSJ":3,"skill-same:01M7CMVEN9W751NRTX1W2X2WSJ":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},"01M7CMVEN9W751NRTX1W2X2WSJ","posthog-automation",null,"Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. 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\u002Fposthog-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: posthog-automation\ndescription: \"Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# PostHog Automation via Rube MCP\n\nAutomate PostHog product analytics and feature flag management through Composio's PostHog toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active PostHog connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `posthog`\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 `posthog`\n3. If connection is not ACTIVE, follow the returned auth link to complete PostHog authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Capture Events\n\n**When to use**: User wants to send event data to PostHog for analytics tracking\n\n**Tool sequence**:\n1. `POSTHOG_CAPTURE_EVENT` - Send one or more events to PostHog [Required]\n\n**Key parameters**:\n- `event`: Event name (e.g., '$pageview', 'user_signed_up', 'purchase_completed')\n- `distinct_id`: Unique user identifier (required)\n- `properties`: Object with event-specific properties\n- `timestamp`: ISO 8601 timestamp (optional; defaults to server time)\n\n**Pitfalls**:\n- `distinct_id` is required for every event; identifies the user\u002Fdevice\n- PostHog system events use `$` prefix (e.g., '$pageview', '$identify')\n- Custom events should NOT use the `$` prefix\n- Properties are freeform; maintain consistent schemas across events\n- Events are processed asynchronously; ingestion delay is typically seconds\n\n### 2. List and Filter Events\n\n**When to use**: User wants to browse or search through captured events\n\n**Tool sequence**:\n1. `POSTHOG_LIST_AND_FILTER_PROJECT_EVENTS` - Query events with filters [Required]\n\n**Key parameters**:\n- `project_id`: PostHog project ID (required)\n- `event`: Filter by event name\n- `person_id`: Filter by person ID\n- `after`: Events after this ISO 8601 timestamp\n- `before`: Events before this ISO 8601 timestamp\n- `limit`: Maximum events to return\n- `offset`: Pagination offset\n\n**Pitfalls**:\n- `project_id` is required; resolve via LIST_PROJECTS first\n- Date filters use ISO 8601 format (e.g., '2024-01-15T00:00:00Z')\n- Large event volumes require pagination; use `offset` and `limit`\n- Results are returned in reverse chronological order by default\n- Event properties are nested; parse carefully\n\n### 3. Manage Feature Flags\n\n**When to use**: User wants to create, view, or manage feature flags\n\n**Tool sequence**:\n1. `POSTHOG_LIST_AND_MANAGE_PROJECT_FEATURE_FLAGS` - List existing feature flags [Required]\n2. `POSTHOG_RETRIEVE_FEATURE_FLAG_DETAILS` - Get detailed flag configuration [Optional]\n3. `POSTHOG_CREATE_FEATURE_FLAGS_FOR_PROJECT` - Create a new feature flag [Optional]\n\n**Key parameters**:\n- For listing: `project_id` (required)\n- For details: `project_id`, `id` (feature flag ID)\n- For creation:\n  - `project_id`: Target project\n  - `key`: Flag key (e.g., 'new-dashboard-beta')\n  - `name`: Human-readable name\n  - `filters`: Targeting rules and rollout percentage\n  - `active`: Whether the flag is enabled\n\n**Pitfalls**:\n- Feature flag `key` must be unique within a project\n- Flag keys should use kebab-case (e.g., 'my-feature-flag')\n- `filters` define targeting groups with properties and rollout percentages\n- Creating a flag with `active: true` immediately enables it for matching users\n- Flag changes take effect within seconds due to PostHog's polling mechanism\n\n### 4. Manage Projects\n\n**When to use**: User wants to list or inspect PostHog projects and organizations\n\n**Tool sequence**:\n1. `POSTHOG_LIST_PROJECTS_IN_ORGANIZATION_WITH_PAGINATION` - List all projects [Required]\n\n**Key parameters**:\n- `organization_id`: Organization identifier (may be optional depending on auth)\n- `limit`: Number of results per page\n- `offset`: Pagination offset\n\n**Pitfalls**:\n- Project IDs are numeric; used as parameters in most other endpoints\n- Organization ID may be required; check your PostHog setup\n- Pagination is offset-based; iterate until results are empty\n- Project settings include API keys and configuration details\n\n### 5. User Profile and Authentication\n\n**When to use**: User wants to check current user details or verify API access\n\n**Tool sequence**:\n1. `POSTHOG_WHOAMI` - Get current API user information [Optional]\n2. `POSTHOG_RETRIEVE_CURRENT_USER_PROFILE` - Get detailed user profile [Optional]\n\n**Key parameters**:\n- No required parameters for either call\n- Returns current authenticated user's details, permissions, and organization info\n\n**Pitfalls**:\n- WHOAMI is a lightweight check; use for verifying API connectivity\n- User profile includes organization membership and permissions\n- These endpoints confirm the API key's access level and scope\n\n## Common Patterns\n\n### ID Resolution\n\n**Organization -> Project ID**:\n```\n1. Call POSTHOG_LIST_PROJECTS_IN_ORGANIZATION_WITH_PAGINATION\n2. Find project by name in results\n3. Extract id (numeric) for use in other endpoints\n```\n\n**Feature flag name -> Flag ID**:\n```\n1. Call POSTHOG_LIST_AND_MANAGE_PROJECT_FEATURE_FLAGS with project_id\n2. Find flag by key or name\n3. Extract id for detailed operations\n```\n\n### Feature Flag Targeting\n\nFeature flags support sophisticated targeting:\n```json\n{\n  \"filters\": {\n    \"groups\": [\n      {\n        \"properties\": [\n          {\"key\": \"email\", \"value\": \"@company.com\", \"operator\": \"icontains\"}\n        ],\n        \"rollout_percentage\": 100\n      },\n      {\n        \"properties\": [],\n        \"rollout_percentage\": 10\n      }\n    ]\n  }\n}\n```\n- Groups are evaluated in order; first matching group determines the rollout\n- Properties filter users by their traits\n- Rollout percentage determines what fraction of matching users see the flag\n\n### Pagination\n\n- Events: Use `offset` and `limit` (offset-based)\n- Feature flags: Use `offset` and `limit` (offset-based)\n- Projects: Use `offset` and `limit` (offset-based)\n- Continue until results array is empty or smaller than `limit`\n\n## Known Pitfalls\n\n**Project IDs**:\n- Required for most API endpoints\n- Always resolve project names to numeric IDs first\n- Multiple projects can exist in one organization\n\n**Event Naming**:\n- System events use `$` prefix ($pageview, $identify, $autocapture)\n- Custom events should NOT use `$` prefix\n- Event names are case-sensitive; maintain consistency\n\n**Feature Flags**:\n- Flag keys must be unique within a project\n- Use kebab-case for flag keys\n- Changes propagate within seconds\n- Deleting a flag is permanent; consider disabling instead\n\n**Rate Limits**:\n- Event ingestion has throughput limits\n- Batch events where possible for efficiency\n- API endpoints have per-minute rate limits\n\n**Response Parsing**:\n- Response data may be nested under `data` or `results` key\n- Paginated responses include `count`, `next`, `previous` fields\n- Event properties are nested objects; access carefully\n- Parse defensively with fallbacks for optional fields\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Capture event | POSTHOG_CAPTURE_EVENT | event, distinct_id, properties |\n| List events | POSTHOG_LIST_AND_FILTER_PROJECT_EVENTS | project_id, event, after, before |\n| List feature flags | POSTHOG_LIST_AND_MANAGE_PROJECT_FEATURE_FLAGS | project_id |\n| Get flag details | POSTHOG_RETRIEVE_FEATURE_FLAG_DETAILS | project_id, id |\n| Create flag | POSTHOG_CREATE_FEATURE_FLAGS_FOR_PROJECT | project_id, key, filters |\n| List projects | POSTHOG_LIST_PROJECTS_IN_ORGANIZATION_WITH_PAGINATION | organization_id |\n| Who am I | POSTHOG_WHOAMI | (none) |\n| User profile | POSTHOG_RETRIEVE_CURRENT_USER_PROFILE | (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","# PostHog Automation via Rube MCP\n\nAutomate PostHog product analytics and feature flag management through Composio's PostHog toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active PostHog connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `posthog`\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 `posthog`\n3. If connection is not ACTIVE, follow the returned auth link to complete PostHog authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Capture Events\n\n**When to use**: User wants to send event data to PostHog for analytics tracking\n\n**Tool sequence**:\n1. `POSTHOG_CAPTURE_EVENT` - Send one or more events to PostHog [Required]\n\n**Key parameters**:\n- `event`: Event name (e.g., '$pageview', 'user_signed_up', 'purchase_completed')\n- `distinct_id`: Unique user identifier (required)\n- `properties`: Object with event-specific properties\n- `timestamp`: ISO 8601 timestamp (optional; defaults to server time)\n\n**Pitfalls**:\n- `distinct_id` is required for every event; identifies the user\u002Fdevice\n- PostHog system events use `$` prefix (e.g., '$pageview', '$identify')\n- Custom events should NOT use the `$` prefix\n- Properties are freeform; maintain consistent schemas across events\n- Events are processed asynchronously; ingestion delay is typically seconds\n\n### 2. List and Filter Events\n\n**When to use**: User wants to browse or search through captured events\n\n**Tool sequence**:\n1. `POSTHOG_LIST_AND_FILTER_PROJECT_EVENTS` - Query events with filters [Required]\n\n**Key parameters**:\n- `project_id`: PostHog project ID (required)\n- `event`: Filter by event name\n- `person_id`: Filter by person ID\n- `after`: Events after this ISO 8601 timestamp\n- `before`: Events before this ISO 8601 timestamp\n- `limit`: Maximum events to return\n- `offset`: Pagination offset\n\n**Pitfalls**:\n- `project_id` is required; resolve via LIST_PROJECTS first\n- Date filters use ISO 8601 format (e.g., '2024-01-15T00:00:00Z')\n- Large event volumes require pagination; use `offset` and `limit`\n- Results are returned in reverse chronological order by default\n- Event properties are nested; parse carefully\n\n### 3. Manage Feature Flags\n\n**When to use**: User wants to create, view, or manage feature flags\n\n**Tool sequence**:\n1. `POSTHOG_LIST_AND_MANAGE_PROJECT_FEATURE_FLAGS` - List existing feature flags [Required]\n2. `POSTHOG_RETRIEVE_FEATURE_FLAG_DETAILS` - Get detailed flag configuration [Optional]\n3. `POSTHOG_CREATE_FEATURE_FLAGS_FOR_PROJECT` - Create a new feature flag [Optional]\n\n**Key parameters**:\n- For listing: `project_id` (required)\n- For details: `project_id`, `id` (feature flag ID)\n- For creation:\n  - `project_id`: Target project\n  - `key`: Flag key (e.g., 'new-dashboard-beta')\n  - `name`: Human-readable name\n  - `filters`: Targeting rules and rollout percentage\n  - `active`: Whether the flag is enabled\n\n**Pitfalls**:\n- Feature flag `key` must be unique within a project\n- Flag keys should use kebab-case (e.g., 'my-feature-flag')\n- `filters` define targeting groups with properties and rollout percentages\n- Creating a flag with `active: true` immediately enables it for matching users\n- Flag changes take effect within seconds due to PostHog's polling mechanism\n\n### 4. Manage Projects\n\n**When to use**: User wants to list or inspect PostHog projects and organizations\n\n**Tool sequence**:\n1. `POSTHOG_LIST_PROJECTS_IN_ORGANIZATION_WITH_PAGINATION` - List all projects [Required]\n\n**Key parameters**:\n- `organization_id`: Organization identifier (may be optional depending on auth)\n- `limit`: Number of results per page\n- `offset`: Pagination offset\n\n**Pitfalls**:\n- Project IDs are numeric; used as parameters in most other endpoints\n- Organization ID may be required; check your PostHog setup\n- Pagination is offset-based; iterate until results are empty\n- Project settings include API keys and configuration details\n\n### 5. User Profile and Authentication\n\n**When to use**: User wants to check current user details or verify API access\n\n**Tool sequence**:\n1. `POSTHOG_WHOAMI` - Get current API user information [Optional]\n2. `POSTHOG_RETRIEVE_CURRENT_USER_PROFILE` - Get detailed user profile [Optional]\n\n**Key parameters**:\n- No required parameters for either call\n- Returns current authenticated user's details, permissions, and organization info\n\n**Pitfalls**:\n- WHOAMI is a lightweight check; use for verifying API connectivity\n- User profile includes organization membership and permissions\n- These endpoints confirm the API key's access level and scope\n\n## Common Patterns\n\n### ID Resolution\n\n**Organization -> Project ID**:\n```\n1. Call POSTHOG_LIST_PROJECTS_IN_ORGANIZATION_WITH_PAGINATION\n2. Find project by name in results\n3. Extract id (numeric) for use in other endpoints\n```\n\n**Feature flag name -> Flag ID**:\n```\n1. Call POSTHOG_LIST_AND_MANAGE_PROJECT_FEATURE_FLAGS with project_id\n2. Find flag by key or name\n3. Extract id for detailed operations\n```\n\n### Feature Flag Targeting\n\nFeature flags support sophisticated targeting:\n```json\n{\n  \"filters\": {\n    \"groups\": [\n      {\n        \"properties\": [\n          {\"key\": \"email\", \"value\": \"@company.com\", \"operator\": \"icontains\"}\n        ],\n        \"rollout_percentage\": 100\n      },\n      {\n        \"properties\": [],\n        \"rollout_percentage\": 10\n      }\n    ]\n  }\n}\n```\n- Groups are evaluated in order; first matching group determines the rollout\n- Properties filter users by their traits\n- Rollout percentage determines what fraction of matching users see the flag\n\n### Pagination\n\n- Events: Use `offset` and `limit` (offset-based)\n- Feature flags: Use `offset` and `limit` (offset-based)\n- Projects: Use `offset` and `limit` (offset-based)\n- Continue until results array is empty or smaller than `limit`\n\n## Known Pitfalls\n\n**Project IDs**:\n- Required for most API endpoints\n- Always resolve project names to numeric IDs first\n- Multiple projects can exist in one organization\n\n**Event Naming**:\n- System events use `$` prefix ($pageview, $identify, $autocapture)\n- Custom events should NOT use `$` prefix\n- Event names are case-sensitive; maintain consistency\n\n**Feature Flags**:\n- Flag keys must be unique within a project\n- Use kebab-case for flag keys\n- Changes propagate within seconds\n- Deleting a flag is permanent; consider disabling instead\n\n**Rate Limits**:\n- Event ingestion has throughput limits\n- Batch events where possible for efficiency\n- API endpoints have per-minute rate limits\n\n**Response Parsing**:\n- Response data may be nested under `data` or `results` key\n- Paginated responses include `count`, `next`, `previous` fields\n- Event properties are nested objects; access carefully\n- Parse defensively with fallbacks for optional fields\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Capture event | POSTHOG_CAPTURE_EVENT | event, distinct_id, properties |\n| List events | POSTHOG_LIST_AND_FILTER_PROJECT_EVENTS | project_id, event, after, before |\n| List feature flags | POSTHOG_LIST_AND_MANAGE_PROJECT_FEATURE_FLAGS | project_id |\n| Get flag details | POSTHOG_RETRIEVE_FEATURE_FLAG_DETAILS | project_id, id |\n| Create flag | POSTHOG_CREATE_FEATURE_FLAGS_FOR_PROJECT | project_id, key, filters |\n| List projects | POSTHOG_LIST_PROJECTS_IN_ORGANIZATION_WITH_PAGINATION | organization_id |\n| Who am I | POSTHOG_WHOAMI | (none) |\n| User profile | POSTHOG_RETRIEVE_CURRENT_USER_PROFILE | (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\u002Fposthog-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 posthog-automation",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill posthog-automation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill posthog-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fposthog-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",[],[]]