supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
60
41%
Does it follow best practices?
Impact
96%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/supabase-postgres-best-practices/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has a solid structure with an explicit 'Use when' clause, which is its strongest aspect. However, it lacks specific concrete actions (e.g., indexing strategies, query plan analysis, connection pooling) and could benefit from more natural trigger terms that users would actually say when encountering database performance issues. The Supabase attribution is helpful for provenance but doesn't strongly differentiate the skill's trigger conditions.
Suggestions
Add specific concrete actions like 'analyze query plans, recommend indexes, optimize joins, configure connection pooling, and improve schema design for performance'.
Expand trigger terms to include natural variations users would say: 'slow query', 'SQL performance', 'PostgreSQL', 'explain analyze', 'index', 'query tuning', 'database bottleneck'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Postgres performance optimization) and mentions some actions (writing, reviewing, optimizing queries, schema designs, configurations), but doesn't list specific concrete actions like 'analyze query plans', 'add indexes', 'rewrite slow joins', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (Postgres performance optimization and best practices from Supabase) and 'when' (Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations) with an explicit 'Use this skill when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Postgres', 'queries', 'schema designs', 'database configurations', and 'optimizing', but misses common variations users might say such as 'slow query', 'index', 'explain plan', 'SQL performance', 'PostgreSQL', 'Supabase database', or 'query tuning'. | 2 / 3 |
Distinctiveness Conflict Risk | The Postgres/Supabase focus provides some distinctiveness, but 'database configurations' and 'schema designs' are broad enough to potentially overlap with general SQL skills or other database-related skills. The Supabase provenance helps but isn't strongly scoped as a trigger. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a table of contents for a bundle of rule files that are not provided. It contains no actionable SQL examples, no concrete optimization guidance, and no executable workflows. Without the referenced bundle files, the skill provides almost no value to Claude — it describes a structure but teaches nothing about Postgres optimization.
Suggestions
Include at least the most critical optimization rules inline (e.g., missing indexes, N+1 queries, RLS performance) with concrete SQL examples rather than deferring everything to missing reference files.
Add a concrete workflow for diagnosing and fixing query performance issues, such as: run EXPLAIN ANALYZE → identify sequential scans → add appropriate index → verify with EXPLAIN ANALYZE again.
Provide executable SQL examples for the highest-priority patterns (e.g., correct vs incorrect index usage, connection pooling configuration) so the skill has standalone value even without bundle files.
Remove the 'When to Apply' section and the description of what rule files contain — these are meta-information Claude doesn't need — and replace them with actual optimization content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but includes unnecessary elements like the 'When to Apply' section (Claude can infer when to apply database optimization rules) and the description of what each rule file contains, which is meta-information rather than actionable guidance. The priority table is useful but the surrounding prose could be tighter. | 2 / 3 |
Actionability | The skill provides no concrete SQL examples, no executable code, and no specific optimization guidance. It is entirely a meta-document describing a structure of rule files rather than providing any actual database optimization instructions. Without the bundle files, this skill teaches Claude nothing actionable. | 1 / 3 |
Workflow Clarity | There is no workflow, no sequencing of steps, and no validation checkpoints. The skill simply says 'read individual rule files' without describing any process for diagnosing, optimizing, or validating database performance improvements. | 1 / 3 |
Progressive Disclosure | The skill references files like 'references/query-missing-indexes.md' and 'references/_sections.md', but no bundle files are provided, meaning all referenced content is missing. The SKILL.md itself is essentially an empty shell pointing to nonexistent resources, providing no standalone value. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- supabase/agent-skills
- Commit
4e69c80
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.