postgres-patterns
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.
73
60%
Does it follow best practices?
Impact
96%
1.12xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/ja-JP/skills/postgres-patterns/SKILL.mdQuality
Discovery
32%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 identifies a clear domain (PostgreSQL/Supabase) and lists relevant capability areas, but remains at a category level rather than specifying concrete actions. The biggest weakness is the complete absence of a 'Use when...' clause, which is critical for Claude to know when to select this skill from a pool of many. The trigger terms are reasonable but could be expanded with common user phrasings.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about PostgreSQL queries, Supabase database setup, SQL performance issues, or database security policies.'
Include more natural trigger term variations such as 'postgres', 'SQL', 'slow queries', 'RLS', 'row level security', 'database performance', 'migrations'.
Make capabilities more concrete by listing specific actions, e.g., 'Writes optimized SQL queries, designs normalized schemas, creates indexes for performance, implements Row Level Security (RLS) policies.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (PostgreSQL) and lists several action areas (query optimization, schema design, indexing, security), but these are categories rather than concrete specific actions like 'create indexes', 'write RLS policies', or 'optimize slow queries'. | 2 / 3 |
Completeness | Describes what the skill covers (PostgreSQL patterns for optimization, schema, indexing, security) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately detailed, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'PostgreSQL', 'query optimization', 'schema design', 'indexing', 'security', and 'Supabase', but misses common user variations like 'SQL', 'database performance', 'slow queries', 'RLS', 'row level security', 'migrations', or 'postgres'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of PostgreSQL and Supabase provides some distinctiveness, but 'database patterns', 'query optimization', and 'schema design' could overlap with general SQL skills or other database-related skills. The Supabase qualifier helps narrow it somewhat. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-crafted reference skill that efficiently covers PostgreSQL patterns with executable SQL examples and clear organization. The cheat-sheet format with tables and categorized code snippets is ideal for quick lookup. The main gap is the lack of explicit validation/verification steps (e.g., using EXPLAIN ANALYZE after adding indexes), which would strengthen the workflow dimension.
Suggestions
Add a brief validation pattern showing how to verify index effectiveness (e.g., `EXPLAIN ANALYZE` before/after adding an index) to strengthen the workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presented as a quick reference with tables and code snippets. No unnecessary explanations of what PostgreSQL is or how databases work. Every section earns its place with actionable patterns. | 3 / 3 |
Actionability | Provides fully executable SQL examples throughout — index creation, RLS policies, upserts, cursor pagination, queue processing, and diagnostic queries. All code is copy-paste ready with inline comments explaining the 'why'. | 3 / 3 |
Workflow Clarity | This is primarily a reference/cheat-sheet skill rather than a multi-step workflow, so sequential processes are less critical. However, the anti-pattern detection and configuration sections lack validation steps (e.g., verifying index creation succeeded, checking query plan after adding an index). For a reference skill this is acceptable but not exemplary. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections (index cheat sheet, data types, common patterns, anti-patterns, configuration). Appropriately references the `database-reviewer` agent for full workflow and links to related skills. Content is kept at the right level of detail for a quick reference. | 3 / 3 |
Total | 11 / 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
- affaan-m/everything-claude-code
- Commit
5df943e
- 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.