← Back to Skills Marketplace
temperatio

Jira API (REST + Agile)

by César · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ⚠ suspicious
249
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install jira-api-rest
Description
Automate Jira Cloud by managing worklogs, executing advanced JQL searches, editing/deleting worklogs, handling sprints, and making direct REST API calls.
README (SKILL.md)

Jira API

Usa jira-cli cuando exista el comando (listar issues, ver issue, transiciones, etc.). Usa este skill cuando jira-cli no cubra la operación o necesites una llamada REST directa.

Quick start (scripts)

Script principal (sin dependencias externas):

  • skills/work/jira-api/scripts/jira_api.py

Ejemplos:

  1. Buscar issues por JQL (API nueva):
./skills/work/jira-api/scripts/jira_api.py search-jql "worklogAuthor = currentUser() AND worklogDate >= 2026-03-09 AND worklogDate \x3C= 2026-03-15" --fields key,summary,status --max 100
  1. Listar worklogs de una issue (y filtrar por rango de fechas):
./skills/work/jira-api/scripts/jira_api.py list-worklogs DES-355 --from 2026-03-09 --to 2026-03-15
  1. Borrar un worklog concreto (revertir imputación):
./skills/work/jira-api/scripts/jira_api.py delete-worklog DES-355 29978 --adjustEstimate auto
  1. Actualizar un worklog (tiempo / comentario / started):
./skills/work/jira-api/scripts/jira_api.py update-worklog DES-355 29978 --timeSpent "3h 30m" --comment "Ajuste" --started "2026-03-10 12:00:00" --timezone Europe/Madrid --adjustEstimate auto
  1. Llamada REST genérica (para cubrir lo que falte):
./skills/work/jira-api/scripts/jira_api.py request GET /rest/api/3/myself

Operativa y seguridad

  • Autenticación esperada: API token en ~/.netrc (no pegar tokens en chat).
  • No imprimir respuestas que puedan contener secretos; si necesitas compartir, recorta y elimina cabeceras.
  • Antes de acciones destructivas (DELETE/ediciones masivas): confirmar con César.

Qué NO cubre jira-cli (motivación típica)

  • Borrar/editar worklogs (en nuestro entorno, jira issue worklog solo tiene add).
  • Operaciones REST puntuales que Jira Cloud expone pero el CLI no.
  • Automatizaciones de “revertir”, “mover imputación”, “arreglar estimaciones”.

Sprints / Agile (rápido)

El tablero DES suele ser el 184.

# Ver sprints activos
./skills/work/jira-api/scripts/jira_api.py sprint-list --board 184 --state active

# Ver issues de un sprint
./skills/work/jira-api/scripts/jira_api.py sprint-issues \x3CSPRINT_ID> --fields key,summary,status --max 200

Referencias

  • Notas REST mínimas: references/jira-rest-notes.md (endpoints + ADF).
  • Mapa de endpoints (equivalencias con jira-cli): references/endpoint-map.md.
  • Agile/Sprints: references/agile-sprints.md.
Usage Guidance
This skill is coherent with Jira automation and the Python script implements expected REST calls. However, before installing or running it note that: - The script reads your Jira server/login from ~/.config/.jira/.config.yml and your API token from ~/.netrc. The registry metadata incorrectly states no required config paths — verify and be comfortable with these file accesses. - Use a dedicated Atlassian API token with minimal permissions (not your main account password). Consider creating a token specifically for automation and revoke it if you stop using the skill. - Review the script yourself (it is included) to confirm it only talks to your Jira host and does not transmit data elsewhere — static review shows it uses urllib to contact the server from the config and contains no obfuscated/external download behavior. - For destructive operations (delete/update worklogs) follow the documented human-confirm process and consider testing read-only commands first. - If you want stronger isolation, run the script in a constrained environment (throwaway account, container, or VM) so its access to your real ~/.netrc and Jira is limited.
Capability Analysis
Type: OpenClaw Skill Name: jira-api-rest Version: 0.1.0 The skill provides a Python script (scripts/jira_api.py) for interacting with the Jira Cloud REST API, which includes high-risk capabilities such as reading sensitive credentials from ~/.netrc and performing arbitrary network requests via a generic 'request' command. While these features are plausibly needed for the stated purpose of Jira automation and the code includes safety warnings and manual confirmation instructions in SKILL.md, the broad access to local authentication tokens and the potential for an AI agent to be manipulated into performing unauthorized API actions (e.g., data deletion or configuration changes) meet the threshold for a suspicious classification.
Capability Assessment
ℹ Purpose & Capability
The skill's code and documentation align with its stated purpose (Jira Cloud REST operations: JQL, worklogs, sprints, raw REST). However, the registry metadata claims 'Required config paths: none' while the included script explicitly reads ~/.config/.jira/.config.yml and ~/.netrc to obtain the Jira server, login and API token — a mismatch between declared requirements and actual behavior.
✓ Instruction Scope
SKILL.md instructs the agent to use the script for Jira REST calls and explicitly tells users to authenticate via ~/.netrc and to avoid pasting tokens in chat. The instructions stay within the Jira automation scope and do not request unrelated system data or external endpoints.
✓ Install Mechanism
There is no install spec (instruction-only + bundled script). That is low-risk in that nothing is automatically downloaded or executed from remote sources. The included Python script has no external dependencies and will run locally.
⚠ Credentials
The skill accesses local credential/config files (~/.netrc and ~/.config/.jira/.config.yml) to read your Jira token and server. Access to those files is proportionate to the stated Jira automation purpose, but the metadata did not declare these required config paths or a primary credential — an important omission. The script does not require unrelated environment variables, and there is no evidence it requests unrelated credentials.
✓ Persistence & Privilege
The skill is not always-enabled, does not request elevated platform privileges, and does not modify other skills' configuration. It will act only when invoked.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install jira-api-rest
  3. After installation, invoke the skill by name or use /jira-api-rest
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release: Jira Cloud REST API helper. Covers issues, comments, transitions, assign/link; worklogs add/update/delete; boards/sprints via Agile API; JQL via /search/jql.
Metadata
Slug jira-api-rest
Version 0.1.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Jira API (REST + Agile)?

Automate Jira Cloud by managing worklogs, executing advanced JQL searches, editing/deleting worklogs, handling sprints, and making direct REST API calls. It is an AI Agent Skill for Claude Code / OpenClaw, with 249 downloads so far.

How do I install Jira API (REST + Agile)?

Run "/install jira-api-rest" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Jira API (REST + Agile) free?

Yes, Jira API (REST + Agile) is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Jira API (REST + Agile) support?

Jira API (REST + Agile) is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Jira API (REST + Agile)?

It is built and maintained by César (@temperatio); the current version is v0.1.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments