[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-db444cf5-2f2e-4fc6-9613-ebe147f977d6":3,"$f68eCLsZZIoyii_ZNg6rzoaHOjLg2gg_-qSAFmDFIZvw":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"db444cf5-2f2e-4fc6-9613-ebe147f977d6","jira-automation","通过Rube MCP（Composio）自动化Jira任务：问题、项目、冲刺、看板、评论、用户。始终首先搜索当前架构的工具。","cat_prod_automation","mod_productivity","sickn33,productivity","---\nname: jira-automation\ndescription: \"Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\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\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\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,98,851,"2026-05-16 13:24:31",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"效率工具","productivity","mdi-lightning-bolt-outline","文档处理、数据分析、自动化工作流",4,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"自动化","automation","mdi-robot-outline","工作流自动化、批处理",3,101,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"604cb252-9dfd-42cc-8fbe-1c4af9999c76","1.0.0","jira-automation.zip",2904,"uploads\u002Fskills\u002Fdb444cf5-2f2e-4fc6-9613-ebe147f977d6\u002Fjira-automation.zip","8959930c335645d425d01b664452377ec9f8e63fdac834f375df4753dad04326","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":7113}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]