[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C9ST38ZHCHY6M83PWCWYR6":3,"skill-same:01M7C9ST38ZHCHY6M83PWCWYR6":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},"01M7C9ST38ZHCHY6M83PWCWYR6","freshservice-automation",null,"Automate Freshservice ITSM tasks via Rube MCP (Composio): create\u002Fupdate tickets, bulk operations, service requests, and outbound emails. 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\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Ffreshservice-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: freshservice-automation\ndescription: \"Automate Freshservice ITSM tasks via Rube MCP (Composio): create\u002Fupdate tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Freshservice Automation via Rube MCP\n\nAutomate Freshservice IT Service Management operations through Composio's Freshservice toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Freshservice connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `freshservice`\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 `freshservice`\n3. If connection is not ACTIVE, follow the returned auth link to complete Freshservice authentication\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 find, list, or search for tickets\n\n**Tool sequence**:\n1. `FRESHSERVICE_LIST_TICKETS` - List tickets with optional filtering and pagination [Required]\n2. `FRESHSERVICE_GET_TICKET` - Get detailed information for a specific ticket [Optional]\n\n**Key parameters for listing**:\n- `filter`: Predefined filter ('all_tickets', 'deleted', 'spam', 'watching')\n- `updated_since`: ISO 8601 timestamp to get tickets updated after this time\n- `order_by`: Sort field ('created_at', 'updated_at', 'status', 'priority')\n- `order_type`: Sort direction ('asc' or 'desc')\n- `page`: Page number (1-indexed)\n- `per_page`: Results per page (1-100, default 30)\n- `include`: Additional fields ('requester', 'stats', 'description', 'conversations', 'assets')\n\n**Key parameters for get**:\n- `ticket_id`: Unique ticket ID or display_id\n- `include`: Additional fields to include\n\n**Pitfalls**:\n- By default, only tickets created within the past 30 days are returned\n- Use `updated_since` to retrieve older tickets\n- Each `include` value consumes additional API credits\n- `page` is 1-indexed; minimum value is 1\n- `per_page` max is 100; default is 30\n- Ticket IDs can be the internal ID or the display_id shown in the UI\n\n### 2. Create a Ticket\n\n**When to use**: User wants to log a new incident or request\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_TICKET` - Create a new ticket [Required]\n\n**Key parameters**:\n- `subject`: Ticket subject line (required)\n- `description`: HTML description of the ticket (required)\n- `status`: Ticket status - 2 (Open), 3 (Pending), 4 (Resolved), 5 (Closed) (required)\n- `priority`: Ticket priority - 1 (Low), 2 (Medium), 3 (High), 4 (Urgent) (required)\n- `email`: Requester's email address (provide either email or requester_id)\n- `requester_id`: User ID of the requester\n- `type`: Ticket type ('Incident' or 'Service Request')\n- `source`: Channel - 1 (Email), 2 (Portal), 3 (Phone), 4 (Chat), 5 (Twitter), 6 (Facebook)\n- `impact`: Impact level - 1 (Low), 2 (Medium), 3 (High)\n- `urgency`: Urgency level - 1 (Low), 2 (Medium), 3 (High), 4 (Critical)\n\n**Pitfalls**:\n- `subject`, `description`, `status`, and `priority` are all required\n- Either `email` or `requester_id` must be provided to identify the requester\n- Status and priority use numeric codes, not string names\n- Description supports HTML formatting\n- If email does not match an existing contact, a new contact is created\n\n### 3. Bulk Update Tickets\n\n**When to use**: User wants to update multiple tickets at once\n\n**Tool sequence**:\n1. `FRESHSERVICE_LIST_TICKETS` - Find tickets to update [Prerequisite]\n2. `FRESHSERVICE_BULK_UPDATE_TICKETS` - Update multiple tickets [Required]\n\n**Key parameters**:\n- `ids`: Array of ticket IDs to update (required)\n- `update_fields`: Dictionary of fields to update (required)\n  - Allowed keys: 'subject', 'description', 'status', 'priority', 'responder_id', 'group_id', 'type', 'tags', 'custom_fields'\n\n**Pitfalls**:\n- Bulk update performs sequential updates internally; large batches may take time\n- All specified tickets receive the same field updates\n- If one ticket update fails, others may still succeed; check response for individual results\n- Cannot selectively update different fields per ticket in a single call\n- Custom fields must use their internal field names, not display names\n\n### 4. Create Ticket via Outbound Email\n\n**When to use**: User wants to create a ticket by sending an outbound email notification\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL` - Create ticket with email notification [Required]\n\n**Key parameters**:\n- `email`: Requester's email address (required)\n- `subject`: Email subject \u002F ticket subject (required)\n- `description`: HTML email body content\n- `status`: Ticket status (2=Open, 3=Pending, 4=Resolved, 5=Closed)\n- `priority`: Ticket priority (1=Low, 2=Medium, 3=High, 4=Urgent)\n- `cc_emails`: Array of CC email addresses\n- `email_config_id`: Email configuration ID for the sender address\n- `name`: Requester name\n\n**Pitfalls**:\n- This creates a standard ticket via the \u002Fapi\u002Fv2\u002Ftickets endpoint while sending an email\n- If the email does not match an existing contact, a new contact is created with the provided name\n- `email_config_id` determines which email address the notification appears to come from\n\n### 5. Create Service Requests\n\n**When to use**: User wants to submit a service catalog request\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_SERVICE_REQUEST` - Create a service request for a catalog item [Required]\n\n**Key parameters**:\n- `item_display_id`: Display ID of the catalog item (required)\n- `email`: Requester's email address\n- `quantity`: Number of items to request (default: 1)\n- `custom_fields`: Custom field values for the service item form\n- `parent_ticket_id`: Display ID of a parent ticket (for child requests)\n\n**Pitfalls**:\n- `item_display_id` can be found in Admin > Service Catalog > item URL (e.g., \u002Fservice_catalog\u002Fitems\u002F1)\n- Custom fields keys must match the service item form field names\n- Quantity defaults to 1 if not specified\n- Service requests follow the approval workflow defined for the catalog item\n\n## Common Patterns\n\n### Status Code Reference\n\n| Code | Status |\n|------|--------|\n| 2 | Open |\n| 3 | Pending |\n| 4 | Resolved |\n| 5 | Closed |\n\n### Priority Code Reference\n\n| Code | Priority |\n|------|----------|\n| 1 | Low |\n| 2 | Medium |\n| 3 | High |\n| 4 | Urgent |\n\n### Pagination\n\n- Use `page` (1-indexed) and `per_page` (max 100) parameters\n- Increment `page` by 1 each request\n- Continue until returned results count \u003C `per_page`\n- Default page size is 30\n\n### Finding Tickets by Date Range\n\n```\n1. Call FRESHSERVICE_LIST_TICKETS with updated_since='2024-01-01T00:00:00Z'\n2. Optionally add order_by='updated_at' and order_type='desc'\n3. Paginate through results\n```\n\n## Known Pitfalls\n\n**Numeric Codes**:\n- Status and priority use numeric values, not strings\n- Source channel uses numeric codes (1-6)\n- Impact and urgency use numeric codes (1-3 or 1-4)\n\n**Date Filtering**:\n- Default returns only tickets from the last 30 days\n- Use `updated_since` parameter for older tickets\n- Date format is ISO 8601 (e.g., '2024-01-01T00:00:00Z')\n\n**Rate Limits**:\n- Freshservice API has per-account rate limits\n- Each `include` option consumes additional API credits\n- Implement backoff on 429 responses\n\n**Response Parsing**:\n- Response data may be nested under `data` or `data.data`\n- Parse defensively with fallback patterns\n- Ticket IDs are numeric integers\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List tickets | FRESHSERVICE_LIST_TICKETS | filter, updated_since, page, per_page |\n| Get ticket | FRESHSERVICE_GET_TICKET | ticket_id, include |\n| Create ticket | FRESHSERVICE_CREATE_TICKET | subject, description, status, priority, email |\n| Bulk update | FRESHSERVICE_BULK_UPDATE_TICKETS | ids, update_fields |\n| Outbound email ticket | FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL | email, subject, description |\n| Service request | FRESHSERVICE_CREATE_SERVICE_REQUEST | item_display_id, email, quantity |\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","# Freshservice Automation via Rube MCP\n\nAutomate Freshservice IT Service Management operations through Composio's Freshservice toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Freshservice connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `freshservice`\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 `freshservice`\n3. If connection is not ACTIVE, follow the returned auth link to complete Freshservice authentication\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 find, list, or search for tickets\n\n**Tool sequence**:\n1. `FRESHSERVICE_LIST_TICKETS` - List tickets with optional filtering and pagination [Required]\n2. `FRESHSERVICE_GET_TICKET` - Get detailed information for a specific ticket [Optional]\n\n**Key parameters for listing**:\n- `filter`: Predefined filter ('all_tickets', 'deleted', 'spam', 'watching')\n- `updated_since`: ISO 8601 timestamp to get tickets updated after this time\n- `order_by`: Sort field ('created_at', 'updated_at', 'status', 'priority')\n- `order_type`: Sort direction ('asc' or 'desc')\n- `page`: Page number (1-indexed)\n- `per_page`: Results per page (1-100, default 30)\n- `include`: Additional fields ('requester', 'stats', 'description', 'conversations', 'assets')\n\n**Key parameters for get**:\n- `ticket_id`: Unique ticket ID or display_id\n- `include`: Additional fields to include\n\n**Pitfalls**:\n- By default, only tickets created within the past 30 days are returned\n- Use `updated_since` to retrieve older tickets\n- Each `include` value consumes additional API credits\n- `page` is 1-indexed; minimum value is 1\n- `per_page` max is 100; default is 30\n- Ticket IDs can be the internal ID or the display_id shown in the UI\n\n### 2. Create a Ticket\n\n**When to use**: User wants to log a new incident or request\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_TICKET` - Create a new ticket [Required]\n\n**Key parameters**:\n- `subject`: Ticket subject line (required)\n- `description`: HTML description of the ticket (required)\n- `status`: Ticket status - 2 (Open), 3 (Pending), 4 (Resolved), 5 (Closed) (required)\n- `priority`: Ticket priority - 1 (Low), 2 (Medium), 3 (High), 4 (Urgent) (required)\n- `email`: Requester's email address (provide either email or requester_id)\n- `requester_id`: User ID of the requester\n- `type`: Ticket type ('Incident' or 'Service Request')\n- `source`: Channel - 1 (Email), 2 (Portal), 3 (Phone), 4 (Chat), 5 (Twitter), 6 (Facebook)\n- `impact`: Impact level - 1 (Low), 2 (Medium), 3 (High)\n- `urgency`: Urgency level - 1 (Low), 2 (Medium), 3 (High), 4 (Critical)\n\n**Pitfalls**:\n- `subject`, `description`, `status`, and `priority` are all required\n- Either `email` or `requester_id` must be provided to identify the requester\n- Status and priority use numeric codes, not string names\n- Description supports HTML formatting\n- If email does not match an existing contact, a new contact is created\n\n### 3. Bulk Update Tickets\n\n**When to use**: User wants to update multiple tickets at once\n\n**Tool sequence**:\n1. `FRESHSERVICE_LIST_TICKETS` - Find tickets to update [Prerequisite]\n2. `FRESHSERVICE_BULK_UPDATE_TICKETS` - Update multiple tickets [Required]\n\n**Key parameters**:\n- `ids`: Array of ticket IDs to update (required)\n- `update_fields`: Dictionary of fields to update (required)\n  - Allowed keys: 'subject', 'description', 'status', 'priority', 'responder_id', 'group_id', 'type', 'tags', 'custom_fields'\n\n**Pitfalls**:\n- Bulk update performs sequential updates internally; large batches may take time\n- All specified tickets receive the same field updates\n- If one ticket update fails, others may still succeed; check response for individual results\n- Cannot selectively update different fields per ticket in a single call\n- Custom fields must use their internal field names, not display names\n\n### 4. Create Ticket via Outbound Email\n\n**When to use**: User wants to create a ticket by sending an outbound email notification\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL` - Create ticket with email notification [Required]\n\n**Key parameters**:\n- `email`: Requester's email address (required)\n- `subject`: Email subject \u002F ticket subject (required)\n- `description`: HTML email body content\n- `status`: Ticket status (2=Open, 3=Pending, 4=Resolved, 5=Closed)\n- `priority`: Ticket priority (1=Low, 2=Medium, 3=High, 4=Urgent)\n- `cc_emails`: Array of CC email addresses\n- `email_config_id`: Email configuration ID for the sender address\n- `name`: Requester name\n\n**Pitfalls**:\n- This creates a standard ticket via the \u002Fapi\u002Fv2\u002Ftickets endpoint while sending an email\n- If the email does not match an existing contact, a new contact is created with the provided name\n- `email_config_id` determines which email address the notification appears to come from\n\n### 5. Create Service Requests\n\n**When to use**: User wants to submit a service catalog request\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_SERVICE_REQUEST` - Create a service request for a catalog item [Required]\n\n**Key parameters**:\n- `item_display_id`: Display ID of the catalog item (required)\n- `email`: Requester's email address\n- `quantity`: Number of items to request (default: 1)\n- `custom_fields`: Custom field values for the service item form\n- `parent_ticket_id`: Display ID of a parent ticket (for child requests)\n\n**Pitfalls**:\n- `item_display_id` can be found in Admin > Service Catalog > item URL (e.g., \u002Fservice_catalog\u002Fitems\u002F1)\n- Custom fields keys must match the service item form field names\n- Quantity defaults to 1 if not specified\n- Service requests follow the approval workflow defined for the catalog item\n\n## Common Patterns\n\n### Status Code Reference\n\n| Code | Status |\n|------|--------|\n| 2 | Open |\n| 3 | Pending |\n| 4 | Resolved |\n| 5 | Closed |\n\n### Priority Code Reference\n\n| Code | Priority |\n|------|----------|\n| 1 | Low |\n| 2 | Medium |\n| 3 | High |\n| 4 | Urgent |\n\n### Pagination\n\n- Use `page` (1-indexed) and `per_page` (max 100) parameters\n- Increment `page` by 1 each request\n- Continue until returned results count \u003C `per_page`\n- Default page size is 30\n\n### Finding Tickets by Date Range\n\n```\n1. Call FRESHSERVICE_LIST_TICKETS with updated_since='2024-01-01T00:00:00Z'\n2. Optionally add order_by='updated_at' and order_type='desc'\n3. Paginate through results\n```\n\n## Known Pitfalls\n\n**Numeric Codes**:\n- Status and priority use numeric values, not strings\n- Source channel uses numeric codes (1-6)\n- Impact and urgency use numeric codes (1-3 or 1-4)\n\n**Date Filtering**:\n- Default returns only tickets from the last 30 days\n- Use `updated_since` parameter for older tickets\n- Date format is ISO 8601 (e.g., '2024-01-01T00:00:00Z')\n\n**Rate Limits**:\n- Freshservice API has per-account rate limits\n- Each `include` option consumes additional API credits\n- Implement backoff on 429 responses\n\n**Response Parsing**:\n- Response data may be nested under `data` or `data.data`\n- Parse defensively with fallback patterns\n- Ticket IDs are numeric integers\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List tickets | FRESHSERVICE_LIST_TICKETS | filter, updated_since, page, per_page |\n| Get ticket | FRESHSERVICE_GET_TICKET | ticket_id, include |\n| Create ticket | FRESHSERVICE_CREATE_TICKET | subject, description, status, priority, email |\n| Bulk update | FRESHSERVICE_BULK_UPDATE_TICKETS | ids, update_fields |\n| Outbound email ticket | FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL | email, subject, description |\n| Service request | FRESHSERVICE_CREATE_SERVICE_REQUEST | item_display_id, email, quantity |\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\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Ffreshservice-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 freshservice-automation",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill freshservice-automation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill freshservice-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Ffreshservice-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",[],[]]