[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BXWDHBT2T20D8PXCE910S9":3,"skill-same:01M7BXWDHBT2T20D8PXCE910S9":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7BXWDHBT2T20D8PXCE910S9","docusign-automation",null,"Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-all-skills\u002Fskills\u002Fdocusign-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: docusign-automation\ndescription: \"Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\ncategory: business-productivity\n---\n\n# DocuSign Automation via Rube MCP\n\nAutomate DocuSign e-signature workflows through Composio's DocuSign toolkit via Rube MCP.\n\n**Toolkit docs**: [composio.dev\u002Ftoolkits\u002Fdocusign](https:\u002F\u002Fcomposio.dev\u002Ftoolkits\u002Fdocusign)\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active DocuSign connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docusign`\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 `docusign`\n3. If connection is not ACTIVE, follow the returned auth link to complete DocuSign OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Browse and Select Templates\n\n**When to use**: User wants to find available document templates for sending\n\n**Tool sequence**:\n1. `DOCUSIGN_LIST_ALL_TEMPLATES` - List all available templates [Required]\n2. `DOCUSIGN_GET_TEMPLATE` - Get detailed template information [Optional]\n\n**Key parameters**:\n- For listing: Optional search\u002Ffilter parameters\n- For details: `templateId` (from list results)\n- Response includes template `templateId`, `name`, `description`, roles, and fields\n\n**Pitfalls**:\n- Template IDs are GUIDs (e.g., '12345678-abcd-1234-efgh-123456789012')\n- Templates define recipient roles with signing tabs; understand roles before creating envelopes\n- Large template libraries require pagination; check for continuation tokens\n- Template access depends on account permissions\n\n### 2. Create and Send Envelopes from Templates\n\n**When to use**: User wants to send documents for signature using a pre-built template\n\n**Tool sequence**:\n1. `DOCUSIGN_LIST_ALL_TEMPLATES` - Find the template to use [Prerequisite]\n2. `DOCUSIGN_GET_TEMPLATE` - Review template roles and fields [Optional]\n3. `DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE` - Create the envelope [Required]\n4. `DOCUSIGN_SEND_ENVELOPE` - Send the envelope for signing [Required]\n\n**Key parameters**:\n- For CREATE_ENVELOPE_FROM_TEMPLATE:\n  - `templateId`: Template to use\n  - `templateRoles`: Array of role assignments with `roleName`, `name`, `email`\n  - `status`: 'created' (draft) or 'sent' (send immediately)\n  - `emailSubject`: Custom subject line for the signing email\n  - `emailBlurb`: Custom message in the signing email\n- For SEND_ENVELOPE:\n  - `envelopeId`: Envelope ID from creation response\n\n**Pitfalls**:\n- `templateRoles` must match the role names defined in the template exactly (case-sensitive)\n- Setting `status` to 'sent' during creation sends immediately; use 'created' for drafts\n- If status is 'sent' at creation, no need to call SEND_ENVELOPE separately\n- Each role requires at minimum `roleName`, `name`, and `email`\n- `emailSubject` overrides the template's default email subject\n\n### 3. Monitor Envelope Status\n\n**When to use**: User wants to check the status of sent envelopes or track signing progress\n\n**Tool sequence**:\n1. `DOCUSIGN_GET_ENVELOPE` - Get envelope details and status [Required]\n\n**Key parameters**:\n- `envelopeId`: Envelope identifier (GUID)\n- Response includes `status`, `recipients`, `sentDateTime`, `completedDateTime`\n\n**Pitfalls**:\n- Envelope statuses: 'created', 'sent', 'delivered', 'signed', 'completed', 'declined', 'voided'\n- 'delivered' means the email was opened, not that the document was signed\n- 'completed' means all recipients have signed\n- Recipients array shows individual signing status per recipient\n- Envelope IDs are GUIDs; always resolve from creation or search results\n\n### 4. Add Templates to Existing Envelopes\n\n**When to use**: User wants to add additional documents or templates to an existing envelope\n\n**Tool sequence**:\n1. `DOCUSIGN_GET_ENVELOPE` - Verify envelope exists and is in draft state [Prerequisite]\n2. `DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE` - Add template to envelope [Required]\n\n**Key parameters**:\n- `envelopeId`: Target envelope ID\n- `documentId`: Document ID within the envelope\n- `templateId`: Template to add\n\n**Pitfalls**:\n- Envelope must be in 'created' (draft) status to add templates\n- Cannot add templates to already-sent envelopes\n- Document IDs are sequential within an envelope (starting from '1')\n- Adding a template merges its fields and roles into the existing envelope\n\n### 5. Manage Envelope Lifecycle\n\n**When to use**: User wants to send, void, or manage draft envelopes\n\n**Tool sequence**:\n1. `DOCUSIGN_GET_ENVELOPE` - Check current envelope status [Prerequisite]\n2. `DOCUSIGN_SEND_ENVELOPE` - Send a draft envelope [Optional]\n\n**Key parameters**:\n- `envelopeId`: Envelope to manage\n- For sending: envelope must be in 'created' status with all required recipients\n\n**Pitfalls**:\n- Only 'created' (draft) envelopes can be sent\n- Sent envelopes cannot be unsent; they can only be voided\n- Voiding an envelope notifies all recipients\n- All required recipients must have valid email addresses before sending\n\n## Common Patterns\n\n### ID Resolution\n\n**Template name -> Template ID**:\n```\n1. Call DOCUSIGN_LIST_ALL_TEMPLATES\n2. Find template by name in results\n3. Extract templateId (GUID format)\n```\n\n**Envelope tracking**:\n```\n1. Store envelopeId from CREATE_ENVELOPE_FROM_TEMPLATE response\n2. Call DOCUSIGN_GET_ENVELOPE periodically to check status\n3. Check recipient-level status for individual signing progress\n```\n\n### Template Role Mapping\n\nWhen creating an envelope from a template:\n```\n1. Call DOCUSIGN_GET_TEMPLATE to see defined roles\n2. Map each role to actual recipients:\n   {\n     \"roleName\": \"Signer 1\",     \u002F\u002F Must match template role name exactly\n     \"name\": \"John Smith\",\n     \"email\": \"john@example.com\"\n   }\n3. Include ALL required roles in templateRoles array\n```\n\n### Envelope Status Flow\n\n```\ncreated (draft) -> sent -> delivered -> signed -> completed\n                       \\-> declined\n                       \\-> voided (by sender)\n```\n\n## Known Pitfalls\n\n**Template Roles**:\n- Role names are case-sensitive; must match template definition exactly\n- All required roles must be assigned when creating an envelope\n- Missing role assignments cause envelope creation to fail\n\n**Envelope Status**:\n- 'delivered' means email opened, NOT document signed\n- 'completed' is the final successful state (all parties signed)\n- Status transitions are one-way; cannot revert to previous states\n\n**GUIDs**:\n- All DocuSign IDs (templates, envelopes) are GUID format\n- Always resolve names to GUIDs via list\u002Fsearch endpoints\n- Do not hardcode GUIDs; they are unique per account\n\n**Rate Limits**:\n- DocuSign API has per-account rate limits\n- Bulk envelope creation should be throttled\n- Polling envelope status should use reasonable intervals (30-60 seconds)\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Recipient information is nested within envelope response\n- Date fields use ISO 8601 format\n- Parse defensively with fallbacks for optional fields\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List templates | DOCUSIGN_LIST_ALL_TEMPLATES | (optional filters) |\n| Get template | DOCUSIGN_GET_TEMPLATE | templateId |\n| Create envelope | DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE | templateId, templateRoles, status |\n| Send envelope | DOCUSIGN_SEND_ENVELOPE | envelopeId |\n| Get envelope status | DOCUSIGN_GET_ENVELOPE | envelopeId |\n| Add template to envelope | DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE | envelopeId, documentId, templateId |\n\n---\n*Powered by [Composio](https:\u002F\u002Fcomposio.dev)*\n","# DocuSign Automation via Rube MCP\n\nAutomate DocuSign e-signature workflows through Composio's DocuSign toolkit via Rube MCP.\n\n**Toolkit docs**: [composio.dev\u002Ftoolkits\u002Fdocusign](https:\u002F\u002Fcomposio.dev\u002Ftoolkits\u002Fdocusign)\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active DocuSign connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docusign`\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 `docusign`\n3. If connection is not ACTIVE, follow the returned auth link to complete DocuSign OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Browse and Select Templates\n\n**When to use**: User wants to find available document templates for sending\n\n**Tool sequence**:\n1. `DOCUSIGN_LIST_ALL_TEMPLATES` - List all available templates [Required]\n2. `DOCUSIGN_GET_TEMPLATE` - Get detailed template information [Optional]\n\n**Key parameters**:\n- For listing: Optional search\u002Ffilter parameters\n- For details: `templateId` (from list results)\n- Response includes template `templateId`, `name`, `description`, roles, and fields\n\n**Pitfalls**:\n- Template IDs are GUIDs (e.g., '12345678-abcd-1234-efgh-123456789012')\n- Templates define recipient roles with signing tabs; understand roles before creating envelopes\n- Large template libraries require pagination; check for continuation tokens\n- Template access depends on account permissions\n\n### 2. Create and Send Envelopes from Templates\n\n**When to use**: User wants to send documents for signature using a pre-built template\n\n**Tool sequence**:\n1. `DOCUSIGN_LIST_ALL_TEMPLATES` - Find the template to use [Prerequisite]\n2. `DOCUSIGN_GET_TEMPLATE` - Review template roles and fields [Optional]\n3. `DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE` - Create the envelope [Required]\n4. `DOCUSIGN_SEND_ENVELOPE` - Send the envelope for signing [Required]\n\n**Key parameters**:\n- For CREATE_ENVELOPE_FROM_TEMPLATE:\n  - `templateId`: Template to use\n  - `templateRoles`: Array of role assignments with `roleName`, `name`, `email`\n  - `status`: 'created' (draft) or 'sent' (send immediately)\n  - `emailSubject`: Custom subject line for the signing email\n  - `emailBlurb`: Custom message in the signing email\n- For SEND_ENVELOPE:\n  - `envelopeId`: Envelope ID from creation response\n\n**Pitfalls**:\n- `templateRoles` must match the role names defined in the template exactly (case-sensitive)\n- Setting `status` to 'sent' during creation sends immediately; use 'created' for drafts\n- If status is 'sent' at creation, no need to call SEND_ENVELOPE separately\n- Each role requires at minimum `roleName`, `name`, and `email`\n- `emailSubject` overrides the template's default email subject\n\n### 3. Monitor Envelope Status\n\n**When to use**: User wants to check the status of sent envelopes or track signing progress\n\n**Tool sequence**:\n1. `DOCUSIGN_GET_ENVELOPE` - Get envelope details and status [Required]\n\n**Key parameters**:\n- `envelopeId`: Envelope identifier (GUID)\n- Response includes `status`, `recipients`, `sentDateTime`, `completedDateTime`\n\n**Pitfalls**:\n- Envelope statuses: 'created', 'sent', 'delivered', 'signed', 'completed', 'declined', 'voided'\n- 'delivered' means the email was opened, not that the document was signed\n- 'completed' means all recipients have signed\n- Recipients array shows individual signing status per recipient\n- Envelope IDs are GUIDs; always resolve from creation or search results\n\n### 4. Add Templates to Existing Envelopes\n\n**When to use**: User wants to add additional documents or templates to an existing envelope\n\n**Tool sequence**:\n1. `DOCUSIGN_GET_ENVELOPE` - Verify envelope exists and is in draft state [Prerequisite]\n2. `DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE` - Add template to envelope [Required]\n\n**Key parameters**:\n- `envelopeId`: Target envelope ID\n- `documentId`: Document ID within the envelope\n- `templateId`: Template to add\n\n**Pitfalls**:\n- Envelope must be in 'created' (draft) status to add templates\n- Cannot add templates to already-sent envelopes\n- Document IDs are sequential within an envelope (starting from '1')\n- Adding a template merges its fields and roles into the existing envelope\n\n### 5. Manage Envelope Lifecycle\n\n**When to use**: User wants to send, void, or manage draft envelopes\n\n**Tool sequence**:\n1. `DOCUSIGN_GET_ENVELOPE` - Check current envelope status [Prerequisite]\n2. `DOCUSIGN_SEND_ENVELOPE` - Send a draft envelope [Optional]\n\n**Key parameters**:\n- `envelopeId`: Envelope to manage\n- For sending: envelope must be in 'created' status with all required recipients\n\n**Pitfalls**:\n- Only 'created' (draft) envelopes can be sent\n- Sent envelopes cannot be unsent; they can only be voided\n- Voiding an envelope notifies all recipients\n- All required recipients must have valid email addresses before sending\n\n## Common Patterns\n\n### ID Resolution\n\n**Template name -> Template ID**:\n```\n1. Call DOCUSIGN_LIST_ALL_TEMPLATES\n2. Find template by name in results\n3. Extract templateId (GUID format)\n```\n\n**Envelope tracking**:\n```\n1. Store envelopeId from CREATE_ENVELOPE_FROM_TEMPLATE response\n2. Call DOCUSIGN_GET_ENVELOPE periodically to check status\n3. Check recipient-level status for individual signing progress\n```\n\n### Template Role Mapping\n\nWhen creating an envelope from a template:\n```\n1. Call DOCUSIGN_GET_TEMPLATE to see defined roles\n2. Map each role to actual recipients:\n   {\n     \"roleName\": \"Signer 1\",     \u002F\u002F Must match template role name exactly\n     \"name\": \"John Smith\",\n     \"email\": \"john@example.com\"\n   }\n3. Include ALL required roles in templateRoles array\n```\n\n### Envelope Status Flow\n\n```\ncreated (draft) -> sent -> delivered -> signed -> completed\n                       \\-> declined\n                       \\-> voided (by sender)\n```\n\n## Known Pitfalls\n\n**Template Roles**:\n- Role names are case-sensitive; must match template definition exactly\n- All required roles must be assigned when creating an envelope\n- Missing role assignments cause envelope creation to fail\n\n**Envelope Status**:\n- 'delivered' means email opened, NOT document signed\n- 'completed' is the final successful state (all parties signed)\n- Status transitions are one-way; cannot revert to previous states\n\n**GUIDs**:\n- All DocuSign IDs (templates, envelopes) are GUID format\n- Always resolve names to GUIDs via list\u002Fsearch endpoints\n- Do not hardcode GUIDs; they are unique per account\n\n**Rate Limits**:\n- DocuSign API has per-account rate limits\n- Bulk envelope creation should be throttled\n- Polling envelope status should use reasonable intervals (30-60 seconds)\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Recipient information is nested within envelope response\n- Date fields use ISO 8601 format\n- Parse defensively with fallbacks for optional fields\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List templates | DOCUSIGN_LIST_ALL_TEMPLATES | (optional filters) |\n| Get template | DOCUSIGN_GET_TEMPLATE | templateId |\n| Create envelope | DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE | templateId, templateRoles, status |\n| Send envelope | DOCUSIGN_SEND_ENVELOPE | envelopeId |\n| Get envelope status | DOCUSIGN_GET_ENVELOPE | envelopeId |\n| Add template to envelope | DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE | envelopeId, documentId, templateId |\n\n---\n*Powered by [Composio](https:\u002F\u002Fcomposio.dev)*\n",{"name":5,"category":24,"requires":25,"description":7},"business-productivity",{"mcp":26},[27],"rube","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-all-skills\u002Fskills\u002Fdocusign-automation",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill docusign-automation",{"tool":43,"command":44},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill docusign-automation",{"tool":46,"command":47},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill docusign-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-all-skills\u002Fskills\u002Fdocusign-automation\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]