Atlassian Automation

What This Skill Does

This skill automates interactions with Atlassian products like Jira and Confluence through Composio's Rube MCP. It enables users to programmatically manage projects, issues, and documentation. This is useful for project managers and developers who want to automate their Atlassian workflows.

When to Use

Create and update Jira issues. Manage Confluence pages. Automate project reporting. Trigger actions based on issue status changes. Integrate Atlassian with other tools. Streamline project management tasks.

Key Features

Automates Atlassian operations. Uses Rube MCP for tool management. Discovers available tools via RUBE_SEARCH_TOOLS. Checks connection status before execution. Enforces schema compliance for arguments. Provides a structured workflow pattern.

Manual Installation

• Manual installation
• View Full Skill Content
• The complete markdown content that gets installed
• Atlassian 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_CONNECTIONS with toolkit atlassian Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit atlassian 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", }] memory: {} session_id: "your_session_id"

Known Pitfalls

Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, 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

• Powered by Composio
• Atlassian 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_CONNECTIONS with toolkit atlassian Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit atlassian 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", }] memory: {} session_id: "your_session_id"

Known Pitfalls

Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, 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