[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71S5N08BZX53TERK820WWA1":3,"skill-same:01M71S5N08BZX53TERK820WWA1":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M71S5N08BZX53TERK820WWA1","docusign-automation",null,"Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.","javiertarazon\u002Fide-agente-free-jt7-","javiertarazon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153141207?v=4","01M71R52TB3S9HXKH6WSNT8A7V","01M71R52VG5KS2DKDDH4GDQ30A",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fdocusign-automation\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"automation","docusign automation","docusign","automate","Tools","management","composio","search tools","templates","via","first","tasks","unknown","document","MCP","document management","signatures","search","for","community","2026-11-10 13:02:02",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]\nrisk: unknown\nsource: community\n---\n\n# DocuSign Automation via Rube MCP\n\nAutomate DocuSign e-signature workflows through Composio's DocuSign toolkit via Rube MCP.\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## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# DocuSign Automation via Rube MCP\n\nAutomate DocuSign e-signature workflows through Composio's DocuSign toolkit via Rube MCP.\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## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":35,"source":42,"requires":48,"description":7},{"mcp":49},[50],"rube","release\u002Fv4.2.11-panel-pro","a92ea02bcf7e2b3dbaf46d49696c29a3cb490d4f",".github\u002Fskills\u002Fdocusign-automation","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-","https:\u002F\u002Fgithub.com\u002Fjaviertarazon","2026-07-12 07:10:45",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add javiertarazon\u002Fide-agente-free-jt7- --skill docusign-automation",{"tool":63,"command":64},"bunx","bunx skills add javiertarazon\u002Fide-agente-free-jt7- --skill docusign-automation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add javiertarazon\u002Fide-agente-free-jt7- --skill docusign-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fdocusign-automation\u002FSKILL.md",true,[],[72,99,115,134,148,170],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":81,"publishedAt":43},"01M71TQ7Q6Z10VWF3C2H5X1KW9","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[82,83,84,42,85,86,87,88,89,35,90,91,92,93,94,95,96,28,97,98],"zustand","store","zustand store ts","middleware","implementing","use","react state management","when","react","with","state","create","state management","typescript","action","separation","global",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":106,"publishedAt":43},"01M71TQ5EAR40G6W0MV5ZDVEZT","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[105],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[107,108,23,42,109,41,40,110,37,35,33,32,111,30,112,113,29,114,28,27],"zoom automation","zoom","creation","schemas","meeting","tracking","webinars","recordings",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":43},"01M71TQ29B1EYBCEAP1ZBGXQ1A","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[121],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[123,124,23,125,126,127,42,128,129,41,130,40,110,131,37,35,132,34,133,93],"crm automation","zoho crm automation","crm","zoho crm","zoho","leads","manage leads","manage","records","convert","contacts",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":43},"01M71TPZPMN60DH0XV58KVHY23","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[140],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[142,23,143,42,41,40,110,37,144,35,34,145,146,33,32,147,30,29,27,26],"zendesk automation","zendesk","organizations","replies","users","tickets",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":43},"01M71TPXDWKHKG4N6TVEPXWD0N","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[155,156,157,158,159,160,161,162,163,23,164,35,165,166,167,168,169,26],"zapier make patterns","zapier","patterns","make","No-Code","complexity","writing","spawner","business","workflow","code","integromat","apache","processes","but",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"publishedAt":43},"01M71TPT5T10WXNKW9G7ZXZ27W","youtube-summarizer","Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fyoutube-summarizer\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[180,181,182,183,42,184,185,186,187,188,189,190,165,191,192,193,194,195,196,197],"summarizer","youtube","youtube summarizer","Video","content-analysis","frameworks","copilot","2025","github-copilot","extract transcripts","analysis","codex","cli","summaries","github","generate","summarization","2026"]