CB issue-create
Create a new ticket/issue with configurable backend (Gitea, GitHub, Jira, Linear, or local files)
Create a new ticket/issue with configurable backend (Gitea, GitHub, Jira, Linear, or local files)
As a process B 76/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting
This is a copy of a skill from another catalog; the rating counts the canonical one: issue-create (jmagly/aiwg)
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securityreferences/examples.md:82Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file; quoted — discussed, not commanded)Create an issue titled "Security audit" with body "Run penetration test on authentication endpoints", assign security-team, add labels "security,high-priority", and set milestone "Q1-2026".
fixturequoted
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "namespace" - note
frontmatter-keyunknown frontmatter key "script" - note
frontmatter-keyunknown frontmatter key "commandHint" - note
edit-residuethe text marks something as outdated (lines 24, 141): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 76/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4351 tokens
- 100Tools and files. No external tools needed
- 100Steps. 79 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
- high The skill tells the model to perform an irreversible action with no human approval
- 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 97: 120–800 characters recommended
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 28 headings
- +3Step-by-step instructions: 79 items
- +3Output format is stated explicitly
- +4Has examples (21 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.