postgres-patterns

PostgreSQL database patterns for query optimization, schema design, indexing, and security. Quick reference for common patterns, index types, data types, and anti-pattern detection. Based on Supabase best practices.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/postgres-patterns/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a high-quality, executable PostgreSQL quick reference with excellent actionability and good conciseness, but it lacks validation/feedback loops for its destructive and batch database operations, which caps workflow clarity.

Suggestions

Add explicit validation checkpoints for risky operations — e.g., after ALTER SYSTEM config, verify with SHOW <setting> and check pg_stat_activity before reloading; for the anti-pattern queries, include a remediation step (e.g., 'CREATE the missing index, then re-run the detection query to confirm').

Remove the duplicated 'When to Use This Skill' section (it repeats 'When to Activate') to tighten conciseness.

Consider splitting the Configuration Template and Anti-Pattern Detection blocks into separate reference files to improve progressive disclosure for this >50-line skill.

Dimension	Reasoning	Score
Conciseness	Mostly lean: compact tables and terse SQL with inline comments, with only minor padding such as the duplicated 'When to Activate' and 'When to Use This Skill' bullet lists.	4 / 5
Actionability	Fully executable, copy-paste-ready SQL throughout — index creation, composite/covering/partial indexes, RLS policy, UPSERT, cursor pagination, FOR UPDATE SKIP LOCKED queue processing, anti-pattern detection queries, and a config template — covering the common cases concretely.	5 / 5
Workflow Clarity	This is a reference/cheat-sheet with no multi-step sequence or validation checkpoints; the config template runs destructive ALTER SYSTEM statements then pg_reload_conf() with no verify/retry loop, and the rubric caps database-operation skills lacking feedback loops at 3.	3 / 5
Progressive Disclosure	Well-organized sections with a clearly signaled 'Related' pointer to other skills/agents; at ~150 lines it exceeds the simple-skill threshold and inlines config/anti-pattern material that could be split into reference files, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 clearly conveys the skill's PostgreSQL scope and concrete capability areas but omits an explicit 'Use when...' trigger clause, which caps completeness and slightly weakens trigger-term quality.

Suggestions

Add an explicit 'Use when...' sentence naming natural triggers (e.g., 'Use when writing SQL/migrations, designing schemas, troubleshooting slow queries, or implementing RLS') to raise completeness above 3.

Include user-natural terms and synonyms ('slow queries', 'migrations', 'row-level security/RLS', 'connection pooling') to broaden trigger-term coverage.

Use active third-person verbs ('Optimize queries, design schemas, detect anti-patterns') instead of noun-phrase 'patterns' to sharpen specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas — 'query optimization, schema design, indexing, and security' plus 'anti-pattern detection' — but phrases them as 'patterns' rather than direct verbs, leaving minor coverage gaps versus the comprehensive anchor.	4 / 5
Completeness	The 'what' is clear (PostgreSQL patterns for optimization, schema, indexing, security, anti-pattern detection) but there is no explicit 'when'/'Use when...' clause; per the judging guidelines a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Good keyword coverage ('PostgreSQL', 'query optimization', 'schema design', 'indexing', 'security') but a few natural user phrases are missing, and there is no 'Use when...' clause to surface trigger terms like 'slow queries', 'migrations', or 'RLS'.	4 / 5
Distinctiveness Conflict Risk	Clearly niched to PostgreSQL-specific concerns (index types, data types, RLS, anti-pattern detection) with minimal overlap risk; not a 5 only because the absence of explicit trigger phrases leaves a little ambiguity vs related database skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/postgres-patterns/SKILL.md
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.