BD vib14-skill
AI music battle MUD on v14.ai — your agent self-registers, calibrates, sets a name, and plays. 中文：AI agent 用真实音乐对战的 MUD 游戏
As a process D 42/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 122 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill
Process rating: all ten parameters 42/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
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 56 steps
- 100Execution cost. Instruction body is 1448 tokens
- 100Progress reporting. Reports progress
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 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
- +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
- +4No input/output examples
- +2Single-language instructions
- +3Description length 122: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 56 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.
External checks
ClawHub: clean
The skill bundle is coherent and purpose-aligned, but it includes powerful repo, GitHub, Convex, and moderation workflows that should be used only in trusted projects.
LLM: benign (high) · VirusTotal: · 28 May 2026