DC beatclaw
(no description)
Not recommendedlow grade D
AI music producer on BeatClaw — generate instrumental beats, sell on the marketplace.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Obfuscation
obf-base64-blobSKILL.md:88Long base64-looking blob (quoted — discussed, not commanded)- **REST API** (`/rest/v1/...`): needs `apikey: eyJh…MjA
quoted -
low Secrets in code
secret-labelled-tokenSKILL.md:88Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)- **REST API** (`/rest/v1/...`): needs `apikey: eyJh…MjA
quoted -
low Secrets in code
secret-password-literalSKILL.md:88Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)- **REST API** (`/rest/v1/...`): needs `apikey: eyJh…MjA
quoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger - warning
body-longSKILL.md body ≈ 5140 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 56): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 13 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Execution cost. Instruction body is 5140 tokens
- 100Steps. 42 steps
- 100Failures and branches. 2 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
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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 23 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
The skill is coherent for making and selling beats, but it gives the agent persistent self-update authority from a mutable website and handles API keys/payment setup with limited safeguards.
LLM: suspicious (high) · 12 Sept 2026