SKILLEMALL.ai
RU Sign in

AB code-dev-v1-tool-pro

|-. 在需要code dev v1 tool相关能力的开发场景,提供工作流程和配置参考. 该工具基于用户反馈进行了深度优化,提升了可操作性。Use。适用于独立开发者、企业团队和自动化工作流场景，提供结构化输出与错误处理机制，支持中文交互，即开即用。Use when 需要代码生成、编程辅助、调试测试、开发部署时使用。不适用于无明确技术栈的模糊需求。

ClawHub Hermes author: 天轰穿 v1.0.0 MIT-0 2 files body ≈ 2 581 tokens Open the sourceclawhub.ai↗ analyzed 33 h ago

|-. 在需要code dev v1 tool相关能力的开发场景,提供工作流程和配置参考. 该工具基于用户反馈进行了深度优化,提升了可操作性。Use。适用于独立开发者、企业团队和自动化工作流场景，提供结构化输出与错误处理机制，支持中文交互，即开即用。Use when…

As a process B 67/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, progress reporting

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
B
67/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. 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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 175 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • 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"
  • note frontmatter-key unknown frontmatter key "pricing_tier"

Process rating: all ten parameters 67/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 45 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2581 tokens
  • 100Running it twice. No mutating operations
  • low 18 top-level sections: this looks like several domains in one skill

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)
  • +2Single-language instructions
  • +3Description length 175: enough signal without eating the budget
  • +4Structure: 51 headings
  • +3Step-by-step instructions: 45 items
  • +3Output format is stated explicitly
  • +4Has examples (17 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This is a legitimate-looking development workflow skill, but it is broad enough to run file, shell, API, and release/deployment actions without clear user gating.
LLM: suspicious (high) · 20 Aug 2026