database-schema-design
Database schema design for PostgreSQL/MySQL with normalization, relationships, constraints. Use for new databases, schema reviews, migrations, or encountering missing PKs/FKs, wrong data types, premature denormalization, EAV anti-pattern.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill database-schema-design93
Does it follow best practices?
Agent success when using this skill
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that excels across all dimensions. It provides specific capabilities (schema design, normalization, constraints), uses natural developer terminology, explicitly states when to use it with concrete scenarios, and carves out a distinct niche in database schema design that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'schema design', 'normalization', 'relationships', 'constraints', 'schema reviews', 'migrations'. Also identifies specific anti-patterns to address like 'missing PKs/FKs', 'wrong data types', 'premature denormalization', 'EAV anti-pattern'. | 3 / 3 |
Completeness | Clearly answers both what ('Database schema design for PostgreSQL/MySQL with normalization, relationships, constraints') and when ('Use for new databases, schema reviews, migrations, or encountering missing PKs/FKs, wrong data types, premature denormalization, EAV anti-pattern'). Explicit 'Use for' clause with specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'PostgreSQL', 'MySQL', 'database', 'schema', 'migrations', 'PKs/FKs', 'data types', 'normalization'. These are terms developers naturally use when discussing database design issues. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on database schema design with distinct triggers (PostgreSQL/MySQL, PKs/FKs, normalization, EAV anti-pattern). Unlikely to conflict with general coding skills or other database skills like query optimization. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent executable SQL examples and clear progressive disclosure through referenced files. The main weakness is some redundancy between sections (Critical Rules, Top 7 Errors, and Known Issues Prevention overlap significantly), which inflates token usage without adding proportional value.
Suggestions
Consolidate the 'Known Issues Prevention' section into the 'Top 7 Critical Errors' section to eliminate redundancy - the checklist already covers verification
Remove explanatory phrases in tables like 'Ensures row uniqueness, enables relationships' - Claude understands why primary keys matter
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., the 'Known Issues Prevention' section largely repeats the 'Critical Rules' and 'Top 7 Critical Errors' sections). Some explanations like 'Ensures row uniqueness, enables relationships' are unnecessary for Claude. | 2 / 3 |
Actionability | Excellent executable SQL examples throughout with clear before/after comparisons. Code is copy-paste ready with proper syntax for both PostgreSQL and MySQL. The production example demonstrates complete, working schemas. | 3 / 3 |
Workflow Clarity | Clear 3-step quick start process, comprehensive checklist with explicit validation steps ('Before Creating Tables', 'Every Table Must Have', etc.), and well-sequenced guidance for schema design. The checklist format provides clear verification points. | 3 / 3 |
Progressive Disclosure | Excellent structure with quick start overview, clear 'When to Load References' section pointing to specific files with line numbers, and well-organized templates/references split. All references are one level deep with clear signaling. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
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.