SKILLEMALL.ai
RU Sign in

BD flexible-database-design

(no description)

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

一套可复用的「软 Schema」设计方法：主干硬、尾巴软，三层演进。用户安装后，Agent 可据此指导其真正构建出灵活数据库。 1.

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

ReferenceInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
100
Quality 40%
51
Run on models
none yet
Process rating
D
43/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
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. 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 frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Map keys must be unique at line 20, column 1: pricing_tier: "L2-标准级" license: "Proprietary" ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-long-hermes description is 174 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 "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 43/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 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
  • 30Running it twice. 22 mutating operations with no state check
  • 40Consistency. Frontmatter name (flexible-database-design) differs from the folder (db-schema-designer)
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 42 steps
  • 100Execution cost. Instruction body is 2293 tokens
  • low 20 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 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 39 headings
  • +3Step-by-step instructions: 42 items
  • +4Has examples (3 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
The skill appears intended for database setup guidance, but it grants and describes local execution and project modification with loose scoping and missing bundled assets, so it should be reviewed before installation.
LLM: suspicious (medium) · VirusTotal: · 25 Aug 2026