BF postgres
Operate PostgreSQL instances safely: configuration review, index and query-plan analysis, vacuum and bloat management, WAL archiving and point-in-time recovery, replication and failover, extensions, major-version upgrades, and evidence-based diagnostics with the bundled read-only pgdiag script. Use when running or inspecting a PostgreSQL server, diagnosing performance or backup health, or planning an upgrade or failover. Do not use for application-level data access patterns (that's backend-engineering) or schema design (that's data-architect/data-engineering).
Operate PostgreSQL instances safely: configuration review, index and query-plan analysis, vacuum and bloat management, WAL archiving and point-in-time…
As a process F 43/100 · Will not run — References files that are not bundled: ../data-engineering/SKILL.md, ../backend-engineering/SKILL.md, ../data-architect/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../data-engineering/SKILL.md - warning
missing-refreference to a missing file: ../backend-engineering/SKILL.md - warning
missing-refreference to a missing file: ../data-architect/SKILL.md - warning
missing-refreference to a missing file: ../supabase/SKILL.md - warning
missing-refreference to a missing file: ../platform-engineering/SKILL.md - warning
missing-refreference to a missing file: ../supabase/references/agent-evals.md - warning
missing-refreference to a missing file: scripts/pgdiag
Process rating: all ten parameters 43/100
- 0Tools and files. 7 referenced file(s) missing: ../data-engineering/SKILL.md, ../backend-engineering/SKILL.md, ../data-architect/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 6 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 64 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3766 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 top-level sections: this looks like several domains in one skill
- medium 6 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 566: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 64 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (9 of 9)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.