[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CSX9TYPK4F73SE2ZS9BYB4":3,"skill-same:01M6CSX9TYPK4F73SE2ZS9BYB4":82},{"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":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6CSX9TYPK4F73SE2ZS9BYB4","docusign-automation",null,"Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.","Sam-06060\u002Fjarvis-assistant","Sam-06060","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F208600848?v=4","01M6CRKT7C7FXD21V6HXF293S0","Samson Frank Ganta","01M6CRKTBEKYFD8YX5Z1GT99EE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fdocusign-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"automation","docusign automation","docusign","MCP","tasks","search","templates","Tools","first","automate","management","document","community","signatures","composio","2026-11-10 10:12:30",false,"---\nname: docusign-automation\ndescription: \"Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\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":44,"source":36,"date_added":45,"description":7},"unknown","2026-02-27","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fdocusign-automation",0,"https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant","https:\u002F\u002Fgithub.com\u002FSam-06060","Mobile Application Developer | Kotlin | Flutter, KMP, Swfit, Android,Swift UI | Building at Saar It Resources | Creator of Jarvis (AI Assistant)","2026-06-23 05:13:38",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill docusign-automation",{"tool":60,"command":61},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill docusign-automation",{"tool":63,"command":64},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill docusign-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fdocusign-automation\u002FSKILL.md",true,[68,74,78],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Ftriggers.json","REFERENCE","参考文档",3258,"https:\u002F\u002Fgithub.com\u002Fevent4u-app\u002Fagent-config\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Froadmap-writing\u002Fevals\u002Ftriggers.json",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Ffollow-up-roadmap-shape.md",1874,"https:\u002F\u002Fgithub.com\u002Fevent4u-app\u002Fagent-config\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Froadmap-writing\u002Freferences\u002Ffollow-up-roadmap-shape.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Finflation-checklist.md",1516,"https:\u002F\u002Fgithub.com\u002Fevent4u-app\u002Fagent-config\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Froadmap-writing\u002Freferences\u002Finflation-checklist.md",[83,94,110,127,145,172],{"skillNo":84,"name":85,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":91,"publishedAt":39},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[92,93],"Test Skill","test",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":39},"01M6GDRQ40HX22MA6XWC31RHHK","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzustand-store-ts\u002FSKILL.md",[],[101,102,103,104,105,106,107,36,108,109],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":117,"publishedAt":39},"01M6GDRKEA0WE670SPFWX5GKCN","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoom-automation\u002FSKILL.md",[116],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,118,119,32,31,29,27,120,121,33,122,123,124,38,36,125,34,126],"zoom automation","zoom","via","meeting","critical","creation","webinars","recordings","tracking",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":39},"01M6GDRFS1452PC71JQ38S24HR","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoho-crm-automation\u002FSKILL.md",[133],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[135,24,136,137,138,139,140,36,29,141,38,142,122,33,31,143,108,28,27,144],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","manage",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":154,"publishedAt":39},"01M6GDRCKQBAVTGHX5XBH26KPZ","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzod-validation-expert\u002FSKILL.md",[151],{"categoryNo":152,"categoryName":153,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[155,156,157,158,159,109,160,161,162,163,164,165,104,166,167,168,169,36,170,171],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":179,"publishedAt":39},"01M6GDR658B08K4MY0RWD4A6EH","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzeroize-audit\u002FSKILL.md",[178],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[180,181,182,183,184,185,186,187,36,188,189,190,191,192,193,194,195,196,197,27],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]