A sql-optimization
Deep SQL performance workflow—symptom framing, execution plans, indexing strategy, query rewrite, locking/transaction behavior, statistics, partitioning, and verification. Use when queries time out, DB CPU spikes, or migrations change access patterns.
ProcedureInfrastructureData and analyticstype and topics are labelled automatically from the skill text
A
92/100
Overall score
- Safety 60%
- Quality 40%
- Tests bonus
How to improve
- Add evals/evals.json with 4–6 real requests and expected answers: the full check will then use your cases instead of a model draft.
- Add a spec.yaml with triggers and assertions (skilltest init): the behaviour contract for CI.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Lint
✓ Lint: no remarks
Process maturity 56/100
- 0Result and completion. Does not say what the result is
- 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. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 46 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1212 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 251: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 46 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.
External checks
ClawHub: clean
This is a plain SQL performance guidance skill with no executable code, hidden behavior, or credential access.
LLM: benign (high) · VirusTotal: · 29 May 2026