postgres-patterns

tessl i github:ysyecust/everything-claude-code --skill postgres-patterns

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

69%

Overall

Validation — 69%

Implementation — 88%

Activation — 33%

SKILL.md

Review

Evals

Validation

69%

Warnings & errors only

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
body_output_format	No obvious output/return/format terms detected; consider specifying expected outputs	Warning
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow	Warning

	Total	11 / 16 Passed

Implementation

88%

This is a high-quality quick reference skill that excels at conciseness and actionability. The table-based format for index and data type selection is particularly effective. The main weakness is the lack of explicit validation workflows for operations like migrations or schema changes, though the skill appropriately delegates detailed workflows to the database-reviewer agent.

Suggestions

Add a brief workflow section for common multi-step operations (e.g., 'Adding an index to production: 1. Check table size, 2. Use CONCURRENTLY, 3. Verify with EXPLAIN')

Include validation steps after the anti-pattern detection queries (e.g., 'If unindexed foreign keys found: evaluate query patterns before adding indexes')

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 examples 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	While individual patterns are clear, there's no explicit workflow for multi-step operations like schema design or migration processes. The anti-pattern detection queries are useful but lack guidance on what to do after finding issues.	2 / 3
Progressive Disclosure	Excellent structure with clear sections, tables for quick lookup, and explicit references to the database-reviewer agent for detailed workflows. Related skills are clearly signaled at the end.	3 / 3
	Total	11 / 12 Passed

Activation

33%

The description identifies a clear domain (PostgreSQL/Supabase) and lists relevant capability areas, but lacks concrete action verbs and completely omits trigger guidance. The absence of a 'Use when...' clause significantly weakens Claude's ability to select this skill appropriately from a large skill library.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios like 'Use when optimizing PostgreSQL queries, designing Supabase schemas, or troubleshooting slow database performance'

Include common user terms and variations: 'postgres', 'SQL', 'database', 'slow queries', 'db performance', 'RLS', 'row level security'

Convert category names to concrete actions: instead of 'query optimization', use 'optimize slow queries, add indexes, analyze query plans'

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 actions like 'create indexes' or 'write optimized queries'.	2 / 3
Completeness	Describes what the skill covers (PostgreSQL patterns) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	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	The Supabase and PostgreSQL focus provides some distinction, but 'database patterns' and 'query optimization' could overlap with general SQL skills or other database-related skills.	2 / 3
	Total	7 / 12 Passed

Reviewed

about 7 hours ago

Table of Contents

Validation Implementation Activation

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.