atlassian-reader
Installation
SKILL.md
Atlassian Reader
Read-only access to Jira and Confluence via Atlassian Cloud REST APIs using scoped read-only API tokens. All operations use curl with Basic Auth through the Atlassian API gateway (api.atlassian.com). Never create, update, or delete any Atlassian resource.
1. Environment Variables
This skill requires four environment variables. Do not run any verification commands — go straight to the API call. If it fails, consult the error handling section (Section 11) to diagnose the cause and guide the user.
| Variable | Purpose |
|---|---|
ATLASSIAN_CLOUD_ID |
Bitwarden Atlassian Cloud ID (find it at https://bitwarden.atlassian.net/_edge/tenant_info) |
ATLASSIAN_EMAIL |
Email address associated with the Atlassian account |
ATLASSIAN_JIRA_READ_ONLY_TOKEN |
Scoped Jira API token with read permissions only (create one here) |
ATLASSIAN_CONFLUENCE_READ_ONLY_TOKEN |
Scoped Confluence API token with read permissions only (create one here) |
Why two tokens? Atlassian scoped tokens are per-product. A Jira-scoped token cannot access Confluence and vice versa. This enforces least-privilege: each token only has read access to its respective product.