From atlassian-sync
Set up Atlassian sync credentials and configuration. Use when user says "configure atlassian", "setup jira sync", or when sync-jira reports missing credentials.
How this skill is triggered — by the user, by Claude, or both
Slash command
/atlassian-sync:configureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interactive setup for Jira and Confluence credentials.
Interactive setup for Jira and Confluence credentials.
Zero external dependencies — only needs Python 3.8+.
Check the project root for existing configuration:
.env file — look for ATLASSIAN_* or JIRA_* variablesIf .env is missing Atlassian credentials, ask the user for:
https://your-domain.atlassian.nethttps://your-domain.atlassian.net/_edge/tenant_infoPROJPROJ (often same as Jira project key)Append credentials to the project's .env file (create if it doesn't exist):
ATLASSIAN_SA_EMAIL=<email>
ATLASSIAN_API_TOKEN=<token>
ATLASSIAN_CLOUD_ID=<cloud_id>
ATLASSIAN_SITE_URL=<site URL>
JIRA_PROJECT_KEY=<project key>
CONFLUENCE_SPACE_KEY=<space key>
JIRA_BOARD_ID=<board ID>
If .env already exists, only add missing variables — never overwrite existing ones.
Test credentials by fetching the Jira project:
python3 "${CLAUDE_PLUGIN_ROOT}/src/atlassian_cli.py" jira boards <JIRA_PROJECT_KEY>
If this succeeds, credentials are working. If it fails, show the error and help debug.
Check if .env is in .gitignore. If not, warn:
"Your
.envfile is not in.gitignore. Add it to prevent committing secrets."
Offer to add .env to .gitignore if approved.
Atlassian Sync configured:
Site: https://your-domain.atlassian.net
Jira: PROJ (board ID: 1)
Confluence: PROJ
Credentials: .env (ATLASSIAN_SA_EMAIL, ATLASSIAN_API_TOKEN)
Ready to sync. Try: /atlassian-sync:sync-jira
npx claudepluginhub 3d-stories/bmad-atlassian-sync --plugin atlassian-syncSets up Jira Cloud integration by verifying credentials, discovering custom fields and projects, and persisting results as version-controlled JSON caches. Idempotent setup command.
Opt-in Atlassian/Jira integration via acli for creating work items, transitioning statuses, adding comments, and linking PRs. Activates when working with Jira, Atlassian, or acli.
Manages Jira issues with JQL, Confluence pages with CQL, sprint workflows, and MCP server authentication for Atlassian API integrations.