SKILLEMALL.ai
GitHub ↗ RU Sign in

BF code_test

代码功能测试skill，根据用户需求搜索代码、生成测试用例、执行测试并修复问题

ClawHub Agent Skills author: zhouhh2017 v1.0.3 MIT-0 5 files · 1 script body ≈ 253 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 30/100 · Will not run — References files that are not bundled: scripts/log/, scripts/release/v{n}/

ProcedureSoftware developmenttype 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
76/100
safety, quality, tests
Safety 60%
100
Quality 40%
40
Run on models
none yet
Process rating
F
30/100
Will not run
References files that are not bundled: scripts/log/, scripts/release/v{n}/
Tools and files w 18
0
Result and completion w 14
0
When it triggers w 12
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.
  2. The text references files that are not there: add them or drop the references.
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 name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • 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")
  • warning missing-ref reference to a missing file: scripts/log/
  • warning missing-ref reference to a missing file: scripts/release/v{n}/

Process rating: all ten parameters 30/100

Will not run. References files that are not bundled: scripts/log/, scripts/release/v{n}/
  • 0Tools and files. 2 referenced file(s) missing: scripts/log/, scripts/release/v{n}/
  • 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
  • 40Consistency. Frontmatter name (code_test) differs from the folder (python-code-test)
  • 100Steps. 28 steps
  • 100Execution cost. Instruction body is 253 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress

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 39: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -32 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 3 headings
  • +3Step-by-step instructions: 28 items

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

External checks

ClawHub: suspicious
This is a coherent Python testing skill, but it can install packages, run generated tests, and direct changes to real project files without clear approval gates.
LLM: suspicious (high) · VirusTotal: · 29 May 2026