SKILLEMALL.ai

BD strudel-music

Audio deconstruction and composition via Strudel live-coding. Decompose any audio into stems, extract samples, compose with the vocabulary, render offline to WAV/MP3.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 80 files · 3 scripts body ≈ 4 781 tokens Open the sourcegithub.com analyzed 2 d ago

Audio deconstruction and composition via Strudel live-coding.

As a process D 44/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorDiscordGitHubInfrastructureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
95
Quality 40%
74
Run on models
none yet
Process rating
D
44/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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 · 5

✓ No critical or high findings

Medium and low: 5
  • low Secrets in code secret-high-entropy-token package-lock.json:101
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…4wC+Keca…vc6/fddvw/6lg9…Dt9+DkIvjXImQQ==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:110
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…7KL+OVwF…Elx+TiI1/6kcmcEe+g5YR…OvQ==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:148
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…p7K+vRNE…9hg==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:217
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…p7K+vRNE…9hg==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:229
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…dNm+w/2fIz…imP+QNz605/XnjF…qBg==",
    detector

Files scanned: 80. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 44/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (web, python, node) that frontmatter does not declare
  • 70Execution cost. Instruction body is 4781 tokens
  • 85Steps. 45 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 17 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 5 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 166: enough signal without eating the budget
  • +4Structure: 40 headings
  • +3Step-by-step instructions: 45 items
  • +4Has examples (24 code blocks)
  • +4Reference files are cited in the instructions (8 of 19)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.