SKILLEMALL.ai
GitHub ↗ RU Sign in

BF legionclaw-skill-manager

帮助用户通过交互方式创建、修改和管理 LegionClaw 技能文件包。触发词：创建技能、新建技能、写技能、修改技能、技能开发、skill manager。

ClawHub Claude Code author: LegionSpace-Hackathon v1.0.0 MIT-0 5 files body ≈ 2 190 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

帮助用户通过交互方式创建、修改和管理 LegionClaw 技能文件包。触发词：创建技能、新建技能、写技能、修改技能、技能开发、skill manager。

As a process F 35/100 · Will not run — References files that are not bundled: ../openclaw-file-share/SKILL.md

ProcedureAI 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
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
F
35/100
Will not run
References files that are not bundled: ../openclaw-file-share/SKILL.md
Tools and files w 18
0
Result and completion w 14
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.
  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 description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: ../openclaw-file-share/SKILL.md

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: ../openclaw-file-share/SKILL.md
  • 0Tools and files. 1 referenced file(s) missing: ../openclaw-file-share/SKILL.md
  • 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
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Steps. 79 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2190 tokens
  • 100Running it twice. No mutating operations
  • low 13 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (4 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 78: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +4Structure: 39 headings
  • +3Step-by-step instructions: 79 items
  • +4Has examples (8 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 2 scripts are documented

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

External checks

ClawHub: clean
This appears to be a local skill creation and management aid whose file access is aligned with its stated purpose, with some normal caution because it can change persistent skill files.
LLM: benign (medium) · VirusTotal: · 9 Jul 2026