SKILLEMALL.ai
GitHub ↗ RU Sign in

BD code-right

自动生成软件著作权申报全套材料（Word 文档+截图）。输入系统名称和邮箱， Code-Right 自动完成：系统功能描述撰写、模块分析、真实浏览器截图、 格式合规的申报文档生成、打包 ZIP 邮件发送。 纯 AI 搞不定的排版和截图，由工具链自动完成。

ClawHub Hermes author: ziyiyu v0.2.0 MIT-0 3 files body ≈ 476 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 38/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 Hermes Agent
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
D
38/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.
  2. 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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 128 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "title"

Process rating: all ten parameters 38/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
  • 0Consistency. Frontmatter name (code-right) differs from the folder (code-right-skill)
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 17 steps
  • 100Execution cost. Instruction body is 476 tokens
  • 100Running it twice. No mutating operations

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
  • -219 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 127: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (4 code blocks)
  • +3All 1 scripts are documented
  • +1License stated

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

External checks

ClawHub: clean
This skill is a disclosed remote document-generation client that sends user-provided project details to an external service and emails the resulting download link.
LLM: benign (high) · VirusTotal: · 29 Jul 2026