database-schema-design
Design and optimize database schemas for SQL and NoSQL databases. Use when creating new databases, designing tables, defining relationships, indexing strategies, or database migrations. Handles PostgreSQL, MySQL, MongoDB, normalization, and performance optimization.
91
88%
Does it follow best practices?
Impact
100%
1.17xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes a comprehensive set of natural trigger terms covering both general concepts and specific technologies, explicitly states when to use the skill, and carves out a distinct niche in database design that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Design and optimize database schemas', 'creating new databases', 'designing tables', 'defining relationships', 'indexing strategies', 'database migrations', 'normalization', and 'performance optimization'. | 3 / 3 |
Completeness | Clearly answers both what ('Design and optimize database schemas for SQL and NoSQL databases') and when ('Use when creating new databases, designing tables, defining relationships, indexing strategies, or database migrations') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'database schemas', 'SQL', 'NoSQL', 'tables', 'relationships', 'indexing', 'migrations', 'PostgreSQL', 'MySQL', 'MongoDB', 'normalization'. These are terms users naturally use when discussing database work. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on database schema design with distinct triggers like 'schemas', 'tables', 'relationships', 'indexing', and specific database names. Unlikely to conflict with general coding or data processing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured database schema design skill with excellent executable examples and clear workflow steps. The main weakness is verbosity - it includes explanatory content Claude doesn't need and could benefit from splitting detailed examples into separate reference files. The core instructional content is strong but buried in excessive documentation.
Suggestions
Remove or significantly trim the 'When to use this skill' and 'Input Format' sections - Claude can infer these from context
Move the extensive examples (Blog Platform, MongoDB Schema) to a separate EXAMPLES.md file and reference it
Consolidate the 'Best practices', 'Common Issues', and 'References' sections into a separate REFERENCE.md to keep the main skill focused on the core workflow
Remove metadata section (version, tags, related skills) as this is operational overhead that doesn't help Claude execute the skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but verbose in places. Sections like 'When to use this skill' and 'Input Format' explain things Claude already understands. The examples are valuable but the surrounding explanatory text could be significantly trimmed. | 2 / 3 |
Actionability | Excellent executable code throughout with complete, copy-paste ready SQL examples for PostgreSQL, MySQL patterns, and MongoDB schemas. Includes specific migration scripts, index creation, triggers, and real-world examples that are immediately usable. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit sequencing from entity definition through migration scripts. Includes validation checkpoints (checklists for indexing, decision criteria for normalization), and migration scripts include transaction wrapping with BEGIN/COMMIT for safe rollback. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but it's a monolithic document with no references to external files for detailed content. The ERD examples, full schema examples, and extensive code could be split into separate reference files to keep the main skill leaner. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (695 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 9 / 11 Passed | |
- Repository
- supercent-io/skills-template
- Commit
c033769
- 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.