BD dbcheck
执行 MySQL、PostgreSQL、Oracle、SQL Server、DM8、TiDB、IvorySQL、GBase 8s、YashanDB、KingbaseES 数据库健康巡检，内置 130+ 条增强风险分析规则，一键生成专业 Word 巡检报告。适用于 DBA 和运维人员快速掌握数据库运行状况、排查风险。项目地址：https://github.com/fiyo/DBCheck
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedurePostgreSQLMySQLGitHubInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Dangerous commands
cmd-cron-mentionscripts/main_oracle_full.py:476Mentions editing / listing crontab (string literal in code, not executed)data['crontab'] = self.run_cmd("crontab -l 2>/dev/null").strip()code literal -
low Risky intent
intent-offensive-securitysecurity.md:16Offensive-security / dual-use content (legitimate for authorised testing; review intended use)**No network communication, no remote execution, no privilege escalation.**
-
low Dangerous commands
cmd-pipe-to-shellsecurity.md:56Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation table row; documentation of a security skill)| `curl ... | bash` (remote code download) | None — all code is bundled locally |
tablesecurity skill -
low Risky intent
intent-offensive-securitysecurity.md:58Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Sends data to remote C2 server | No — no network exfiltration whatsoever |
Files scanned: 31. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 48/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
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 42 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2498 tokens
- 100Running it twice. No mutating operations
- 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
- -220 emoji in the instructions: noise for the model
- -320 of 21 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 194: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (17 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
External checks
ClawHub: suspicious
DBCheck appears to be a legitimate database inspection tool, but it handles sensitive database and SSH data and has under-disclosed paths for remote AI analysis, so users should review it carefully before installing.
LLM: suspicious (medium) · VirusTotal: · 23 Jun 2026