atlassian-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/atlassian-automation --openclawAtlassian Automation via Rube MCP
Automate Atlassian operations through Composio's Atlassian toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/atlassian
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Atlassian connection via
RUBE_MANAGE_CONNECTIONSwith toolkitatlassian - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed ā just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitatlassian - If connection is not ACTIVE, follow the returned auth link to complete setup
- Confirm connection status shows ACTIVE before running any workflows
Tool Discovery
Always discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Atlassian operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
Core Workflow Pattern
Step 1: Discover Available Tools
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Atlassian task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["atlassian"]
session_id: "your_session_id"
Step 3: Execute Tools
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
Known Pitfalls
- Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling
RUBE_SEARCH_TOOLS - Check connection: Verify
RUBE_MANAGE_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, even if empty ({}) - Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
- Pagination: Check responses for pagination tokens and continue fetching until complete
Quick Reference
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Atlassian-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit atlassian |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/atlassian-automation/SKILL.mdView on GitHub Overview
Automates Atlassian operations using Composio's Atlassian toolkit via Rube MCP. It requires an active Rube MCP connection and Atlassian access, and emphasizes always discovering current tool schemas before running workflows.
How This Skill Works
Connect Rube MCP to your Atlassian instance, then call RUBE_SEARCH_TOOLS to discover available tools and their input schemas. Verify the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and the required arguments, including a memory object. This runtime discovery ensures up-to-date schemas and safe, schema-driven execution.
When to Use It
- Automating routine Atlassian tasks (e.g., Jira issue creation, updates, or permissions) using dynamically discovered tools.
- You must ensure current tool schemas by performing tool discovery before execution.
- You want to avoid hardcoding tool slugs or arguments and rely on runtime schemas.
- You need to reuse a session across multiple steps in a workflow and manage session IDs.
- Working with paginated tool responses and needing to fetch all pages via subsequent searches or calls.
Quick Start
- Step 1: Add Rube MCP endpoint to your client config (https://rube.app/mcp).
- Step 2: Verify RUBE_SEARCH_TOOLS responds to ensure tool schemas are current.
- Step 3: Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and arguments, including memory and a session_id.
Best Practices
- Always search for tools first to get current schemas and avoid hardcoding slugs or arguments.
- Check that the Atlassian connection is ACTIVE before executing any tools.
- Use exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
- Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow and handle pagination when tool responses are paginated.
Example Use Cases
- Create Jira issues from a chat or form input using a discovered tool slug and schema.
- Bulk update issue statuses across multiple Jira projects in a single workflow.
- Synchronize Confluence space permissions with Jira groups via automated tooling.
- Validate Atlassian tool configurations and generate alerts for misconfigurations.
- Onboard a new Atlassian project by automating setup steps (repositories, boards, permissions) using runtime-discovered tools.
