SKILLEMALL.ai

AF jira

Interact with Atlassian Jira from the terminal: search issues with JQL, view details, create issues, add comments, count matches with fast approximate-count, list projects, discover valid transitions, and change status. Includes a full JQL language reference (functions, operators, history predicates, date expressions, saved filters, performance tuning) plus REST auth/pagination guidance. Use when the user mentions Jira, a ticket key (e.g. PROJ-123), asks about issues, bugs, tasks, projects, or sprint work, or needs to write, debug, or optimize JQL queries. Do not use for GitHub or GitLab issue tracking, Jira site administration, or generic ticketing systems.

magnus919/agent-skills Agent Skills author: magnus919 MIT 10 files · 1 script body ≈ 2 993 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Interact with Atlassian Jira from the terminal: search issues with JQL, view details, create issues, add comments, count matches with fast approximate-count…

As a process F 55/100 · Will not run — References files that are not bundled: scripts/jira

IntegrationJiraGitHubGitLabOperations and projectstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
90
Run on models
none yet
Process rating
F
55/100
Will not run
References files that are not bundled: scripts/jira
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: scripts/jira
  • note edit-residue the text marks something as outdated (lines 17, 142, 143, 175, 198): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: scripts/jira
  • 0Tools and files. 1 referenced file(s) missing: scripts/jira
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 7 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 27 steps
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2993 tokens
  • low 12 top-level sections: this looks like several domains in one skill
  • medium 6 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

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
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 666: enough signal without eating the budget
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 27 items
  • +4Has examples (13 code blocks)
  • +4Reference files are cited in the instructions (6 of 6)
  • +3All 1 scripts are documented
  • +1License stated

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