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.
Install with Tessl CLI
npx tessl i github:supabase/agent-skills --skill supabase-postgres-best-practices57
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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.
This description has good structure with explicit 'Use when' guidance and covers the core domain adequately. However, it lacks specific concrete actions (what exactly does optimization entail?) and misses common trigger terms users would naturally use when seeking database help. The Supabase attribution is nice context but doesn't strongly differentiate the skill's triggers.
Suggestions
Add specific concrete actions like 'analyze query plans', 'recommend indexes', 'identify N+1 queries', 'tune connection pooling' to improve specificity.
Expand trigger terms to include common variations: 'SQL', 'PostgreSQL', 'slow queries', 'query performance', 'database indexes', 'explain analyze'.
| 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', or 'tune connection pooling'. | 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Postgres', 'queries', 'schema designs', 'database configurations', but misses common variations users might say like 'SQL', 'slow queries', 'indexes', 'PostgreSQL', 'db performance', or 'query optimization'. | 2 / 3 |
Distinctiveness Conflict Risk | The Supabase and Postgres focus provides some distinction, but 'database configurations' and 'schema designs' could overlap with general database skills or other SQL-related skills. The Supabase attribution helps but isn't a strong differentiator for triggering. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions as a table of contents rather than actionable guidance. While it's well-organized and concise, it provides zero executable SQL examples, no concrete optimization techniques, and no workflow for diagnosing or fixing performance issues. Claude would need to read the referenced files to get any actual value.
Suggestions
Add a 'Quick Wins' section with 3-5 concrete, copy-paste-ready SQL examples for the most common optimizations (e.g., adding an index, fixing a missing WHERE clause)
Include at least one complete workflow example: diagnose slow query → identify issue → apply fix → validate improvement with EXPLAIN ANALYZE
Add inline examples of the most critical rules (query-missing-indexes, security basics) so the skill provides immediate value without requiring file lookups
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information without explaining what Postgres or Supabase is. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | The skill provides no concrete SQL examples, executable code, or specific commands. It only describes what rule files contain and when to apply guidelines, but doesn't actually provide any actionable database optimization guidance itself. | 1 / 3 |
Workflow Clarity | There is no workflow or sequence of steps provided. The skill is purely a table of contents pointing to other files without explaining how to actually diagnose, optimize, or validate database performance improvements. | 1 / 3 |
Progressive Disclosure | The skill appropriately references external rule files with clear organization by category and priority. However, it provides almost no substantive content in the main file itself—it's essentially just a pointer document with no quick-start guidance. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 14 / 16 Passed | |
- 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.