AB music-composer
Use when the user asks to write, compose, make, or generate a song as an actual MIDI/instrumental artifact rather than lyrics or a Suno prompt. Creates original MIDI songs, melodies, chord progressions, website music, game music, ambient loops, and short title-based compositions.
As a process B 70/100 · Nearly there — weak spots: inputs and preconditions, consistency, running it twice
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 280 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
Process rating: all ten parameters 70/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Consistency. Frontmatter name (music-composer) differs from the folder (midi-music-composer)
- 30Running it twice. 3 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 5 branches
- 100Tools and files. No external tools needed
- 100Steps. 71 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 2836 tokens
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
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
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 280: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 71 items
- +3Output format is stated explicitly
- +4Has examples (17 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 6 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.