[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSJB0WJE5FPXJ8JVCD9N6Z":3,"skill-same:01M6FSJB0WJE5FPXJ8JVCD9N6Z":81},{"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":31,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":14,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6FSJB0WJE5FPXJ8JVCD9N6Z","figma-automation",null,"Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. 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\u002Ffigma-automation\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"automation","figma","figma automation","automate","comments","via","tokens","composio","community","files","design tokens","design","first","Tools","search","tasks","components","MCP","2026-11-10 10:12:30",false,"---\nname: figma-automation\ndescription: \"Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Figma Automation via Rube MCP\n\nAutomate Figma operations through Composio's Figma toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Figma connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `figma`\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 `figma`\n3. If connection is not ACTIVE, follow the returned auth link to complete Figma auth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Get File Data and Components\n\n**When to use**: User wants to inspect Figma design files or extract component information\n\n**Tool sequence**:\n1. `FIGMA_DISCOVER_FIGMA_RESOURCES` - Extract IDs from Figma URLs [Prerequisite]\n2. `FIGMA_GET_FILE_JSON` - Get file data (simplified by default) [Required]\n3. `FIGMA_GET_FILE_NODES` - Get specific node data [Optional]\n4. `FIGMA_GET_FILE_COMPONENTS` - List published components [Optional]\n5. `FIGMA_GET_FILE_COMPONENT_SETS` - List component sets [Optional]\n\n**Key parameters**:\n- `file_key`: File key from URL (e.g., 'abc123XYZ' from figma.com\u002Fdesign\u002Fabc123XYZ\u002F...)\n- `ids`: Comma-separated node IDs (NOT an array)\n- `depth`: Tree traversal depth (2 for pages and top-level children)\n- `simplify`: True for AI-friendly format (70%+ size reduction)\n\n**Pitfalls**:\n- Only supports Design files; FigJam boards and Slides return 400 errors\n- `ids` must be a comma-separated string, not an array\n- Node IDs may be dash-formatted (1-541) in URLs but need colon format (1:541) for API\n- Broad ids\u002Fdepth can trigger oversized payloads (413); narrow scope or reduce depth\n- Response data may be in `data_preview` instead of `data`\n\n### 2. Export and Render Images\n\n**When to use**: User wants to export design assets as images\n\n**Tool sequence**:\n1. `FIGMA_GET_FILE_JSON` - Find node IDs to export [Prerequisite]\n2. `FIGMA_RENDER_IMAGES_OF_FILE_NODES` - Render nodes as images [Required]\n3. `FIGMA_DOWNLOAD_FIGMA_IMAGES` - Download rendered images [Optional]\n4. `FIGMA_GET_IMAGE_FILLS` - Get image fill URLs [Optional]\n\n**Key parameters**:\n- `file_key`: File key\n- `ids`: Comma-separated node IDs to render\n- `format`: 'png', 'svg', 'jpg', or 'pdf'\n- `scale`: Scale factor (0.01-4.0) for PNG\u002FJPG\n- `images`: Array of {node_id, file_name, format} for downloads\n\n**Pitfalls**:\n- Images return as node_id-to-URL map; some IDs may be null (failed renders)\n- URLs are temporary (valid ~30 days)\n- Images capped at 32 megapixels; larger requests auto-scaled down\n\n### 3. Extract Design Tokens\n\n**When to use**: User wants to extract design tokens for development\n\n**Tool sequence**:\n1. `FIGMA_EXTRACT_DESIGN_TOKENS` - Extract colors, typography, spacing [Required]\n2. `FIGMA_DESIGN_TOKENS_TO_TAILWIND` - Convert to Tailwind config [Optional]\n\n**Key parameters**:\n- `file_key`: File key\n- `include_local_styles`: Include local styles (default true)\n- `include_variables`: Include Figma variables\n- `tokens`: Full tokens object from extraction (for Tailwind conversion)\n\n**Pitfalls**:\n- Tailwind conversion requires the full tokens object including total_tokens and sources\n- Do not strip fields from the extraction response before passing to conversion\n\n### 4. Manage Comments and Versions\n\n**When to use**: User wants to view or add comments, or inspect version history\n\n**Tool sequence**:\n1. `FIGMA_GET_COMMENTS_IN_A_FILE` - List all file comments [Optional]\n2. `FIGMA_ADD_A_COMMENT_TO_A_FILE` - Add a comment [Optional]\n3. `FIGMA_GET_REACTIONS_FOR_A_COMMENT` - Get comment reactions [Optional]\n4. `FIGMA_GET_VERSIONS_OF_A_FILE` - Get version history [Optional]\n\n**Key parameters**:\n- `file_key`: File key\n- `as_md`: Return comments in Markdown format\n- `message`: Comment text\n- `comment_id`: Comment ID for reactions\n\n**Pitfalls**:\n- Comments can be positioned on specific nodes using client_meta\n- Reply comments cannot be nested (only one level of replies)\n\n### 5. Browse Projects and Teams\n\n**When to use**: User wants to list team projects or files\n\n**Tool sequence**:\n1. `FIGMA_GET_PROJECTS_IN_A_TEAM` - List team projects [Optional]\n2. `FIGMA_GET_FILES_IN_A_PROJECT` - List project files [Optional]\n3. `FIGMA_GET_TEAM_STYLES` - List team published styles [Optional]\n\n**Key parameters**:\n- `team_id`: Team ID from URL (figma.com\u002Ffiles\u002Fteam\u002FTEAM_ID\u002F...)\n- `project_id`: Project ID\n\n**Pitfalls**:\n- Team ID cannot be obtained programmatically; extract from Figma URL\n- Only published styles\u002Fcomponents are returned by team endpoints\n\n## Common Patterns\n\n### URL Parsing\n\nExtract IDs from Figma URLs:\n```\n1. Call FIGMA_DISCOVER_FIGMA_RESOURCES with figma_url\n2. Extract file_key, node_id, team_id from response\n3. Convert dash-format node IDs (1-541) to colon format (1:541)\n```\n\n### Node Traversal\n\n```\n1. Call FIGMA_GET_FILE_JSON with depth=2 for overview\n2. Identify target nodes from the response\n3. Call again with specific ids and higher depth for details\n```\n\n## Known Pitfalls\n\n**File Type Support**:\n- GET_FILE_JSON only supports Design files (figma.com\u002Fdesign\u002F or figma.com\u002Ffile\u002F)\n- FigJam boards (figma.com\u002Fboard\u002F) and Slides (figma.com\u002Fslides\u002F) are NOT supported\n\n**Node ID Formats**:\n- URLs use dash format: `node-id=1-541`\n- API uses colon format: `1:541`\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Parse URL | FIGMA_DISCOVER_FIGMA_RESOURCES | figma_url |\n| Get file JSON | FIGMA_GET_FILE_JSON | file_key, ids, depth |\n| Get nodes | FIGMA_GET_FILE_NODES | file_key, ids |\n| Render images | FIGMA_RENDER_IMAGES_OF_FILE_NODES | file_key, ids, format |\n| Download images | FIGMA_DOWNLOAD_FIGMA_IMAGES | file_key, images |\n| Get component | FIGMA_GET_COMPONENT | file_key, node_id |\n| File components | FIGMA_GET_FILE_COMPONENTS | file_key |\n| Component sets | FIGMA_GET_FILE_COMPONENT_SETS | file_key |\n| Design tokens | FIGMA_EXTRACT_DESIGN_TOKENS | file_key |\n| Tokens to Tailwind | FIGMA_DESIGN_TOKENS_TO_TAILWIND | tokens |\n| File comments | FIGMA_GET_COMMENTS_IN_A_FILE | file_key |\n| Add comment | FIGMA_ADD_A_COMMENT_TO_A_FILE | file_key, message |\n| File versions | FIGMA_GET_VERSIONS_OF_A_FILE | file_key |\n| Team projects | FIGMA_GET_PROJECTS_IN_A_TEAM | team_id |\n| Project files | FIGMA_GET_FILES_IN_A_PROJECT | project_id |\n| Team styles | FIGMA_GET_TEAM_STYLES | team_id |\n| File styles | FIGMA_GET_FILE_STYLES | file_key |\n| Image fills | FIGMA_GET_IMAGE_FILLS | file_key |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Figma Automation via Rube MCP\n\nAutomate Figma operations through Composio's Figma toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Figma connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `figma`\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 `figma`\n3. If connection is not ACTIVE, follow the returned auth link to complete Figma auth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Get File Data and Components\n\n**When to use**: User wants to inspect Figma design files or extract component information\n\n**Tool sequence**:\n1. `FIGMA_DISCOVER_FIGMA_RESOURCES` - Extract IDs from Figma URLs [Prerequisite]\n2. `FIGMA_GET_FILE_JSON` - Get file data (simplified by default) [Required]\n3. `FIGMA_GET_FILE_NODES` - Get specific node data [Optional]\n4. `FIGMA_GET_FILE_COMPONENTS` - List published components [Optional]\n5. `FIGMA_GET_FILE_COMPONENT_SETS` - List component sets [Optional]\n\n**Key parameters**:\n- `file_key`: File key from URL (e.g., 'abc123XYZ' from figma.com\u002Fdesign\u002Fabc123XYZ\u002F...)\n- `ids`: Comma-separated node IDs (NOT an array)\n- `depth`: Tree traversal depth (2 for pages and top-level children)\n- `simplify`: True for AI-friendly format (70%+ size reduction)\n\n**Pitfalls**:\n- Only supports Design files; FigJam boards and Slides return 400 errors\n- `ids` must be a comma-separated string, not an array\n- Node IDs may be dash-formatted (1-541) in URLs but need colon format (1:541) for API\n- Broad ids\u002Fdepth can trigger oversized payloads (413); narrow scope or reduce depth\n- Response data may be in `data_preview` instead of `data`\n\n### 2. Export and Render Images\n\n**When to use**: User wants to export design assets as images\n\n**Tool sequence**:\n1. `FIGMA_GET_FILE_JSON` - Find node IDs to export [Prerequisite]\n2. `FIGMA_RENDER_IMAGES_OF_FILE_NODES` - Render nodes as images [Required]\n3. `FIGMA_DOWNLOAD_FIGMA_IMAGES` - Download rendered images [Optional]\n4. `FIGMA_GET_IMAGE_FILLS` - Get image fill URLs [Optional]\n\n**Key parameters**:\n- `file_key`: File key\n- `ids`: Comma-separated node IDs to render\n- `format`: 'png', 'svg', 'jpg', or 'pdf'\n- `scale`: Scale factor (0.01-4.0) for PNG\u002FJPG\n- `images`: Array of {node_id, file_name, format} for downloads\n\n**Pitfalls**:\n- Images return as node_id-to-URL map; some IDs may be null (failed renders)\n- URLs are temporary (valid ~30 days)\n- Images capped at 32 megapixels; larger requests auto-scaled down\n\n### 3. Extract Design Tokens\n\n**When to use**: User wants to extract design tokens for development\n\n**Tool sequence**:\n1. `FIGMA_EXTRACT_DESIGN_TOKENS` - Extract colors, typography, spacing [Required]\n2. `FIGMA_DESIGN_TOKENS_TO_TAILWIND` - Convert to Tailwind config [Optional]\n\n**Key parameters**:\n- `file_key`: File key\n- `include_local_styles`: Include local styles (default true)\n- `include_variables`: Include Figma variables\n- `tokens`: Full tokens object from extraction (for Tailwind conversion)\n\n**Pitfalls**:\n- Tailwind conversion requires the full tokens object including total_tokens and sources\n- Do not strip fields from the extraction response before passing to conversion\n\n### 4. Manage Comments and Versions\n\n**When to use**: User wants to view or add comments, or inspect version history\n\n**Tool sequence**:\n1. `FIGMA_GET_COMMENTS_IN_A_FILE` - List all file comments [Optional]\n2. `FIGMA_ADD_A_COMMENT_TO_A_FILE` - Add a comment [Optional]\n3. `FIGMA_GET_REACTIONS_FOR_A_COMMENT` - Get comment reactions [Optional]\n4. `FIGMA_GET_VERSIONS_OF_A_FILE` - Get version history [Optional]\n\n**Key parameters**:\n- `file_key`: File key\n- `as_md`: Return comments in Markdown format\n- `message`: Comment text\n- `comment_id`: Comment ID for reactions\n\n**Pitfalls**:\n- Comments can be positioned on specific nodes using client_meta\n- Reply comments cannot be nested (only one level of replies)\n\n### 5. Browse Projects and Teams\n\n**When to use**: User wants to list team projects or files\n\n**Tool sequence**:\n1. `FIGMA_GET_PROJECTS_IN_A_TEAM` - List team projects [Optional]\n2. `FIGMA_GET_FILES_IN_A_PROJECT` - List project files [Optional]\n3. `FIGMA_GET_TEAM_STYLES` - List team published styles [Optional]\n\n**Key parameters**:\n- `team_id`: Team ID from URL (figma.com\u002Ffiles\u002Fteam\u002FTEAM_ID\u002F...)\n- `project_id`: Project ID\n\n**Pitfalls**:\n- Team ID cannot be obtained programmatically; extract from Figma URL\n- Only published styles\u002Fcomponents are returned by team endpoints\n\n## Common Patterns\n\n### URL Parsing\n\nExtract IDs from Figma URLs:\n```\n1. Call FIGMA_DISCOVER_FIGMA_RESOURCES with figma_url\n2. Extract file_key, node_id, team_id from response\n3. Convert dash-format node IDs (1-541) to colon format (1:541)\n```\n\n### Node Traversal\n\n```\n1. Call FIGMA_GET_FILE_JSON with depth=2 for overview\n2. Identify target nodes from the response\n3. Call again with specific ids and higher depth for details\n```\n\n## Known Pitfalls\n\n**File Type Support**:\n- GET_FILE_JSON only supports Design files (figma.com\u002Fdesign\u002F or figma.com\u002Ffile\u002F)\n- FigJam boards (figma.com\u002Fboard\u002F) and Slides (figma.com\u002Fslides\u002F) are NOT supported\n\n**Node ID Formats**:\n- URLs use dash format: `node-id=1-541`\n- API uses colon format: `1:541`\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Parse URL | FIGMA_DISCOVER_FIGMA_RESOURCES | figma_url |\n| Get file JSON | FIGMA_GET_FILE_JSON | file_key, ids, depth |\n| Get nodes | FIGMA_GET_FILE_NODES | file_key, ids |\n| Render images | FIGMA_RENDER_IMAGES_OF_FILE_NODES | file_key, ids, format |\n| Download images | FIGMA_DOWNLOAD_FIGMA_IMAGES | file_key, images |\n| Get component | FIGMA_GET_COMPONENT | file_key, node_id |\n| File components | FIGMA_GET_FILE_COMPONENTS | file_key |\n| Component sets | FIGMA_GET_FILE_COMPONENT_SETS | file_key |\n| Design tokens | FIGMA_EXTRACT_DESIGN_TOKENS | file_key |\n| Tokens to Tailwind | FIGMA_DESIGN_TOKENS_TO_TAILWIND | tokens |\n| File comments | FIGMA_GET_COMMENTS_IN_A_FILE | file_key |\n| Add comment | FIGMA_ADD_A_COMMENT_TO_A_FILE | file_key, message |\n| File versions | FIGMA_GET_VERSIONS_OF_A_FILE | file_key |\n| Team projects | FIGMA_GET_PROJECTS_IN_A_TEAM | team_id |\n| Project files | FIGMA_GET_FILES_IN_A_PROJECT | project_id |\n| Team styles | FIGMA_GET_TEAM_STYLES | team_id |\n| File styles | FIGMA_GET_FILE_STYLES | file_key |\n| Image fills | FIGMA_GET_IMAGE_FILLS | file_key |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":55,"source":40,"requires":56,"description":7},"unknown",{"mcp":57},[58],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Ffigma-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":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add reikiplanet\u002Fdaoskills --skill figma-automation",{"tool":73,"command":74},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill figma-automation",{"tool":76,"command":77},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill figma-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Ffigma-automation\u002FSKILL.md",true,[],[82,108,120,135,155,178],{"skillNo":83,"name":84,"nameZh":6,"description":85,"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":88,"publishedAt":50},"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",[],[89,90,91,92,93,94,40,95,96,97,98,99,100,101,102,103,104,105,106,107],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":50},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[115,116,106,117,118,40,96,97,98,92,119,93],"ar","vr ar","interaction","requirements","performance",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":50},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","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",[],[122,127,128,129,130,131,40,132,98,133,134,92],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":50},"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",[],[142,143,144,145,146,40,147,148,149,150,132,151,152,153,154],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":50},"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",[],[162,163,164,165,166,167,168,169,40,98,92,170,93,171,172,173,174,175,176,177],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":50},"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",[],[185,186,187,188,189,190,191,192,175,132,193,194,195,40,196,197,198,172,199,200],"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"]