Name: tdg-personal/postgres-patterns
Rating: 53.6 (1 reviews)
Author: tdg-personal

tdg-personal/postgres-patterns

PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.

Quality

67%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

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 provides highly actionable SQL patterns in a concise format. The cheat-sheet tables and executable examples are excellent. The main weakness is the lack of validation/verification steps (e.g., using EXPLAIN ANALYZE to confirm index usage, or checking configuration changes took effect), which slightly limits workflow clarity.

Suggestions

Add a brief validation pattern showing EXPLAIN ANALYZE to verify index usage after creation, e.g., `EXPLAIN ANALYZE SELECT ... -- confirm index scan, not seq scan`

Consider adding a verification step after the configuration template (e.g., `SHOW work_mem;` to confirm settings applied)

Dimension	Reasoning	Score
Conciseness	Every section is lean and practical. No unnecessary explanations of what PostgreSQL is or how indexes work conceptually—just patterns, types, and executable SQL. The cheat-sheet tables are extremely token-efficient.	3 / 3
Actionability	All guidance is concrete with copy-paste-ready SQL examples: index creation, RLS policies, upserts, cursor pagination, queue processing, anti-pattern detection queries, and configuration templates. Every pattern includes executable code.	3 / 3
Workflow Clarity	This is primarily a reference/cheat-sheet skill rather than a multi-step workflow, so sequencing is less critical. However, there are no validation checkpoints—e.g., after creating indexes there's no step to verify they're being used (EXPLAIN ANALYZE), and the configuration template lacks a verification step after pg_reload_conf().	2 / 3
Progressive Disclosure	The skill is well-structured as a quick reference with clear sections and tables, and appropriately delegates deeper review to the `database-reviewer` agent. Related skills and agents are clearly signaled at the bottom. Content is appropriately scoped for a single file.	3 / 3
	Total	11 / 12 Passed

Description

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 topic areas, but remains at a high level without specifying concrete actions or providing explicit trigger guidance. The lack of a 'Use when...' clause is a significant gap that would make it harder for Claude to know when to select this skill over others. Adding natural user trigger terms and specific capabilities would substantially improve selection accuracy.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about PostgreSQL performance, writing SQL queries, designing database schemas, or working with Supabase databases.'

Include more natural trigger term variations such as 'postgres', 'SQL', 'slow queries', 'RLS', 'row level security', 'database performance', 'migrations', '.sql files'.

Replace high-level category names with specific concrete actions, e.g., 'Writes optimized SQL queries, designs normalized schemas, creates indexes for performance, implements row-level security policies.'

Dimension	Reasoning	Score
Specificity	Names the domain (PostgreSQL) and lists several action areas (query optimization, schema design, indexing, security), but these are high-level categories rather than specific concrete 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' are broad enough to overlap with general SQL skills or other database-related skills.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Reviewed

2 months ago

Table of Contents

Discovery Implementation Validation