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

78%

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-table-design/SKILL.md

Quality

Content

86%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 well-structured, token-efficient reference skill with executable examples and exemplary progressive disclosure to a real bundle file. The only soft spot is the absence of explicit validation/verification checkpoints for the live-migration use case it advertises.

Suggestions

For the advertised 'schema change on a live database without downtime' use case, add a short inline checklist with a validation checkpoint (e.g. test on a replica, verify row counts) rather than deferring entirely to references.

Consider a one-line 'verify' note after the DDL examples (e.g. '\d+ table' / EXPLAIN the new indexes) to close the validation gap.

Dimension	Reasoning	Score
Conciseness	Dense, lean bullets that assume Claude's competence and skip basics like 'what PostgreSQL is'; only minor inline commentary could be trimmed further.	4 / 5
Actionability	Provides copy-paste-ready executable DDL for common cases (users, orders, profiles with JSONB/GIN) plus specific, concrete prescriptions for types, constraints, and indexes.	5 / 5
Workflow Clarity	Decision flow is clearly sequenced (when-to-use → core rules → data types → constraints → indexing → partitioning → examples), but no explicit validation checkpoints are inline; the live-migration workflow is deferred to references.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview with a single, genuine one-level-deep reference (references/details.md exists) that is repeatedly and clearly signaled, including an enumerated 'Going deeper' section.	5 / 5
	Total	18 / 20 Passed

Description

71%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 clear, well-targeted description that names concrete capability areas and an explicit trigger, with strong distinctiveness. The main gap is narrower trigger-term coverage and a single use-case for the 'when' clause.

Suggestions

Broaden trigger terms with natural synonyms users say, e.g. 'Use when designing or reviewing a PostgreSQL schema, choosing data types, or planning table DDL, indexes, or migrations.'

Add a second concrete trigger scenario (e.g. schema migrations / no-downtime changes) so the 'when' clause covers more of the skill's actual scope.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ('data types, indexing, constraints, performance patterns, and advanced features') tied to a specific action ('designing or reviewing a PostgreSQL-specific schema'), with only minor granularity gaps.	4 / 5
Completeness	Explicitly answers both 'what' (covers best-practices, data types, indexing, constraints, performance patterns, advanced features) and 'when' ('Use this skill when designing or reviewing a PostgreSQL-specific schema'), though the 'when' covers a single scenario.	4 / 5
Trigger Term Quality	Includes a natural trigger phrase ('designing or reviewing a ... schema') but misses common synonyms users would say such as 'database schema', 'table design', 'DDL', 'migrations', or 'data modeling'.	3 / 5
Distinctiveness Conflict Risk	The 'PostgreSQL-specific schema' niche has distinct, targeted triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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-table-design/SKILL.md
Commit: 4236bb9

Reviewed: 6 days 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.