[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RTQVWVG5D87R1HJHGWG2YH":3,"skill-same:01M6RTQVWVG5D87R1HJHGWG2YH":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":13,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M6RTQVWVG5D87R1HJHGWG2YH","content-engine",null,"Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.","sakamoto-family-smile\u002Fagent_monorepo","sakamoto-family-smile","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F132812403?v=4","01M6RTAT3H8PMWX5SJ65KP3VYF","01M6RTAV321WB5RAHCWTZMX5CV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fcontent-engine\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"content","content engine","engine","when","create","for","threads","posts","native","multi","scripts","systems","platform","campaigns","across","social","tiktok","youtube","use","linkedin","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]\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","# 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",{"name":48,"requires":49,"description":52},"figma-automation",{"mcp":50},[51],"rube","Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.","main","fbf4d3f6fb9300cbe74e1bea7d4e177911f3499b",".claude\u002Fskills\u002Fecc\u002Fcontent-engine","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile","2026-11-08 20:29:14",{"source":8,"skillName":48,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add sakamoto-family-smile\u002Fagent_monorepo --skill figma-automation",{"tool":65,"command":66},"bunx","bunx skills add sakamoto-family-smile\u002Fagent_monorepo --skill figma-automation",{"tool":68,"command":69},"pnpm","pnpm dlx skills add sakamoto-family-smile\u002Fagent_monorepo --skill figma-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fcontent-engine\u002FSKILL.md",true,[],[74,108,116,134,157,181],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":88,"publishedAt":43},"01M6RW50THEFSKK42YNR8XFZA1","remotion-video-creation","Best practices for Remotion - Video creation in React. 29 domain-specific rules covering 3D, animations, audio, captions, charts, transitions, and more.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fremotion-video-creation\u002FSKILL.md",[80,85],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":86,"categoryName":87,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000016","图像与多媒体",[89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,28],"Video","remotion video","remotion video creation","creation","Remotion","Charts","Captions","Audio","3D","Composition","Animation","best practices","more","animations","domain-specific","domain","three","Rules","Lottie",{"skillNo":109,"name":110,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":43},"01M6VCJ23NPECPSZJKGY691F75","hotcook-recipes","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fhotcook-agent\u002Fdata\u002Fskills\u002Fhotcook-recipes\u002FSKILL.md",[],[114,115],"hotcook recipes","recipes",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":128,"publishedAt":43},"01M6VCHHE00X5XHSDRD1KH1BW2","code-helper","Code review and assistance skill","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-2\u002Fskills\u002Fcode-helper\u002Fskill.md",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":126,"categoryName":127,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000030","开发工程师",[129,130,131,132,133],"code helper","helper","code","code review","review",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":146,"publishedAt":43},"01M6VCH3Q31A20H6SQ1H0J7JB2","research-assistant","Web research assistant skill using Brave Search MCP","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-1\u002Fskills\u002Fresearch-assistant\u002Fskill.md",[140,143],{"categoryNo":141,"categoryName":142,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":144,"categoryName":145,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000023","Skill与智能体开发",[147,148,149,150,151,152,153,154,155,156],"research assistant","research","assistant","MCP","web","search","brave search","web research","brave","web research assistant",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":167,"publishedAt":43},"01M6VCGZZGPNVJSCZ1JTMNZAHY","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fx-api\u002FSKILL.md",[163,166],{"categoryNo":164,"categoryName":165,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":126,"categoryName":127,"taxonomyType":20,"taxonomyTypeDesc":21},[168,169,170,26,171,172,28,29,173,31,174,35,175,176,177,41,178,179,152,180],"x api","api","with","limits","rate","reading","posting","patterns","api integration","twitter","auth","analytics","OAuth",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":188,"publishedAt":43},"01M6VCGVX6DGB1FKTA53QBBCQB","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fworkspace-surface-audit\u002FSKILL.md",[187],{"categoryNo":144,"categoryName":145,"taxonomyType":83,"taxonomyTypeDesc":84},[189,190,191,192,150,193,194,131,195,196,197,198,41,199,200,201,202,31,203,26],"workspace surface audit","workspace","audit","hooks","workflows","connectors","capabilities","harness","repo","environment","up","harness setup","active","env","value"]