SKILLEMALL.ai
GitHub ↗ RU Sign in

AC sql-free

适用于需要sql相关能力的开发场景,包含结构化的工作流程和可复用的模板,帮助用户快速完成任务并保持代码质量.该技能适用于相关开发场景,提供标准化流程和配置指引.经过深度差异化处置,针对用户反馈和使用痛点进行了改进,提升了实用性和可操作性。Use。Use when 需要数据库操作、SQL查询、数据存储管理时使用。不适用于数据库架构设计决策。 when 需要数据库操作、SQL查询、数据存储管理时使用。不适用于数据库架构设计决策。

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

适用于需要sql相关能力的开发场景,包含结构化的工作流程和可复用的模板,帮助用户快速完成任务并保持代码质量.该技能适用于相关开发场景,提供标准化流程和配置指引.经过深度差异化处置,针对用户反馈和使用痛点进行了改进,提升了实用性和可操作性。Use。Use when…

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationMySQLPersonal productivitySoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
76
Run on models
none yet
Process rating
C
51/100
Has gaps
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. 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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 214 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 "summary_zh"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "pricing_tier"

Process rating: all ten parameters 51/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. 2 mutating operations with no state check
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 54 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1960 tokens
  • 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)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 214: enough signal without eating the budget
  • +4Structure: 40 headings
  • +3Step-by-step instructions: 54 items
  • +4Has examples (4 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This SQL assistant is not clearly malicious, but it asks for execution and write-capable tooling while encouraging database design, DDL migration, and optional execution without strong safety boundaries.
LLM: suspicious (high) · 2 Aug 2026