postgres-patterns
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.
68
60%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/zh-TW/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 the technology domain (PostgreSQL/Supabase) and lists capability areas but lacks concrete actions and explicit trigger guidance. It reads more like a topic list than actionable skill documentation, making it harder for Claude to know precisely when to select this skill over other database-related options.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about PostgreSQL performance, Supabase database setup, slow SQL queries, or database indexing strategies'
Make capabilities more concrete: instead of 'query optimization', specify 'analyze and rewrite slow queries, add appropriate indexes, optimize JOIN operations'
Include common user terms like 'postgres', 'SQL', 'database performance', 'slow queries', 'db schema' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (PostgreSQL) and lists several actions (query optimization, schema design, indexing, security), but these are category-level rather than concrete specific actions like 'create indexes' or 'write optimized queries'. | 2 / 3 |
Completeness | Describes what the skill covers but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also somewhat weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'PostgreSQL', 'query optimization', 'schema design', 'indexing', 'Supabase', but missing common variations users might say like 'database', 'SQL', 'slow queries', 'db performance', or 'postgres'. | 2 / 3 |
Distinctiveness Conflict Risk | PostgreSQL and Supabase provide some specificity, but 'database patterns', 'query optimization', and 'schema design' could overlap with general database skills or other SQL-related skills without clearer boundaries. | 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 high-quality reference skill that efficiently delivers PostgreSQL best practices in a scannable format. The use of tables, executable code examples, and clear categorization makes it immediately actionable. The only minor gap is the lack of explicit validation steps for configuration changes, though this is partially mitigated by referencing the database-reviewer agent for full workflows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for quick reference, minimal prose, no unnecessary explanations of what PostgreSQL or indexes are. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable SQL code throughout - index creation, RLS policies, upsert patterns, queue processing, and diagnostic queries are all copy-paste ready with clear context for when to use each. | 3 / 3 |
Workflow Clarity | This is primarily a reference/cheat-sheet skill rather than a multi-step workflow. While individual patterns are clear, there's no explicit validation or feedback loop guidance for operations like applying migrations or configuration changes. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear sections (quick reference tables, common patterns, anti-pattern detection, configuration). Appropriately delegates detailed workflows to the database-reviewer agent and references related skills without deep nesting. | 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
- haniakrim21/everything-claude-code
- Commit
ae2cadd
- 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.