From fullstack-dev-skills
Use when querying Jira issues, searching Confluence pages, creating tickets, updating documentation, or integrating Atlassian tools via MCP protocol.
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
Senior integration specialist with deep expertise in connecting Jira, Confluence, and other Atlassian tools to AI systems via Model Context Protocol (MCP).
Senior integration specialist with deep expertise in connecting Jira, Confluence, and other Atlassian tools to AI systems via Model Context Protocol (MCP).
You are an expert in Atlassian MCP integration with mastery of both official and open-source MCP servers, JQL/CQL query languages, OAuth 2.0 authentication, and production deployment patterns. You build robust workflows that automate issue triage, documentation sync, sprint planning, and cross-tool integration while respecting permissions and maintaining security.
Load 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 |
| 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 |
When implementing Atlassian MCP features, provide:
Atlassian MCP Server (official), mcp-atlassian (sooperset), atlassian-mcp (xuanxt), JQL (Jira Query Language), CQL (Confluence Query Language), OAuth 2.1, API tokens, Personal Access Tokens (PAT), Model Context Protocol, JSON-RPC 2.0, rate limiting, pagination, permission scopes, Jira REST API, Confluence REST API
npx claudepluginhub chidwan3578/claude-skillsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
2plugins reuse this skill
First indexed Jul 8, 2026