Agent skill
atlassian-cli
Use Atlassian CLI (acli) for Jira and Confluence operations. Load this skill when a task mentions Atlassian CLI/acli, Jira command-line workflows, or Confluence command-line workflows.
Install this agent skill to your Project
npx add-skill https://github.com/datwaft/dotfiles/tree/main/.config/opencode/skills/atlassian-cli
Metadata
Additional technical details for this skill
- tool
- acli
- scope
- jira-confluence
SKILL.md
Atlassian CLI (acli)
Use this skill to execute Jira and Confluence workflows through acli without repeatedly discovering command groups via --help.
When to use this skill
- user explicitly mentions
acli, Atlassian CLI, Jira CLI, or Confluence CLI - task involves listing, searching, viewing, or inspecting Jira/Confluence resources
- task involves potentially mutating Atlassian resources and needs safe command selection
Command map (high value paths)
Top-level groups:
acli jira ...acli confluence ...acli admin ...acli auth ...acli config ...
Common Jira paths:
- work items:
acli jira workitem view|search|create|edit|delete|transition|assign|comment ... - boards:
acli jira board search|get|list-sprints|list-projects|create|delete - projects:
acli jira project list|view|create|update|archive|restore|delete - filters:
acli jira filter list|search|get|get-columns|add-favourite|change-owner|update|reset-columns - sprints:
acli jira sprint view|list-workitems|create|update|delete - dashboards:
acli jira dashboard search
Common Confluence paths:
- pages:
acli confluence page view - blogs:
acli confluence blog list|view|create - spaces:
acli confluence space list|view|create|update|archive|restore
Read-only vs mutating model
Use this default classifier unless the user asks otherwise.
- read-only verbs:
view,get,list,search,type,visibility - mutating verbs:
create,update,edit,delete,archive,restore,assign,transition,clone,link create/delete,watcher remove,add-favourite,change-owner,reset-columns
If a command has no obvious verb, inspect the command description before running it.
Output defaults
- prefer
--jsonwhen results may need parsing or summarization - use
--csvonly when user asks for CSV/export behavior - use pagination flags (
--paginate,--limit) intentionally to avoid huge outputs
Safety and execution guidance
- do not run mutating commands unless user intent is explicit
- do not assume online reference pages are complete; local
acli ... --helpmay expose newer commands - for unknown subcommands, run the narrowest help command (for example,
acli jira workitem comment --help) rather than broad top-level help
Practical templates
# Search Jira work items
acli jira workitem search --jql "project = TEAM ORDER BY updated DESC" --limit 20 --json
# View one work item
acli jira workitem view TEAM-123 --json
# List boards
acli jira board search --limit 50 --json
# List sprint issues
acli jira sprint list-workitems --board 6 --sprint 42 --json
# View Confluence page
acli confluence page view --id 123456 --json
References
- Command quick reference: commands-readonly.md
- Atlassian docs intro: https://developer.atlassian.com/cloud/acli/guides/introduction/
- Atlassian command reference index: https://developer.atlassian.com/cloud/acli/reference/commands/
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
jira-cli
Use this skill when the user wants to inspect, search, summarize, or update Jira issues, epics, sprints, boards, projects, releases, or server metadata with the `jira` command-line tool (`jira-cli`, `ankitpokhrel/jira-cli`). Also use it when the prompt mentions Jira issue keys like `ABC-123`, JQL, assignees/reporters, sprint or board queries, release/version lists, or converting Jira's interactive output into script-friendly `--plain`, `--raw`, `--table`, or `-n` commands.
jj-vcs
Use jj (Jujutsu) version control system. Load this skill when the user wants to perform version control operations with jj, or when they explicitly mention jj/jujutsu.
fennel-lang
Expert guidance for Fennel code in all forms. Load this skill whenever a task involves reading, writing, debugging, reviewing, translating, or reasoning about Fennel.
zbench
Benchmark interactive zsh performance with zsh-bench and track regressions. Use when benchmarking shell startup, comparing zsh latency after config changes, investigating slow shell, or running git bisect on performance. Trigger phrases: "benchmark zsh", "shell is slow", "zbench", "zsh-bench", "shell startup time", "profile zsh", "zsh performance".
nix-rebuild
Rebuild nix-darwin/NixOS system after dotfiles changes. Use when config files managed by Nix (lazygit, ghostty, etc.) need to be regenerated, or after editing any .nix file in the dotfiles repo.
hass-config-flow
Interact with Home Assistant via the REST API on a NixOS host. Use when adding integrations, querying entities, managing config flows, creating API tokens, or automating HA setup programmatically. Also covers identifying device protocols (Matter, Zigbee, Thread, HomeKit) from the device registry. Trigger phrases: "add HA integration", "configure home assistant", "query HA entities", "create HA token", "HA REST API", "pair homekit", "set up matter in HA", "add spotify to HA", "is this device zigbee or thread", "what protocol is this device", "move devices to ZHA", "identify matter devices".
Didn't find tool you were looking for?