SKILLEMALL.ai

BB tutorial

Provides interactive guided album creation for new users. Use when the user is new to the plugin or asks for a walkthrough of the album creation process.

bitwize-music-studio/claude-ai-music-skills Claude Code author: bitwize-music-studio 2 files body ≈ 2 247 tokens Open the sourcegithub.com↗ analyzed 9 h ago

Provides interactive guided album creation for new users.

As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice

ProcedureLearningtype and topics are labelled automatically from the skill text
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
95
Quality 40%
83
Run on models
none yet
Process rating
B
65/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Inputs and preconditions w 11
30
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

    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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Read Write Edit Glob Grep Bash AskUserQuestion bitwize-music-mcp

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "effort"

    Process rating: all ten parameters 65/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 30Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 15 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 65 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2247 tokens
    • low 10 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
    • +1No license
    • +2Single-language instructions
    • +3Description length 153: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 65 items
    • +4Has examples (8 code blocks)

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