SKILLEMALL.ai
GitHub ↗ RU Sign in

AC File: skills/jira-rest-v3/SKILL.md

Use this skill to perform everyday Jira work from openClaw:

modbender/skill-library-mcp Agent Skills author: modbender MIT 6 files body ≈ 2 638 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Use this skill to perform everyday Jira work from openClaw:

As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency

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
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
57/100
Has gaps
Inputs and preconditions w 11
0
When it triggers w 12
20
Running it twice w 4
30
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 name-format name should be kebab-case (lowercase letters, digits, hyphens)

    Process rating: all ten parameters 57/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 21 mutating operations with no state check
    • 40Consistency. Frontmatter name (File: skills/jira-rest-v3/SKILL.md) differs from the folder (jira-rest-v3)
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 156 steps, 3 vague phrases
    • 100Failures and branches. 1 branches, has a failure section
    • 100Execution cost. Instruction body is 2638 tokens
    • 100Progress reporting. Reports progress
    • low 16 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (3 tags): a typed call is more reliable

    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)
    • +3Description length 59: 120–800 characters recommended
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +4Structure: 52 headings
    • +3Step-by-step instructions: 156 items
    • +3Output format is stated explicitly

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