SKILLEMALL.ai
RU Sign in

AD jira-api

Jira automation via Jira Cloud REST API v3, complementing `jira-cli` when it is missing features (especially edit/delete worklogs, advanced JQL search, bulk inspection, or raw REST calls). Use when you need programmatic Jira operations from this workspace (gruporeacciona.atlassian.net), including: listing/filtering worklogs by date, deleting or updating a specific worklog by id, running JQL via /search/jql, or performing a one-off authenticated REST request.

ClawHub Agent Skills author: César v0.1.0 MIT-0 6 files body ≈ 608 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationJiraOperations and projectstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
81
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Jira automation via Jira Cloud REST API v3, complementing `jira-cl… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value

    Process rating: all ten parameters 46/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 1 mutating operations with no state check
    • 40Consistency. Frontmatter name (jira-api) differs from the folder (jira-api-rest)
    • 100Tools and files. No external tools needed
    • 100Steps. 15 steps
    • 100Execution cost. Instruction body is 608 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 462: enough signal without eating the budget
    • +4Structure: 6 headings
    • +3Step-by-step instructions: 15 items
    • +4Has examples (6 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +3All 1 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.

    External checks

    ClawHub: suspicious
    This Jira helper is mostly transparent, but it gives agents broad Jira account control and a raw authenticated request path without strong guardrails.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026