AA prompt-transformer
Transform messages that begin with `@prt` or `@prompt` into structured, copy-ready prompts for coding, prototyping, planning, and other build-oriented tasks. Use when a user wants prompt-writing help, wants a natural-language request upgraded into a stronger prompt, wants a short summary of the prompt's key handling, or uses the `@prt` / `@prompt` prefix. Also use to bypass non-target prefixed inputs that are really ordinary chat, simple questions, or casual remarks.
As a process A 81/100 · Runs to the end — weak spots: inputs and preconditions, running it twice, progress reporting
How to improve
- 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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 81/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 70Failures and branches. 6 branches
- 100Tools and files. No external tools needed
- 100Steps. 63 steps
- 100Result and completion. Output format and completion criterion are stated
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1689 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)
- +1No license
- +2Single-language instructions
- +3Description length 471: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 63 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (3 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.