[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CT3GPBXHC4KKCXEV1PDV8D":3,"skill-same:01M6CT3GPBXHC4KKCXEV1PDV8D":90},{"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":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6CT3GPBXHC4KKCXEV1PDV8D","figma-automation",null,"Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. 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\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],"automation","figma","figma automation","design","MCP","safe","components","tasks","search","Tools","first","automate","design tokens","files","community","composio","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.\"\nrisk: safe\nsource: community\ndate_added: \"2026-02-27\"\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":37,"source":46,"date_added":53,"description":7},"2026-02-27","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Ffigma-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":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill figma-automation",{"tool":68,"command":69},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill figma-automation",{"tool":71,"command":72},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill figma-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Ffigma-automation\u002FSKILL.md",true,[76,82,86],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fchallenge.md","REFERENCE","参考文档",3655,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fplan\u002Freferences\u002Fchallenge.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fground-truth-routing.md",5569,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fplan\u002Freferences\u002Fground-truth-routing.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fresume-and-handoff.md",4314,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fplan\u002Freferences\u002Fresume-and-handoff.md",[91,102,118,136,154,180],{"skillNo":92,"name":93,"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":94,"categories":95,"keywords":99,"publishedAt":48},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[96],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[100,101],"Test Skill","test",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":48},"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",[],[109,110,111,112,113,114,115,46,116,117],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":125,"publishedAt":48},"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",[124],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[32,126,127,42,41,40,36,128,129,43,130,131,132,47,46,133,134,135],"zoom automation","zoom","via","meeting","critical","creation","webinars","recordings","management","tracking",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":48},"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",[142],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[144,32,145,146,147,148,149,46,40,150,47,151,130,43,41,152,116,39,36,153],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","manage",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":163,"publishedAt":48},"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",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[164,165,166,167,168,117,37,169,170,171,172,173,112,174,175,176,177,46,178,179],"expert","zod","zod validation expert","validation","react","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":187,"publishedAt":48},"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",[186],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[188,189,190,191,192,193,194,195,46,196,197,198,199,200,201,202,203,204,205,36],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]