Atlassian Jira Cloud
OpenClaw skill for Atlassian Jira Cloud — CRUD issues, comments, attachments, workflow transitions, and JQL search via Jira REST API v3 with email + API token auth.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
// README
openclaw-skill-atlassian-jira
OpenClaw skill for Atlassian Jira Cloud — CRUD issues, comments, attachments, workflow transitions, and JQL search via Jira REST API v3.
By Abdelkrim BOUJRAF / ALT-F1 SRL, Brussels 🇧🇪 🇲🇦
Table of Contents
Features
- Issues — Create, read, update, delete, list, and search (JQL)
- Comments — Add, update, delete, and list
- Attachments — Upload, list, and delete
- Workflow Transitions — List available transitions and move issues through workflow states
- Security —
--confirmrequired for deletes, no secrets to stdout, rate-limit retry with backoff - Auth — Email + API token (Basic auth)
Quick Start
# 1. Clone
git clone https://github.com/ALT-F1-OpenClaw/openclaw-skill-atlassian-jira.git
cd openclaw-skill-atlassian-jira
# 2. Install
npm install
# 3. Configure
cp .env.example .env
# Edit .env with your Jira Cloud credentials
# 4. Use
node scripts/jira.mjs list --project PROJ
node scripts/jira.mjs create --project PROJ --summary "My first issue"
node scripts/jira.mjs read --key PROJ-1
Setup
- Go to https://id.atlassian.com/manage-profile/security/api-tokens
- Create an API token
- Copy
.env.exampleto.envand fill in:JIRA_HOST— your Jira Cloud instance (e.g.yourcompany.atlassian.net)JIRA_EMAIL— your Atlassian account emailJIRA_API_TOKEN— the API token you just createdJIRA_DEFAULT_PROJECT— (optional) default project key
Commands
See SKILL.md for full command reference.
Security
- Email + API token auth (Basic auth via base64 encoding)
- No secrets or tokens printed to stdout
- All delete operations require explicit
--confirmflag - Built-in rate limiting with exponential backoff retry
- Lazy config validation (only checked when a command runs)
ClawHub
Published as: atlassian-jira-by-altf1be
clawhub install atlassian-jira-by-altf1be
License
MIT — see LICENSE
Author
Abdelkrim BOUJRAF — ALT-F1 SRL, Brussels 🇧🇪 🇲🇦
- GitHub: @abdelkrim
- X: @altf1be
Contributing
Contributions welcome! Please open an issue or PR.
// HOW IT'S BUILT
TECHNOLOGY STACK
This skill is built with Node.js. The repo includes a Node.js package.
// FILES
4 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
SKILL.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
package.jsonupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
scriptsupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/atlassian-jira-by-altf1be.md