← 返回 Skills 市场

Kansodata Jira Ops

Name: Kansodata Jira Ops
Author: kansodata

作者 Marcos CF. · GitHub ↗ · v0.1.0 · MIT-0

cross-platform ✓ 安全检测通过

总下载

当前安装

版本数

在 OpenClaw 中安装

/install kansodata-jira-ops

功能描述

Skill operativa read-only para análisis de Jira Cloud con enfoque en contexto, bloqueadores y triage.

使用说明 (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:

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

Modos operativos

1) search_issue_context

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

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

2) summarize_issue

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

get_issue.
get_issue_comments.
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:

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

4) triage_backlog

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

search_issues del backlog objetivo.
Revisar campos clave (priority, status, assignee, labels).
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:

Consolidar issues por objetivo/sprint/proyecto.
Identificar avances, riesgos, bloqueadores.
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.

安全使用建议

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.

功能分析

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.

能力评估

✓ 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.

如何使用

确保已安装 OpenClaw（本地或 Docker 部署）
在对话框中输入安装命令：/install kansodata-jira-ops
安装完成后，直接呼叫该 Skill 的名称或使用 /kansodata-jira-ops 触发
根据 Skill 的参数说明提供必要输入，即可获得结构化输出

版本历史

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

元数据

Slug kansodata-jira-ops

版本 0.1.0

许可证 MIT-0

累计安装 0

当前安装数 0

历史版本数 1

常见问题