AA linear-ticket-creator
Generate well-structured Linear tickets from bugs, features, and improvements. Explores the codebase to auto-populate technical notes, acceptance criteria, and scope. TRIGGER when: user asks to create a Linear ticket, write a ticket, draft a bug report, or convert a requirement into a ticket. DO NOT TRIGGER when: user is working on code, asking general questions, or managing existing tickets.
As a process A 86/100 · Runs to the end — weak spots: result and completion, progress reporting
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 86/100
- 0Progress reporting. Says nothing while it works
- 40Result and completion. Does not say what the result is
- 60Failures and branches. 2 branches
- 100Tools and files. No external tools needed
- 100Steps. 14 steps
- 100When it triggers. States when to use and when not to
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1323 tokens
- 100Running it twice. No mutating operations
- medium 7 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 395: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.