postgresql-table-design

Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features

Quality

77%

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 ./plugins/database-design/skills/postgresql/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.

A comprehensive, actionable PostgreSQL schema-design reference with executable examples and well-organized sections. Its main gaps are the absence of a sequenced design workflow with validation feedback loops and the lack of progressive disclosure into bundle files for the longer topical sections.

Suggestions

Add a short sequenced 'Design workflow' (identify entities → choose data types → add constraints → index access paths → review gotchas) with a validation/verify step, especially for destructive DDL.

Move longer topical deep-dives (e.g., JSONB Guidance, Extensions, Partitioning) into referenced reference files to improve progressive disclosure.

Tighten a few truism-like asides (e.g., 'Premature denormalization creates maintenance burden') to maximize token efficiency.

Dimension	Reasoning	Score
Conciseness	Dense, terse bullet-point reference that adds PostgreSQL-specific knowledge (gotchas, TOAST strategies, MVCC) rather than basics Claude already knows; a few truism-like asides ('Premature denormalization creates maintenance burden') keep it from a 5.	4 / 5
Actionability	Provides copy-paste-ready, executable SQL for common cases (users, orders, JSONB profiles) plus concrete DDL/index patterns throughout; specific examples cover the common design tasks.	5 / 5
Workflow Clarity	Content is organized by topic, not as a sequenced design workflow, and while Safe Schema Evolution mentions transactional DDL testing, there is no explicit validate→fix→retry feedback loop; the database-operations feedback-loop cap applies.	3 / 5
Progressive Disclosure	Well-organized single-file reference with clear section headers and no nested references; the ~200 lines are coherent as one document, though some sections (Extensions, JSONB Guidance) could conceivably be split into bundle files.	4 / 5
	Total	16 / 20 Passed

Description

78%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.

A strong, third-person description with an explicit 'Use when' trigger and concrete coverage areas. It is distinct and specific, but could enumerate more trigger scenarios (e.g., creating tables, choosing data types, adding indexes) and include common synonyms like 'Postgres'.

Suggestions

Add more concrete trigger phrases: 'Use when creating tables, choosing data types, adding indexes, or defining constraints for PostgreSQL'.

Include the common synonym 'Postgres' alongside 'PostgreSQL' so it triggers on natural phrasing.

Optionally mention 'database schema' or 'DDL' as additional natural keywords.

Dimension	Reasoning	Score
Specificity	Names the domain ('designing or reviewing a PostgreSQL-specific schema') and enumerates concrete coverage areas ('data types, indexing, constraints, performance patterns, and advanced features'); not a full 5 because it lists coverage topics rather than enumerated discrete actions.	4 / 5
Completeness	Explicitly answers both what (schema design/review with listed coverage) and when ('Use this skill when designing or reviewing a PostgreSQL-specific schema'); the 'when' is a single concrete trigger rather than the multiple trigger phrases of a 5.	4 / 5
Trigger Term Quality	'PostgreSQL', 'schema', 'designing or reviewing' are natural terms a user would say, but common synonyms/variants like 'Postgres', 'tables', 'database', or 'DDL' are missing.	4 / 5
Distinctiveness Conflict Risk	'PostgreSQL-specific schema' is a clear, narrow niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Path: plugins/database-design/skills/postgresql/SKILL.md
Commit: d6837ae

Reviewed: about 12 hours 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.