How do I install the Atlassian Jira By Altf1be skill?

Run npx skillmds@latest add alt-f1-openclaw-openclaw-skill-atlassian-jira/atlassian-jira-by-altf1be in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Atlassian Jira By Altf1be safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Atlassian Jira By Altf1be?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Atlassian Jira By Altf1be free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Atlassian Jira By Altf1be?

ALT-F1-OpenClaw (@alt-f1-openclaw-openclaw-skill-atlassian-jira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Atlassian Jira By Altf1be by alt-f1-openclaw-openclaw-skill-atlassian-jira

Name: Atlassian Jira By Altf1be
Rating: 4.2 (5 reviews)
Author: ALT-F1-OpenClaw

File contents

Jira Cloud by @altf1be

Manage Atlassian Jira Cloud issues, comments, attachments, and workflow transitions via the REST API.

Setup

Get an API token from https://id.atlassian.com/manage-profile/security/api-tokens
Set environment variables (or create .env in {baseDir}):

JIRA_HOST=yourcompany.atlassian.net
JIRA_EMAIL=you@example.com
JIRA_API_TOKEN=your-api-token
JIRA_DEFAULT_PROJECT=PROJ

Install dependencies: cd {baseDir} && npm install

Commands

Issues

# List issues (optionally filter by project, status, assignee)
node {baseDir}/scripts/jira.mjs list --project PROJ --status "In Progress" --assignee "currentUser()"

# Create an issue
node {baseDir}/scripts/jira.mjs create --project PROJ --type Task --summary "Fix login bug" --description "Users can't log in" --priority High

# Read issue details
node {baseDir}/scripts/jira.mjs read --key PROJ-123

# Update issue fields
node {baseDir}/scripts/jira.mjs update --key PROJ-123 --summary "New title" --priority Low

# Delete issue (requires --confirm)
node {baseDir}/scripts/jira.mjs delete --key PROJ-123 --confirm

# Search with JQL
node {baseDir}/scripts/jira.mjs search --jql "project = PROJ AND status = Open ORDER BY created DESC"

Comments

# List comments on an issue
node {baseDir}/scripts/jira.mjs comment-list --key PROJ-123

# Add a comment
node {baseDir}/scripts/jira.mjs comment-add --key PROJ-123 --body "This is ready for review"

# Update a comment
node {baseDir}/scripts/jira.mjs comment-update --key PROJ-123 --comment-id 10001 --body "Updated comment"

# Delete a comment (requires --confirm)
node {baseDir}/scripts/jira.mjs comment-delete --key PROJ-123 --comment-id 10001 --confirm

Attachments

# List attachments on an issue
node {baseDir}/scripts/jira.mjs attachment-list --key PROJ-123

# Upload an attachment
node {baseDir}/scripts/jira.mjs attachment-add --key PROJ-123 --file ./screenshot.png

# Delete an attachment (requires --confirm)
node {baseDir}/scripts/jira.mjs attachment-delete --attachment-id 10001 --confirm

Workflow Transitions

# List available transitions for an issue
node {baseDir}/scripts/jira.mjs transitions --key PROJ-123

# Move issue to a new status (by transition ID or name)
node {baseDir}/scripts/jira.mjs transition --key PROJ-123 --transition-id 31
node {baseDir}/scripts/jira.mjs transition --key PROJ-123 --transition-name "Done"

Dependencies

commander — CLI framework
dotenv — environment variable loading
Node.js built-in fetch (requires Node >= 18)

Security

Email + API token auth (Basic auth via base64 encoding)
No secrets or tokens printed to stdout
All delete operations require explicit --confirm flag
Path traversal prevention for file uploads
Built-in rate limiting with exponential backoff retry
Lazy config validation (only checked when a command runs)

Author

Abdelkrim BOUJRAF — ALT-F1 SRL, Brussels 🇧🇪 X: @altf1be

---name: atlassian-jira-by-altf1bedescription: Atlassian Jira Cloud CRUD skill — manage issues, comments, attachments, workflow transitions, and JQL search via Jira REST API v3 with email + API token auth.---# Jira Cloud by @altf1beManage Atlassian Jira Cloud issues, comments, attachments, and workflow transitions via the REST API.## Setup1. Get an API token from https://id.atlassian.com/manage-profile/security/api-tokens2. Set environment variables (or create `.env` in `{baseDir}`):```JIRA_HOST=yourcompany.atlassian.netJIRA_EMAIL=you@example.comJIRA_API_TOKEN=your-api-tokenJIRA_DEFAULT_PROJECT=PROJ```3. Install dependencies: `cd {baseDir} && npm install`## Commands### Issues```bash# List issues (optionally filter by project, status, assignee)node {baseDir}/scripts/jira.mjs list --project PROJ --status "In Progress" --assignee "currentUser()"# Create an issuenode {baseDir}/scripts/jira.mjs create --project PROJ --type Task --summary "Fix login bug" --description "Users can't log in" --priority High# Read issue detailsnode {baseDir}/scripts/jira.mjs read --key PROJ-123# Update issue fieldsnode {baseDir}/scripts/jira.mjs update --key PROJ-123 --summary "New title" --priority Low# Delete issue (requires --confirm)node {baseDir}/scripts/jira.mjs delete --key PROJ-123 --confirm# Search with JQLnode {baseDir}/scripts/jira.mjs search --jql "project = PROJ AND status = Open ORDER BY created DESC"```### Comments```bash# List comments on an issuenode {baseDir}/scripts/jira.mjs comment-list --key PROJ-123# Add a commentnode {baseDir}/scripts/jira.mjs comment-add --key PROJ-123 --body "This is ready for review"# Update a commentnode {baseDir}/scripts/jira.mjs comment-update --key PROJ-123 --comment-id 10001 --body "Updated comment"# Delete a comment (requires --confirm)node {baseDir}/scripts/jira.mjs comment-delete --key PROJ-123 --comment-id 10001 --confirm```### Attachments```bash# List attachments on an issuenode {baseDir}/scripts/jira.mjs attachment-list --key PROJ-123# Upload an attachmentnode {baseDir}/scripts/jira.mjs attachment-add --key PROJ-123 --file ./screenshot.png# Delete an attachment (requires --confirm)node {baseDir}/scripts/jira.mjs attachment-delete --attachment-id 10001 --confirm```### Workflow Transitions```bash# List available transitions for an issuenode {baseDir}/scripts/jira.mjs transitions --key PROJ-123# Move issue to a new status (by transition ID or name)node {baseDir}/scripts/jira.mjs transition --key PROJ-123 --transition-id 31node {baseDir}/scripts/jira.mjs transition --key PROJ-123 --transition-name "Done"```## Dependencies- `commander` — CLI framework- `dotenv` — environment variable loading- Node.js built-in `fetch` (requires Node >= 18)## Security- Email + API token auth (Basic auth via base64 encoding)- No secrets or tokens printed to stdout- All delete operations require explicit `--confirm` flag- Path traversal prevention for file uploads- Built-in rate limiting with exponential backoff retry- Lazy config validation (only checked when a command runs)## AuthorAbdelkrim BOUJRAF — [ALT-F1 SRL](https://www.alt-f1.be), Brussels 🇧🇪X: [@altf1be](https://x.com/altf1be)

Frequently asked questions

Atlassian Jira By Altf1be