SKILLEMALL.ai
GitHub ↗ RU Sign in

BD agentvibes-openclaw-skill

|-

ClawHub Agent Skills author: 天轰穿 v1.0.0 MIT-0 2 files body ≈ 1 893 tokens Open the sourceclawhub.ai↗ analyzed 11 h ago

|-

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

IntegrationAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
100
Quality 40%
49
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: All mapping items must start at the same column at line 6, column 1: summary: "AgentVibes TTS,切换声音/设性格/控语速/备份" control speed, back... ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "summary"
  • note frontmatter-key unknown frontmatter key "tools"

Process rating: all ten parameters 48/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
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 17 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1893 tokens
  • low 20 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

  • +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 2: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 52 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (15 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This TTS skill is mostly coherent, but it asks for exec-capable behavior while under-scoping updates, cleanup, downloads, broad triggers, and retained audio.
LLM: suspicious (high) · 27 Jul 2026