SKILLEMALL.ai
GitHub ↗ RU Sign in

BD huo15-openclaw-simplify

对最近修改的代码做"复用/质量/效率"三维审查，产出可执行的清理清单；然后实际修复命中的问题。用于刚写完功能、PR 提交前、重构前的自检。触发词：简化代码、清理冗余、重构建议、simplify、code cleanup、代码体检、能不能更简洁。

ClawHub Agent Skills author: Job Zhao v1.0.0 MIT-0 2 files body ≈ 704 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

ReferenceSoftware developmentInfrastructuretype 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
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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 description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "aliases"

Process rating: all ten parameters 48/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
  • 60Tools and files. Uses tools (web, node) that frontmatter does not declare
  • 100Steps. 29 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 704 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)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 122: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 29 items
  • +4Has examples (1 code blocks)
  • +1License stated

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

External checks

ClawHub: clean
This appears to be a code cleanup/refactoring helper with broad trigger wording, but no artifact-backed evidence of hidden or unrelated unsafe behavior.
LLM: benign (medium) · VirusTotal: · 29 May 2026