[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSJ2DCTVVFN8NMRZ3913P2":3,"skill-same:01M6FSJ2DCTVVFN8NMRZ3913P2":71},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6FSJ2DCTVVFN8NMRZ3913P2","docusign-automation",null,"Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\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,39],"automation","docusign automation","docusign","MCP","tasks","search","templates","Tools","first","automate","management","document","community","signatures","composio","via","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.\"\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":45,"source":36,"requires":46,"description":7},"unknown",{"mcp":47},[48],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fdocusign-automation","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add reikiplanet\u002Fdaoskills --skill docusign-automation",{"tool":63,"command":64},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill docusign-automation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill docusign-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fdocusign-automation\u002FSKILL.md",true,[],[72,98,110,124,144,167],{"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":40},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[79,80,81,82,83,84,36,85,86,87,88,89,90,91,92,93,94,95,96,97],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":40},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[105,106,96,107,108,36,86,87,88,82,109,83],"ar","vr ar","interaction","requirements","performance",{"skillNo":111,"name":30,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":40},"01M6G60XNMHAMV1SV0EJ1CX0AY","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[30,116,117,118,119,120,36,121,88,122,123,82],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":40},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[131,132,133,134,135,36,136,137,138,139,121,140,141,142,143],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":40},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[151,152,153,154,155,156,157,158,36,88,82,159,83,160,161,162,163,164,165,166],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":40},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[174,175,176,177,178,179,180,181,164,121,182,183,184,36,185,186,187,161,188,189],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]