database-schema-design
tessl i github:secondsky/claude-skills --skill database-schema-designDatabase 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
85%This is a well-structured, highly actionable skill with excellent progressive disclosure and clear workflows. The main weakness is some redundancy between sections (Critical Rules, Top 7 Errors, and Known Issues Prevention overlap significantly) and occasional explanations of concepts Claude already understands. The executable SQL examples and comprehensive checklists make this immediately useful for database schema work.
Suggestions
Consolidate the 'Known Issues Prevention' section into the 'Top 7 Critical Errors' section to eliminate redundancy and reduce token count
Remove explanatory phrases like 'Ensures row uniqueness, enables relationships' from the Critical Rules table - 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' for primary keys are things Claude already knows. | 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 schema transformations. | 3 / 3 |
Workflow Clarity | Clear 3-step quick start process, comprehensive checklists with explicit validation steps ('Before Creating Tables', 'Every Table Must Have', etc.), and well-sequenced guidance. The 'Complete Setup Checklist' provides explicit verification checkpoints. | 3 / 3 |
Progressive Disclosure | Excellent structure with quick start at top, detailed sections below, and clear one-level-deep references to templates and reference files. The 'When to Load References' section explicitly guides when to access additional materials with specific file paths and line numbers. | 3 / 3 |
Total | 11 / 12 Passed |
Activation
100%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 |
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.