atlassian-reader
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.
2. Discovery
More from bitwarden/ai-plugins
avoiding-false-positives
Use this skill to validate findings during a code review. For each finding, run the rejection criteria and verification checks. If a finding fails any check, drop it.
50retrospecting
Performs comprehensive analysis of Claude Code sessions, examining git history, conversation logs, code changes, and gathering user feedback to generate actionable retrospective reports with insights for continuous improvement.
49implementing-dapper-queries
Implementing Dapper repository methods and stored procedures for MSSQL at Bitwarden. Use when creating or modifying Dapper repositories, writing stored procedures, or working with MSSQL-specific data access in the server repo.
47classifying-review-findings
Use this skill when categorizing code review findings into severity levels. Apply when determining which emoji and label to use for PR comments, deciding if an issue should be flagged at all, or classifying findings as CRITICAL, IMPORTANT, DEBT, SUGGESTED, or QUESTION.
46posting-review-summary
Use this skill when posting the final summary comment after all inline comments are posted. Apply as the LAST step of code review after all findings are classified and inline comments are complete. Detects context (agent mode sticky comment, GitHub Actions MCP tool, or local file) and routes output accordingly.
44reviewing-claude-config
Reviews Claude configuration files for security, structure, and prompt engineering quality. Use when reviewing changes to CLAUDE.md files (project-level or .claude/), skills (SKILL.md), agents, prompts, commands, or settings. Validates YAML frontmatter, progressive disclosure patterns, token efficiency, and security best practices. Detects critical issues like committed settings.local.json, hardcoded secrets, malformed YAML, broken file references, oversized skill files, and insecure agent tool access.
44