Skip to main content
ClaudeWave
ES, Spanish
Skill77.7k estrellas del repoactualizado 1mo ago

atlassian-automation

This Claude Code skill enables automated Atlassian operations through Composio's toolkit via Rube MCP, allowing users to programmatically manage Jira, Confluence, and other Atlassian products. Use this skill when you need to automate tasks like creating issues, updating projects, managing workflows, or querying Atlassian data without manual intervention, provided Rube MCP is connected and an active Atlassian connection exists.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/ComposioHQ/awesome-claude-skills /tmp/atlassian-automation && cp -r /tmp/atlassian-automation/composio-skills/atlassian-automation ~/.claude/skills/atlassian-automation
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Atlassian Automation via Rube MCP

Automate Atlassian operations through Composio's Atlassian toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/atlassian](https://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

**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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `atlassian`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_CONNECTIONS` shows ACTIVE status before executing tools
- **Schema compliance**: Use exact field names and types from the search results
- **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

| 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](https://composio.dev)*