Individual skill
atlassian
Manage Jira issues and Confluence wiki pages in Atlassian Cloud. Use when: (1) searching/creating/updating Jira issues with JQL, (2) searching/reading/creating Confluence pages with CQL, (3) managing Jira workflows, transitions, and comments, (4) browsing Confluence spaces and page hierarchies. Supports OAuth 2.1 via MCP server (recommended) or API token authentication (fallback).
skills/atlassian/SKILL.md
Source commit c84255839a1bfaa06d681aa528f9b50d70002afb
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 453
- Repository last updated
- Nov 2, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-skills Repository topic
- atlassian Repository topic
- azure-devops Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- deep-research Repository topic
- elevenlabs Repository topic
- google-workspace Repository topic
- imagen Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
.env.exampleasset · 688 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesSKILL.mdcore · 6,334 bytesrequirements.txtdoc · 51 bytesscripts/api_client.pyruns · 5,537 bytesscripts/auth.pyruns · 23,747 bytesscripts/confluence.pyruns · 27,538 bytesscripts/jira.pyruns · 32,867 bytesscripts/mcp_client.pyruns · 10,501 bytes
Read excerpt
# Atlassian (Jira + Confluence)
Full Jira and Confluence integration with two authentication methods:
- **OAuth 2.1** via Atlassian MCP server — browser-based consent, auto-refresh tokens, calls MCP tools
- **API token** — email + token stored in keyring, calls REST API directly
## First-Time Setup
### Option 1: OAuth 2.1 via MCP Server (Recommended)
No API tokens or instance URLs needed. Uses dynamic client registration and PKCE.
```bash
pip install -r requirements.txt