SKILLEMALL.ai
GitHub ↗ RU Sign in

BD release-checker

一体化发版兼容性检查工具。自动分析 Git diff 检测发版兼容性，通过代码智能识别推送中心/Gateway/配置变更，自动检测 SQL 脚本兼容性并生成多数据库版本，输出完整的 TODO 清单和 Markdown 报告。

ClawHub Hermes author: QFann v1.0.0 MIT-0 5 files body ≈ 4 899 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

IntegrationPostgreSQLSoftware developmentInfrastructurePersonal productivitytype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
56
Run on models
none yet
Process rating
D
49/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: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 112 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 "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "tools"

Process rating: all ten parameters 49/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
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 5 mutating operations with no state check
  • 70Execution cost. Instruction body is 4899 tokens
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 134 steps
  • 100Consistency. Name and required fields are in place
  • low 11 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)
  • +3Description length 112: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • -243 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 58 headings
  • +3Step-by-step instructions: 134 items
  • +4Has examples (43 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: clean
This release-checking skill is coherent and purpose-aligned: it reads repository changes, checks SQL compatibility, and writes reports or converted SQL files, with no evidence of hidden data transfer or persistence.
LLM: benign (high) · VirusTotal: · 29 May 2026