← Back to Skills Marketplace
kansodata

Kansodata Jira Ops

by Marcos CF. · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ✓ Security Clean
64
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install kansodata-jira-ops
Description
Skill operativa read-only para análisis de Jira Cloud con enfoque en contexto, bloqueadores y triage.
README (SKILL.md)

Skill: kansodata-jira-ops

Propósito

Analizar contexto operativo en Jira Cloud con evidencia verificable, sin ejecutar acciones de escritura.

Alcance

Esta skill solo usa tools read-only del plugin Jira:

  • get_issue
  • search_issues
  • get_issue_comments
  • get_issue_worklogs
  • get_project
  • list_projects
  • list_issue_types
  • list_statuses
  • list_transitions

Prohibiciones

  • No inventar datos.
  • No ejecutar writes (crear, editar, comentar, asignar, transicionar).
  • No presentar inferencias como hechos.

Regla de salida obligatoria

Separar siempre:

  1. Hechos observados (evidencia de Jira).
  2. Inferencias (hipótesis razonables).
  3. Datos faltantes / permisos insuficientes.

Modos operativos

1) search_issue_context

Objetivo: reunir contexto de una o varias issues. Pasos mínimos:

  1. Buscar issues con search_issues.
  2. Profundizar con get_issue para las claves críticas.
  3. Agregar comentarios/worklogs si aportan señal.

2) summarize_issue

Objetivo: resumir estado actual de una issue. Pasos mínimos:

  1. get_issue.
  2. get_issue_comments.
  3. get_issue_worklogs. Salida mínima:
  • Resumen factual, riesgos, próximos pasos sugeridos (sin escribir en Jira).

3) analyze_blockers

Objetivo: detectar bloqueadores explícitos e implícitos. Pasos mínimos:

  1. search_issues con JQL orientado a bloqueos.
  2. get_issue en candidatas.
  3. Clasificar bloqueadores por criticidad y dependencia.

4) triage_backlog

Objetivo: priorizar backlog por impacto/urgencia. Pasos mínimos:

  1. search_issues del backlog objetivo.
  2. Revisar campos clave (priority, status, assignee, labels).
  3. Entregar propuesta de triage indicando qué es hecho vs inferencia.

5) prepare_status_update

Objetivo: preparar update de estado para stakeholders sin modificar Jira. Pasos mínimos:

  1. Consolidar issues por objetivo/sprint/proyecto.
  2. Identificar avances, riesgos, bloqueadores.
  3. Producir texto listo para enviar fuera de Jira.

Degradación segura

Si faltan permisos o datos:

  • No forzar conclusiones.
  • Informar exactamente qué endpoint falló y por qué.
  • Entregar alternativa conservadora con datos parciales.

Ejemplos

Ver examples.md en esta misma carpeta.

Usage Guidance
This skill appears internally consistent and low-risk: it only describes read-only Jira queries and asks for no installs or credentials. Before enabling, confirm that the platform's Jira plugin/account used by the agent truly has read-only scope and that audit/logging is enabled. Also consider whether Jira issues might contain sensitive data (PII, secrets) that the agent could surface in outputs; if so, restrict access to appropriate projects or scrub outputs. If you want extra assurance, ask the platform admin to show the OAuth/API token scopes used by the Jira integration.
Capability Analysis
Type: OpenClaw Skill Name: kansodata-jira-ops Version: 0.1.0 The skill bundle 'kansodata-jira-ops' is a set of operational instructions for an AI agent to perform read-only analysis of Jira Cloud data. The documentation (SKILL.md, scope.md, usage-rules.md) explicitly prohibits write operations, data fabrication, and unauthorized inferences, focusing instead on factual reporting and safe degradation in case of permission errors.
Capability Assessment
✓ Purpose & Capability
Name/description (Jira read-only operational analysis) align with SKILL.md: all listed modes use only read-only plugin operations (search_issues, get_issue, comments, worklogs, project/status listing). Nothing requested is outside that scope.
✓ Instruction Scope
Runtime instructions explicitly restrict to read-only plugin tools, prohibit writes and invented data, and require outputs to separate facts/inferences/missing data. Instructions do not ask to read host files, other env vars, or contact external endpoints beyond the Jira plugin.
✓ Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is written to disk or downloaded during install.
ℹ Credentials
The skill declares no required env vars or credentials. This is reasonable for an instruction-only skill that relies on the platform's Jira plugin, but you should verify the platform-provided Jira integration only grants read-only permissions (so the tool cannot escalate to writes).
✓ Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent presence or modify other skills/configs.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install kansodata-jira-ops
  3. After installation, invoke the skill by name or use /kansodata-jira-ops
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial public release of the Jira read-only operational skill for OpenClaw. Included: - search_issue_context - summarize_issue - analyze_blockers - triage_backlog - prepare_status_update Notes: - Read-only only - Jira Cloud focused - No write actions - Designed to work with the @kansodata/kansodata-jira-plugin plugin
Metadata
Slug kansodata-jira-ops
Version 0.1.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Kansodata Jira Ops?

Skill operativa read-only para análisis de Jira Cloud con enfoque en contexto, bloqueadores y triage. It is an AI Agent Skill for Claude Code / OpenClaw, with 64 downloads so far.

How do I install Kansodata Jira Ops?

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

Is Kansodata Jira Ops free?

Yes, Kansodata Jira Ops is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Kansodata Jira Ops support?

Kansodata Jira Ops is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Kansodata Jira Ops?

It is built and maintained by Marcos CF. (@kansodata); 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...
⬇ 463815 · 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.
⬇ 259802 · 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...
⬇ 200680 · 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.
⬇ 191345 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190333 · by oswalpalash

💬 Comments