BF music-craft
Generate songs, instrumentals, or lyrics-driven tracks through a structured OpenClaw-native workflow with anti-sparse prompt engineering and quality verification. Provider-agnostic — works with any music backend the runtime exposes (ACE-Step, MusicGen, Stable Audio, mmx).
Generate songs, instrumentals, or lyrics-driven tracks through a structured OpenClaw-native workflow with anti-sparse prompt engineering and quality…
As a process F 66/100 · Will not run — References files that are not bundled: /Users/luis/Repos/skills/publish/LOCAL-MODELS-INSTALL-GUIDE.md, ../music-craft-minimax/scripts/lint_music_request.py, ../music-craft-minimax/references/emotion-delivery.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostreferences/windows-wsl-setup.md:100Pipe-to-shell installer from a well-known host (still executes remote code)curl -LsSf https://astral.sh/uv/install.sh | sh
Files scanned: 35. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 9887 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: /Users/luis/Repos/skills/publish/LOCAL-MODELS-INSTALL-GUIDE.md - warning
missing-refreference to a missing file: ../music-craft-minimax/scripts/lint_music_request.py - warning
missing-refreference to a missing file: ../music-craft-minimax/references/emotion-delivery.md - warning
missing-refreference to a missing file: scripts/lint_music_request.py
Process rating: all ten parameters 66/100
- 0Tools and files. 4 referenced file(s) missing: /Users/luis/Repos/skills/publish/LOCAL-MODELS-INSTALL-GUIDE.md, ../music-craft-minimax/scripts/lint_music_request.py, ../music-craft-minimax/references/emotion-delivery.md
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 18 mutating operations with no state check
- 40Execution cost. Instruction body is 9887 tokens: crowds the task out of the window
- 85Steps. 139 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 20 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 26 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)
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 272: enough signal without eating the budget
- +4Structure: 44 headings
- +3Step-by-step instructions: 139 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (25 of 26)
- +3All 6 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.