[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RVDKC5VVS0STDQNPWE6XKT":3,"skill-same:01M6RVDKC5VVS0STDQNPWE6XKT":68},{"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":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6RVDKC5VVS0STDQNPWE6XKT","java-coding-standards",null,"Java coding standards for Spring Boot and Quarkus services: naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout. Automatically applies framework-specific conventions.","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\u002Fjava-coding-standards\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"coding standards","java","java coding standards","coding","standards","reactive","boot","framework-specific","for","usage","streams","naming","layout","project","patterns","spring","quarkus","services","spring boot","framework","2026-11-10 10:12:30",false,"---\nname: jira-automation\ndescription: \"Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\n---\n\n# Jira Automation via Rube MCP\n\nAutomate Jira operations through Composio's Jira toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Jira connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\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 `jira`\n3. If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Search and Filter Issues\n\n**When to use**: User wants to find issues using JQL or browse project issues\n\n**Tool sequence**:\n1. `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` - Search with JQL query [Required]\n2. `JIRA_GET_ISSUE` - Get full details of a specific issue [Optional]\n\n**Key parameters**:\n- `jql`: JQL query string (e.g., `project = PROJ AND status = \"In Progress\"`)\n- `maxResults`: Max results per page (default 50, max 100)\n- `startAt`: Pagination offset\n- `fields`: Array of field names to return\n- `issueIdOrKey`: Issue key like 'PROJ-123' for GET_ISSUE\n\n**Pitfalls**:\n- JQL field names are case-sensitive and must match Jira configuration\n- Custom fields use IDs like `customfield_10001`, not display names\n- Results are paginated; check `total` vs `startAt + maxResults` to continue\n\n### 2. Create and Edit Issues\n\n**When to use**: User wants to create new issues or update existing ones\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List projects to find project key [Prerequisite]\n2. `JIRA_GET_FIELDS` - Get available fields and their IDs [Prerequisite]\n3. `JIRA_CREATE_ISSUE` - Create a new issue [Required]\n4. `JIRA_EDIT_ISSUE` - Update fields on an existing issue [Optional]\n5. `JIRA_ASSIGN_ISSUE` - Assign issue to a user [Optional]\n\n**Key parameters**:\n- `project`: Project key (e.g., 'PROJ')\n- `issuetype`: Issue type name (e.g., 'Bug', 'Story', 'Task')\n- `summary`: Issue title\n- `description`: Issue description (Atlassian Document Format or plain text)\n- `issueIdOrKey`: Issue key for edits\n\n**Pitfalls**:\n- Issue types and required fields vary by project; use GET_FIELDS to check\n- Custom fields require exact field IDs, not display names\n- Description may need Atlassian Document Format (ADF) for rich content\n\n### 3. Manage Sprints and Boards\n\n**When to use**: User wants to work with agile boards, sprints, and backlogs\n\n**Tool sequence**:\n1. `JIRA_LIST_BOARDS` - List all boards [Prerequisite]\n2. `JIRA_LIST_SPRINTS` - List sprints for a board [Required]\n3. `JIRA_MOVE_ISSUE_TO_SPRINT` - Move issue to a sprint [Optional]\n4. `JIRA_CREATE_SPRINT` - Create a new sprint [Optional]\n\n**Key parameters**:\n- `boardId`: Board ID from LIST_BOARDS\n- `sprintId`: Sprint ID for move operations\n- `name`: Sprint name for creation\n- `startDate`\u002F`endDate`: Sprint dates in ISO format\n\n**Pitfalls**:\n- Boards and sprints are specific to Jira Software (not Jira Core)\n- Only one sprint can be active at a time per board\n\n### 4. Manage Comments\n\n**When to use**: User wants to add or view comments on issues\n\n**Tool sequence**:\n1. `JIRA_LIST_ISSUE_COMMENTS` - List existing comments [Optional]\n2. `JIRA_ADD_COMMENT` - Add a comment to an issue [Required]\n\n**Key parameters**:\n- `issueIdOrKey`: Issue key like 'PROJ-123'\n- `body`: Comment body (supports ADF for rich text)\n\n**Pitfalls**:\n- Comments support ADF (Atlassian Document Format) for formatting\n- Mentions use account IDs, not usernames\n\n### 5. Manage Projects and Users\n\n**When to use**: User wants to list projects, find users, or manage project roles\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List all projects [Optional]\n2. `JIRA_GET_PROJECT` - Get project details [Optional]\n3. `JIRA_FIND_USERS` \u002F `JIRA_GET_ALL_USERS` - Search for users [Optional]\n4. `JIRA_GET_PROJECT_ROLES` - List project roles [Optional]\n5. `JIRA_ADD_USERS_TO_PROJECT_ROLE` - Add user to role [Optional]\n\n**Key parameters**:\n- `projectIdOrKey`: Project key\n- `query`: Search text for FIND_USERS\n- `roleId`: Role ID for role operations\n\n**Pitfalls**:\n- User operations use account IDs (not email or display name)\n- Project roles differ from global permissions\n\n## Common Patterns\n\n### JQL Syntax\n\n**Common operators**:\n- `project = \"PROJ\"` - Filter by project\n- `status = \"In Progress\"` - Filter by status\n- `assignee = currentUser()` - Current user's issues\n- `created >= -7d` - Created in last 7 days\n- `labels = \"bug\"` - Filter by label\n- `priority = High` - Filter by priority\n- `ORDER BY created DESC` - Sort results\n\n**Combinators**:\n- `AND` - Both conditions\n- `OR` - Either condition\n- `NOT` - Negate condition\n\n### Pagination\n\n- Use `startAt` and `maxResults` parameters\n- Check `total` in response to determine remaining pages\n- Continue until `startAt + maxResults >= total`\n\n## Known Pitfalls\n\n**Field Names**:\n- Custom fields use IDs like `customfield_10001`\n- Use JIRA_GET_FIELDS to discover field IDs and names\n- Field names in JQL may differ from API field names\n\n**Authentication**:\n- Jira Cloud uses account IDs, not usernames\n- Site URL must be configured correctly in the connection\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Search issues (JQL) | JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST | jql, maxResults |\n| Get issue | JIRA_GET_ISSUE | issueIdOrKey |\n| Create issue | JIRA_CREATE_ISSUE | project, issuetype, summary |\n| Edit issue | JIRA_EDIT_ISSUE | issueIdOrKey, fields |\n| Assign issue | JIRA_ASSIGN_ISSUE | issueIdOrKey, accountId |\n| Add comment | JIRA_ADD_COMMENT | issueIdOrKey, body |\n| List comments | JIRA_LIST_ISSUE_COMMENTS | issueIdOrKey |\n| List projects | JIRA_GET_ALL_PROJECTS | (none) |\n| Get project | JIRA_GET_PROJECT | projectIdOrKey |\n| List boards | JIRA_LIST_BOARDS | (none) |\n| List sprints | JIRA_LIST_SPRINTS | boardId |\n| Move to sprint | JIRA_MOVE_ISSUE_TO_SPRINT | sprintId, issues |\n| Create sprint | JIRA_CREATE_SPRINT | name, boardId |\n| Find users | JIRA_FIND_USERS | query |\n| Get fields | JIRA_GET_FIELDS | (none) |\n| List filters | JIRA_LIST_FILTERS | (none) |\n| Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey |\n| Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey |\n","# Jira Automation via Rube MCP\n\nAutomate Jira operations through Composio's Jira toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Jira connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\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 `jira`\n3. If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Search and Filter Issues\n\n**When to use**: User wants to find issues using JQL or browse project issues\n\n**Tool sequence**:\n1. `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` - Search with JQL query [Required]\n2. `JIRA_GET_ISSUE` - Get full details of a specific issue [Optional]\n\n**Key parameters**:\n- `jql`: JQL query string (e.g., `project = PROJ AND status = \"In Progress\"`)\n- `maxResults`: Max results per page (default 50, max 100)\n- `startAt`: Pagination offset\n- `fields`: Array of field names to return\n- `issueIdOrKey`: Issue key like 'PROJ-123' for GET_ISSUE\n\n**Pitfalls**:\n- JQL field names are case-sensitive and must match Jira configuration\n- Custom fields use IDs like `customfield_10001`, not display names\n- Results are paginated; check `total` vs `startAt + maxResults` to continue\n\n### 2. Create and Edit Issues\n\n**When to use**: User wants to create new issues or update existing ones\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List projects to find project key [Prerequisite]\n2. `JIRA_GET_FIELDS` - Get available fields and their IDs [Prerequisite]\n3. `JIRA_CREATE_ISSUE` - Create a new issue [Required]\n4. `JIRA_EDIT_ISSUE` - Update fields on an existing issue [Optional]\n5. `JIRA_ASSIGN_ISSUE` - Assign issue to a user [Optional]\n\n**Key parameters**:\n- `project`: Project key (e.g., 'PROJ')\n- `issuetype`: Issue type name (e.g., 'Bug', 'Story', 'Task')\n- `summary`: Issue title\n- `description`: Issue description (Atlassian Document Format or plain text)\n- `issueIdOrKey`: Issue key for edits\n\n**Pitfalls**:\n- Issue types and required fields vary by project; use GET_FIELDS to check\n- Custom fields require exact field IDs, not display names\n- Description may need Atlassian Document Format (ADF) for rich content\n\n### 3. Manage Sprints and Boards\n\n**When to use**: User wants to work with agile boards, sprints, and backlogs\n\n**Tool sequence**:\n1. `JIRA_LIST_BOARDS` - List all boards [Prerequisite]\n2. `JIRA_LIST_SPRINTS` - List sprints for a board [Required]\n3. `JIRA_MOVE_ISSUE_TO_SPRINT` - Move issue to a sprint [Optional]\n4. `JIRA_CREATE_SPRINT` - Create a new sprint [Optional]\n\n**Key parameters**:\n- `boardId`: Board ID from LIST_BOARDS\n- `sprintId`: Sprint ID for move operations\n- `name`: Sprint name for creation\n- `startDate`\u002F`endDate`: Sprint dates in ISO format\n\n**Pitfalls**:\n- Boards and sprints are specific to Jira Software (not Jira Core)\n- Only one sprint can be active at a time per board\n\n### 4. Manage Comments\n\n**When to use**: User wants to add or view comments on issues\n\n**Tool sequence**:\n1. `JIRA_LIST_ISSUE_COMMENTS` - List existing comments [Optional]\n2. `JIRA_ADD_COMMENT` - Add a comment to an issue [Required]\n\n**Key parameters**:\n- `issueIdOrKey`: Issue key like 'PROJ-123'\n- `body`: Comment body (supports ADF for rich text)\n\n**Pitfalls**:\n- Comments support ADF (Atlassian Document Format) for formatting\n- Mentions use account IDs, not usernames\n\n### 5. Manage Projects and Users\n\n**When to use**: User wants to list projects, find users, or manage project roles\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List all projects [Optional]\n2. `JIRA_GET_PROJECT` - Get project details [Optional]\n3. `JIRA_FIND_USERS` \u002F `JIRA_GET_ALL_USERS` - Search for users [Optional]\n4. `JIRA_GET_PROJECT_ROLES` - List project roles [Optional]\n5. `JIRA_ADD_USERS_TO_PROJECT_ROLE` - Add user to role [Optional]\n\n**Key parameters**:\n- `projectIdOrKey`: Project key\n- `query`: Search text for FIND_USERS\n- `roleId`: Role ID for role operations\n\n**Pitfalls**:\n- User operations use account IDs (not email or display name)\n- Project roles differ from global permissions\n\n## Common Patterns\n\n### JQL Syntax\n\n**Common operators**:\n- `project = \"PROJ\"` - Filter by project\n- `status = \"In Progress\"` - Filter by status\n- `assignee = currentUser()` - Current user's issues\n- `created >= -7d` - Created in last 7 days\n- `labels = \"bug\"` - Filter by label\n- `priority = High` - Filter by priority\n- `ORDER BY created DESC` - Sort results\n\n**Combinators**:\n- `AND` - Both conditions\n- `OR` - Either condition\n- `NOT` - Negate condition\n\n### Pagination\n\n- Use `startAt` and `maxResults` parameters\n- Check `total` in response to determine remaining pages\n- Continue until `startAt + maxResults >= total`\n\n## Known Pitfalls\n\n**Field Names**:\n- Custom fields use IDs like `customfield_10001`\n- Use JIRA_GET_FIELDS to discover field IDs and names\n- Field names in JQL may differ from API field names\n\n**Authentication**:\n- Jira Cloud uses account IDs, not usernames\n- Site URL must be configured correctly in the connection\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Search issues (JQL) | JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST | jql, maxResults |\n| Get issue | JIRA_GET_ISSUE | issueIdOrKey |\n| Create issue | JIRA_CREATE_ISSUE | project, issuetype, summary |\n| Edit issue | JIRA_EDIT_ISSUE | issueIdOrKey, fields |\n| Assign issue | JIRA_ASSIGN_ISSUE | issueIdOrKey, accountId |\n| Add comment | JIRA_ADD_COMMENT | issueIdOrKey, body |\n| List comments | JIRA_LIST_ISSUE_COMMENTS | issueIdOrKey |\n| List projects | JIRA_GET_ALL_PROJECTS | (none) |\n| Get project | JIRA_GET_PROJECT | projectIdOrKey |\n| List boards | JIRA_LIST_BOARDS | (none) |\n| List sprints | JIRA_LIST_SPRINTS | boardId |\n| Move to sprint | JIRA_MOVE_ISSUE_TO_SPRINT | sprintId, issues |\n| Create sprint | JIRA_CREATE_SPRINT | name, boardId |\n| Find users | JIRA_FIND_USERS | query |\n| Get fields | JIRA_GET_FIELDS | (none) |\n| List filters | JIRA_LIST_FILTERS | (none) |\n| Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey |\n| Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey |\n",{"name":43,"requires":44,"description":47},"jira-automation",{"mcp":45},[46],"rube","Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.","main","fbf4d3f6fb9300cbe74e1bea7d4e177911f3499b",".claude\u002Fskills\u002Fecc\u002Fjava-coding-standards","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":43,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add sakamoto-family-smile\u002Fagent_monorepo --skill jira-automation",{"tool":60,"command":61},"bunx","bunx skills add sakamoto-family-smile\u002Fagent_monorepo --skill jira-automation",{"tool":63,"command":64},"pnpm","pnpm dlx skills add sakamoto-family-smile\u002Fagent_monorepo --skill jira-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fjava-coding-standards\u002FSKILL.md",true,[],[69,103,111,131,154,182],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":83,"publishedAt":38},"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",[75,80],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":81,"categoryName":82,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000016","图像与多媒体",[84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,26],"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":104,"name":105,"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":106,"categories":107,"keywords":108,"publishedAt":38},"01M6VCJ23NPECPSZJKGY691F75","hotcook-recipes","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fhotcook-agent\u002Fdata\u002Fskills\u002Fhotcook-recipes\u002FSKILL.md",[],[109,110],"hotcook recipes","recipes",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":125,"publishedAt":38},"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",[117,120],{"categoryNo":118,"categoryName":119,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[126,127,128,129,130],"code helper","helper","code","code review","review",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":143,"publishedAt":38},"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",[137,140],{"categoryNo":138,"categoryName":139,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":141,"categoryName":142,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发",[144,145,146,147,148,149,150,151,152,153],"research assistant","research","assistant","MCP","web","search","brave search","web research","brave","web research assistant",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":164,"publishedAt":38},"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",[160,163],{"categoryNo":161,"categoryName":162,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},[165,166,167,168,169,170,26,171,172,173,174,175,32,176,177,178,179,180,149,181],"x api","api","with","when","limits","rate","threads","reading","native","posting","platform","api integration","twitter","use","auth","analytics","OAuth",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":189,"publishedAt":38},"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",[188],{"categoryNo":141,"categoryName":142,"taxonomyType":78,"taxonomyTypeDesc":79},[190,191,192,193,147,194,195,128,196,197,198,199,178,200,201,202,203,173,204,168],"workspace surface audit","workspace","audit","hooks","workflows","connectors","capabilities","harness","repo","environment","up","harness setup","active","env","value"]