atlassian-usage
Atlassian CLI Usage
This skill provides guidance for using the atl CLI tool to interact with Jira and Confluence.
CRITICAL: Handling Atlassian URLs
NEVER attempt to fetch Atlassian URLs directly via web tools. Atlassian Cloud requires authentication that web fetch tools cannot provide. Instead, extract identifiers from URLs and use the atl CLI.
Jira URL Patterns
When a user provides a Jira URL, extract the relevant identifier and use atl:
| URL Pattern | Extract | Command |
|---|---|---|
https://*.atlassian.net/jira/software/projects/PROJ/boards/123 |
PROJ |
atl jira search-jql "project = PROJ" |
https://*.atlassian.net/jira/core/projects/PROJ/board |
PROJ |
atl jira search-jql "project = PROJ" |
Examples:
https://example.atlassian.net/jira/software/projects/PROJ/boards/5→atl jira search-jql "project = PROJ"
Confluence URL Patterns
When a user provides a Confluence URL, extract the page ID and use atl:
| URL Pattern | Extract | Command |
|---|---|---|
https://*.atlassian.net/wiki/spaces/SPACE/pages/123456789/Page+Title |
123456789 |
atl confluence get-page 123456789 |
https://*.atlassian.net/wiki/spaces/SPACE/overview |
SPACE |
atl confluence get-pages-in-space SPACE |
Examples:
https://example.atlassian.net/wiki/spaces/ENG/pages/987654321/Architecture→atl confluence get-page 987654321https://example.atlassian.net/wiki/spaces/TEAM/pages/123456789→atl confluence get-page 123456789
URL Recognition Rules
- Any URL containing
.atlassian.netshould trigger this skill - NEVER use WebFetch or similar tools on Atlassian URLs
- Extract the identifier (issue key or page ID) from the URL
- Use the appropriate
atlcommand to retrieve the content
Overview
The atl CLI provides direct access to Jira and Confluence through their REST APIs. Use it for searching, reading, creating, and updating content in Atlassian products.
Discovering Commands
The atl CLI is actively developed and may have commands not covered in this skill. Always use --help to discover available commands and options:
atl --help
atl jira --help
atl confluence --help
atl jira <command> --help
Jira Operations
Searching Issues (JQL)
Search using Jira Query Language:
atl jira search-jql "project = PROJ AND status = 'In Progress'"
atl jira search-jql "assignee = currentUser() AND created >= -7d"
atl jira search-jql "text ~ 'keyword'" --max-results 20 --json
For detailed JQL syntax, see references/jql-reference.md.
Reading Issues
atl jira get-issue PROJ-123
atl jira get-issue PROJ-123 --json
atl jira get-issue PROJ-123 --fields summary,status,assignee
Creating Issues
atl jira create-issue --project PROJ --type Task --summary "Issue title"
atl jira create-issue --project PROJ --type Bug --summary "Bug title" \
--description "**Details:** markdown supported"
The --description flag supports markdown formatting including headings, bold, italic, code blocks, and lists.
Updating Issues
atl jira edit-issue PROJ-123 --summary "New title"
atl jira edit-issue PROJ-123 --description "Updated description"
atl jira edit-issue PROJ-123 --assignee <account-id>
To find account IDs:
atl jira lookup-account-id "username or email"
Comments
atl jira add-comment PROJ-123 "Comment text with **markdown**"
Transitions
atl jira get-transitions PROJ-123
atl jira transition-issue PROJ-123 --transition "In Progress"
Issue Links
atl jira get-link-types
atl jira create-issue-link --inward PROJ-123 --outward PROJ-456 --type "Blocks"
atl jira get-issue-links PROJ-123
Project Information
atl jira get-projects
atl jira get-project-issue-types PROJ
atl jira get-create-meta --project PROJ --issue-type Task
Confluence Operations
Searching Pages (CQL)
Search using Confluence Query Language:
atl confluence search-cql "space = TEAM AND type = page"
atl confluence search-cql "title ~ 'Onboarding'"
atl confluence search-cql "text ~ 'documentation'" --limit 20 --json
For detailed CQL syntax, see references/cql-reference.md.
Reading Pages
Page IDs are numeric values found in page URLs or search results:
atl confluence get-page 123456789
atl confluence get-page 123456789 --json
Creating Pages
atl confluence create-page --space TEAM --title "Page Title" --body "Content"
Updating Pages
atl confluence update-page 123456789 --title "New Title"
atl confluence update-page 123456789 --body "Updated content"
Comments
atl confluence get-page-comments 123456789
atl confluence add-comment 123456789 "Comment text"
atl confluence create-inline-comment 123456789 --body "Inline comment"
Navigation
atl confluence get-spaces
atl confluence get-pages-in-space TEAM
atl confluence get-page-ancestors 123456789
atl confluence get-page-descendants 123456789
Output Formats
Most commands support --json for machine-readable output:
atl jira get-issue PROJ-123 --json | jq '.fields.status.name'
atl jira search-jql "project = PROJ" --json | jq '.[].key'
Common Workflows
Research a Topic
-
Search Jira for relevant tickets:
atl jira search-jql "project = PROJ AND text ~ 'topic'" -
Read promising tickets:
atl jira get-issue PROJ-123 -
Search Confluence for documentation:
atl confluence search-cql "text ~ 'topic'" -
Read relevant pages:
atl confluence get-page 123456789
Create and Track Work
-
Create the issue:
atl jira create-issue --project PROJ --type Task --summary "Task name" \ --description "Details here" -
Transition to in progress:
atl jira transition-issue PROJ-123 --transition "In Progress" -
Add updates as comments:
atl jira add-comment PROJ-123 "Progress update"
Authentication
Verify authentication status:
atl meta user-info
If not authenticated or authentication has expired:
atl auth
Additional Resources
Reference Files
For detailed query syntax, consult:
references/jql-reference.md- Complete JQL syntax, fields, operators, and functionsreferences/cql-reference.md- Complete CQL syntax for Confluence searches
Discovering New Features
The CLI is actively developed. To discover commands not covered here:
atl --help
atl jira --help
atl confluence --help
atl <product> <command> --help
More from dhughes/claude-marketplace
ci-monitor
This skill should be used when the user asks to "monitor the PR", "watch the CI", "check if CI passes", "let me know when CI finishes", "watch the checks", "monitor CI status", "tell me when the build completes", or any variation requesting to track GitHub PR check status until completion. Also use this skill proactively after creating or updating a PR when the user would benefit from knowing the CI result.
9ezcater-research
This skill should be used when the user asks to "investigate ezCater systems", "research architectural decisions", "understand code evolution", "find historical context", "analyze project history", "search internal documentation", or needs to understand why technical decisions were made at ezCater. Use this for lighter research where the user doesn't explicitly request "deep research" (which triggers the agent).
5whats-new
This skill should be used when the user asks about new features, recent changes, or updates in Claude Code — for example "what's new in Claude Code?", "Claude Code changelog", "what did I miss in Claude?", "any recent updates?", "tell me about new Claude features", or "what's changed since version 1.0.30?". It fetches the official changelog, filters for notable features (excluding bug fixes), researches each feature for deeper context on Anthropic's website, and presents mini-article summaries. Supports both automatic tracking (since last check) and explicit version queries.
5configure
Use when user asks "what statusline components are available", "list statusline components", "show statusline components", "which statusline components", "configure statusline", "enable/disable statusline components", "change statusline order", or wants to manage statusline component configuration globally or per-project
5gcb-monitor
This skill should be used when the user asks about build status in GCP, Google Cloud Build, or gcloud builds. Trigger phrases include "monitor the build", "watch the build", "check build status", "build in test environment", "build in staging", "build in production", "status of the build", "gcloud builds", "Cloud Build", "GCP build", "what happened with the build", "why did the build fail", "analyze the build failure", "did the build succeed", "check the deploy", "monitor the deploy", "anything weird with the build", or when user mentions checking CI/CD status in Google Cloud. Also use when user wants to use gcloud CLI to check build results or logs. Use proactively after merging a PR when build monitoring would be helpful.
5pr-creation
This skill should be used when you need to create, open, or edit a pull request (PR), or the user asks to "create a PR", "open a PR", "submit a PR", "raise a PR", "file a PR", "make a PR", "create a pull request", "open a pull request", "new PR", or any variation requesting GitHub pull request creation.
5