BC db-connector-free
数据库连接助手免费版是一套面向独立开发者与小型团队的数据库使用与运维知识库，帮助用户在日常开发中规避连接泄漏、事务死锁、索引失效等高频陷阱。核心能力：提供连接池配置建议、事务隔离级别选择指南、Schema
数据库连接助手免费版是一套面向独立开发者与小型团队的数据库使用与运维知识库，帮助用户在日常开发中规避连接泄漏、事务死锁、索引失效等高频陷阱。核心能力：提供连接池配置建议、事务隔离级别选择指南、Schema
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationPostgreSQLSoftware developmentAI and agentstype 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 · 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-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Map keys must be unique at line 22, column 1: suggested_price: 19.9 tools: ["read", "write", "exec"] ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "pricing_tier" - note
frontmatter-keyunknown frontmatter key "pricing_model" - note
frontmatter-keyunknown frontmatter key "suggested_price"
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. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1611 tokens
- low 12 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 102: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 43 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.
External checks
ClawHub: suspicious
This database guidance skill is mostly advisory, but it requests command execution and file write authority without clear enough scoping or user controls.
LLM: suspicious (high) · 23 Jul 2026