AC musicbrainz_importer
Look up and add music metadata on MusicBrainz. Use when asked to check if an artist, album, or release exists on MusicBrainz, find MusicBrainz entries linked to Spotify URLs, or add/edit releases, artists, or other entities on MusicBrainz. Triggers on mentions of MusicBrainz, MB, music database, adding releases, music metadata, or linking Spotify to MusicBrainz.
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (musicbrainz_importer) differs from the folder (musicbrainz-importer)
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Execution cost. Instruction body is 4598 tokens
- 85Steps. 20 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -31 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 364: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (1 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.