From fullstack-dev-skills
Manages Jira issues with JQL, Confluence pages with CQL, sprint workflows, and MCP server authentication for Atlassian API integrations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fullstack-dev-skills:atlassian-mcpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Querying Jira issues with JQL filters
maxResults=1 before full executionLoad detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| Server Setup | references/mcp-server-setup.md | Installation, choosing servers, configuration |
| Jira Operations | references/jira-queries.md | JQL syntax, issue CRUD, sprints, boards, issue linking |
| Confluence Ops | references/confluence-operations.md | CQL search, page creation, spaces, comments |
| Authentication | references/authentication-patterns.md | OAuth 2.0, API tokens, permission scopes |
| Common Workflows | references/common-workflows.md | Issue triage, doc sync, sprint automation |
# Open issues assigned to current user in a sprint
project = PROJ AND status = "In Progress" AND assignee = currentUser() ORDER BY priority DESC
# Unresolved bugs created in the last 7 days
project = PROJ AND issuetype = Bug AND status != Done AND created >= -7d ORDER BY created DESC
# Validate before bulk: test with maxResults=1 first
project = PROJ AND sprint in openSprints() AND status = Open ORDER BY created DESC
# Find pages updated in a specific space recently
space = "ENG" AND type = page AND lastModified >= "2024-01-01" ORDER BY lastModified DESC
# Search page text for a keyword
space = "ENG" AND type = page AND text ~ "deployment runbook"
{
"mcpServers": {
"atlassian": {
"command": "npx",
"args": ["-y", "@sooperset/mcp-atlassian"],
"env": {
"JIRA_URL": "https://your-domain.atlassian.net",
"JIRA_EMAIL": "user@example.com",
"JIRA_API_TOKEN": "${JIRA_API_TOKEN}",
"CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
"CONFLUENCE_EMAIL": "user@example.com",
"CONFLUENCE_API_TOKEN": "${CONFLUENCE_API_TOKEN}"
}
}
}
}
Note: Always load
JIRA_API_TOKENandCONFLUENCE_API_TOKENfrom environment variables or a secrets manager — never hardcode credentials.
maxResults=1 probe first)When implementing Atlassian MCP features, provide:
npx claudepluginhub jeffallan/claude-skills --plugin fullstack-dev-skillsInteract with Atlassian Jira and Confluence via REST APIs. Create, edit, search, and transition Jira issues; read and write Confluence pages. No MCP server needed.
Retrieves, analyzes, and updates Jira tickets via MCP or direct REST API. Useful for fetching requirements, transitioning status, adding comments, and linking work items.
Automates Atlassian operations (Jira, Confluence, etc.) via Composio's toolkit through Rube MCP. Always searches for current tool schemas before execution.