SKILLEMALL.ai

BD text-to-sql-query

直接通过 Text-to-SQL 方式查询零售数据库。根据用户自然语言描述,生成 SQL 查询语句并执行。 本 Skill 不依赖语义层或指标平台,而是直接基于数据库 schema 生成 SQL。 触发场景:用户需要查询零售数据、生成 SQL 查询、分析销售/客户/商品数据时使用。

ClawHub Agent Skills author: jackyujun v1.0.0 MIT-0 2 files body ≈ 5 522 tokens Open the sourceclawhub.ai analyzed 3 d ago

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

ReferenceInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
D
42/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. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 5522 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 42/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
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 70Execution cost. Instruction body is 5522 tokens
  • 100Steps. 61 steps
  • 100Consistency. Name and required fields are in place
  • low 10 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
  • -232 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 141: enough signal without eating the budget
  • +4Structure: 48 headings
  • +3Step-by-step instructions: 61 items
  • +4Has examples (23 code blocks)

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

External checks

ClawHub: suspicious
The skill is a disclosed Text-to-SQL database helper, but it gives an agent credentialed live access to sensitive retail and member data without a clear confirmation or data-minimization gate.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026