SKILLEMALL.ai
GitHub ↗ RU Sign in

BF dbq

Multi-database SQL assistant — query MySQL, PostgreSQL, SQLite & MariaDB across dev/test/prod environments with a single command. Security-first: read-only by default, DML/DDL gating, EXPLAIN analysis. 多数据库查询助手，一个命令搞定 MySQL/PostgreSQL/SQLite/MariaDB 和多套环境。

ClawHub Agent Skills author: yinpengfei v1.4.0 MIT-0 11 files body ≈ 1 775 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

Multi-database SQL assistant — query MySQL, PostgreSQL, SQLite & MariaDB across dev/test/prod environments with a single command.

As a process F 35/100 · Will not run — References files that are not bundled: assets/connections*.yaml, assets/.env

AnalyzerMySQLPostgreSQLSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
63
Run on models
none yet
Process rating
F
35/100
Will not run
References files that are not bundled: assets/connections*.yaml, assets/.env
Tools and files w 18
0
Result and completion w 14
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. The text references files that are not there: add them or drop the references.
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: 6. 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 missing-ref reference to a missing file: assets/connections*.yaml
  • warning missing-ref reference to a missing file: assets/.env
  • note frontmatter-key unknown frontmatter key "agent_created"

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: assets/connections*.yaml, assets/.env
  • 0Tools and files. 2 referenced file(s) missing: assets/connections*.yaml, assets/.env
  • 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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 6 mutating operations with no state check
  • 100Steps. 33 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1775 tokens
  • 100Progress reporting. Reports progress

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
  • -33 of 5 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 256: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 33 items
  • +4Has examples (13 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

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

External checks

ClawHub: suspicious
This database skill is not malicious, but it needs Review because it can let agents run write and schema-changing SQL, bypass confirmations, and expose local database credentials.
LLM: suspicious (high) · VirusTotal: · 9 Jul 2026