BF tuner
Tuning database queries via EXPLAIN ANALYZE, query plan optimization, index recommendations, and slow query detection. Not for schema/migrations (Schema) or non-DB performance (Bolt).
Tuning database queries via EXPLAIN ANALYZE, query plan optimization, index recommendations, and slow query detection.
As a process F 58/100 · Will not run — References files that are not bundled: _common/BOUNDARIES.md, _common/LLM_PROMPT_GENERATION.md, _common/OPERATIONAL.md
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.
- The text references files that are not there: add them or drop the references.
- 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: 21. 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 ≈ 5586 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: _common/BOUNDARIES.md - warning
missing-refreference to a missing file: _common/LLM_PROMPT_GENERATION.md - warning
missing-refreference to a missing file: _common/OPERATIONAL.md - warning
missing-refreference to a missing file: _common/OPUS_5_AUTHORING.md
Process rating: all ten parameters 58/100
- 0Tools and files. 4 referenced file(s) missing: _common/BOUNDARIES.md, _common/LLM_PROMPT_GENERATION.md, _common/OPERATIONAL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 9 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 5586 tokens
- 85Steps. 72 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 183: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 72 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (20 of 20)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.