Kansodata Jira Ops

v0.1.0

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

0· 20·0 current·0 all-time
byMarcos CF.@kansodata
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
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.
Assessment
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.

Like a lobster shell, security has layers — review code before you run it.

jiravk979dfm000cj6f52wf7b2eds9h8505qglatestvk979dfm000cj6f52wf7b2eds9h8505qgopenclawvk979dfm000cj6f52wf7b2eds9h8505qgoperationsvk979dfm000cj6f52wf7b2eds9h8505qgread-onlyvk979dfm000cj6f52wf7b2eds9h8505qgtriagevk979dfm000cj6f52wf7b2eds9h8505qg

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments