BC sql-query-generator
Generate secure SQL queries with validation, pagination helpers, risk analysis, and audit-focused safeguards.
Generate secure SQL queries with validation, pagination helpers, risk analysis, and audit-focused safeguards.
As a process C 53/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
AnalyzerPostgreSQLMySQLSoftware developmenttype 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.
- 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: 0. 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") - warning
body-longSKILL.md body ≈ 6281 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 53/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 6281 tokens
- 85Steps. 113 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 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 109: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 49 headings
- +3Step-by-step instructions: 113 items
- +3Output format is stated explicitly
- +4Has examples (29 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.
External checks
ClawHub: suspicious
This skill is a coherent SQL helper, but its strong security claims are not matched by the implementation and it can persist sensitive query/user data in logs.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026