postgresql-table-design
tessl i github:wshobson/agents --skill postgresql-table-designDesign a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features
Review Score
66%
Validation Score
11/16
Implementation Score
80%
Activation Score
33%
Generated
Validation
Total
11/16Score
Passed| Criteria | Score |
|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') |
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow |
Implementation
Suggestions 2
Score
80%Overall Assessment
This is an excellent, comprehensive PostgreSQL schema design reference that maximizes information density while remaining actionable. The skill excels at conciseness and actionability with concrete examples and specific guidance. Minor weaknesses include the lack of explicit validation workflows for schema changes and the monolithic structure that could benefit from progressive disclosure to separate files for advanced topics.
Suggestions
- Add explicit validation workflow for schema changes (e.g., 'BEGIN; ALTER TABLE...; verify with \d tablename; COMMIT or ROLLBACK') in the Safe Schema Evolution section
- Split advanced topics (JSONB Guidance, Partitioning, Extensions) into separate reference files with links from the main skill
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 3/3 | Extremely dense and efficient—every section delivers actionable information without explaining concepts Claude already knows. No padding or unnecessary context; uses terse bullet points and code examples throughout. |
Actionability | 3/3 | Provides fully executable SQL examples, specific syntax patterns, and concrete guidance for every recommendation. The examples section includes copy-paste ready table definitions with proper constraints and indexes. |
Workflow Clarity | 2/3 | While individual recommendations are clear, the skill lacks explicit validation checkpoints for schema changes. The 'Safe Schema Evolution' section mentions transactional DDL but doesn't provide a step-by-step workflow with verification steps for destructive operations. |
Progressive Disclosure | 2/3 | Content is well-organized with clear sections, but it's a monolithic document (~300 lines) that could benefit from splitting advanced topics (JSONB guidance, partitioning, extensions) into separate reference files. No external file references for deeper dives. |
Activation
Suggestions 3
Score
33%Overall Assessment
The description identifies its PostgreSQL focus and covers relevant topic areas, but lacks concrete action verbs and critically omits explicit trigger guidance ('Use when...'). The absence of when-to-use criteria makes it difficult for Claude to reliably select this skill from a large skill library.
Suggestions
- Add an explicit 'Use when...' clause with trigger scenarios like 'Use when designing new PostgreSQL tables, optimizing existing schemas, or when the user mentions Postgres database structure'.
- Include common term variations: 'Postgres', 'database design', 'table design', 'DDL', 'CREATE TABLE'.
- Convert category nouns to concrete actions: 'Define data types, create indexes, set up foreign key constraints, implement partitioning' instead of 'data types, indexing, constraints'.
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names the domain (PostgreSQL schema design) and lists several action areas (data types, indexing, constraints, performance patterns, advanced features), but these are categories rather than concrete actions like 'create indexes' or 'define foreign key constraints'. |
Completeness | 1/3 | Describes what the skill covers (schema design topics) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. |
Trigger Term Quality | 2/3 | Includes 'PostgreSQL' and 'schema' which users would naturally say, plus related terms like 'indexing' and 'constraints'. However, missing common variations like 'Postgres', 'database design', 'table structure', 'DDL', or '.sql'. |
Distinctiveness Conflict Risk | 2/3 | 'PostgreSQL-specific' provides some distinction from generic database skills, but could still overlap with general SQL skills, database migration skills, or other PostgreSQL-related skills without clearer trigger boundaries. |