SKILLEMALL.ai
GitHub ↗ RU Sign in

AB promote-idea

Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".

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

Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or…

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

GeneratorAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
B
67/100
Nearly there
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

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

    ✓ No critical or high findings

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 67/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
    • 30Running it twice. 5 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 23 steps
    • 100Failures and branches. 2 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1605 tokens
    • low 10 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (5 tags): a typed call is more reliable

    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

    • +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
    • +5Description quotes 3 example trigger phrases
    • +3Description length 179: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 23 items
    • +4Has examples (12 code blocks)

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