postgresql-table-design

Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features

1.27x

Quality

73%

Does it follow best practices?

Impact

92%

1.27x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/database-design/skills/postgresql/SKILL.md

The canonical home for this skill is postgresql-table-design in wshobson/agents

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 design reference: dense, concrete, and well-organized with copy-paste DDL examples. Its main weakness is the absence of a sequenced workflow with explicit validation checkpoints for destructive/batch schema operations.

Suggestions

Add a short "Workflow" section sequencing schema changes with explicit checkpoints, e.g. draft DDL → apply in transaction → validate → commit, leveraging the existing transactional-DDL and CONCURRENTLY guidance.

For destructive/batch operations (schema evolution, bulk loads, partition swaps), surface an explicit validate→fix→retry feedback loop rather than scattered notes.

Consider splitting the longest sections (Data Types, JSONB Guidance) into reference files to improve navigability and bring progressive disclosure to the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no explanation of what PostgreSQL or a database is), with only minor explanatory clauses that could be trimmed, fitting the efficient-but-not-fully-lean anchor.	4 / 5
Actionability	Guidance is concrete and copy-paste ready: exact data types, exact DDL syntax, and complete `CREATE TABLE` / `CREATE INDEX` examples in the Examples section covering common cases.	5 / 5
Workflow Clarity	This is a prescriptive reference catalog of conditional design rules rather than a sequenced multi-step process, and it lacks an explicit validate→fix→retry feedback loop for the DDL/schema-evolution operations the rubric flags as needing one.	3 / 5
Progressive Disclosure	Single-file skill (no bundle files present) with well-organized section headers (Core Rules, Data Types, Indexing, Partitioning, etc.); good structure with minor gaps, though long sections like Data Types and JSONB Guidance could be split out.	4 / 5
	Total	16 / 20 Passed

Description

70%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 conveys a clear niche and broad capability list but omits an explicit "Use when..." trigger clause, capping completeness at 3. Trigger-term and specificity coverage are strong but not comprehensive.

Suggestions

Add an explicit "Use when..." clause naming concrete triggers, e.g. "Use when designing PostgreSQL tables, choosing data types, or planning indexes and constraints."

Include user-natural synonyms such as "database tables" and "DDL" alongside "schema" to broaden trigger-term coverage.

Sharpen the capability list from category labels ("best-practices", "advanced features") toward concrete verbs ("choose data types", "add indexes", "define constraints").

Dimension	Reasoning	Score
Specificity	Enumerates several concrete capability areas ("data types, indexing, constraints, performance patterns, and advanced features") but these are coverage categories rather than the vivid, fully concrete actions of the top anchor, so it sits just below 5.	4 / 5
Completeness	The description states clearly what the skill does ("Design a PostgreSQL-specific schema. Covers...") but has no "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at 3.	3 / 5
Trigger Term Quality	Natural terms users say are present ("PostgreSQL", "schema", "indexing", "constraints"), but common synonyms/variants ("database", "tables", "DDL", "migrate") are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	"PostgreSQL-specific schema" is a clear niche with distinct triggers and minimal conflict risk with unrelated 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: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/database-design/skills/postgresql/SKILL.md
Commit: 6453c0b

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