designing-database-schemas

Process use when you need to work with database schema design. This skill provides schema design and migrations with comprehensive guidance and automation. Trigger with phrases like "design schema", "create migration", or "model database".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable schema-design guide with excellent concrete DDL guidance and examples, weakened by re-explained normalization concepts and a lack of validation/verification checkpoints in the migration workflow. Progressive disclosure is undermined by inline content and missing/non-referenced bundle files.

Suggestions

Trim the 1NF/2NF/3NF textbook definitions and basic data-type explanations down to decision rules Claude doesn't already know, keeping only the skill's specific conventions.

Add an explicit validation step to the workflow (e.g., load the DDL via psql/mysql to confirm it applies cleanly, and verify migrations before applying) given these are destructive database operations.

Either create the referenced bundle files (schema_validation.py, erd_generator.py, sql_generator.py, example_schemas/) and link them from the body, or remove the dangling README checklist entries and split the inline Examples/Error Handling into a referenced file.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and actionable, but the 1NF/2NF/3NF definitions and some type advice re-explain database concepts Claude already knows, so it is not fully lean.	2 / 3
Actionability	It provides concrete, copy-paste-ready DDL snippets, specific data-type and constraint choices, and three worked examples (e-commerce, multi-tenant RLS, event sourcing).	3 / 3
Workflow Clarity	The 10-step sequence is clear, but a DDL/migration workflow involves destructive database operations with no validation or verification checkpoint, capping this dimension at 2.	2 / 3
Progressive Disclosure	Section headers give some structure, but content that could be split (full Examples, Error Handling table) is inline, and the body links only external URLs — the bundle files named in the READMEs do not exist and are not signaled from the body.	2 / 3
	Total	9 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit what-and-when guidance and natural trigger phrases, distinct within its niche. Its only weakness is the vague 'comprehensive guidance and automation' phrasing in place of concrete capabilities.

Suggestions

Replace 'comprehensive guidance and automation' with concrete capabilities (e.g., 'generates PostgreSQL/MySQL DDL with constraints, indexes, and migrations') to lift specificity.

Dimension	Reasoning	Score
Specificity	It names the domain and some actions ('schema design and migrations') but pads with the vague phrase 'comprehensive guidance and automation' rather than listing multiple concrete actions.	2 / 3
Completeness	It states both what the skill does (schema design and migrations) and when to use it via explicit trigger phrases, satisfying both halves.	3 / 3
Trigger Term Quality	It provides natural phrases users would actually say — 'design schema', 'create migration', 'model database' — giving good coverage of trigger terms.	3 / 3
Distinctiveness Conflict Risk	The database-schema niche with distinct triggers ('design schema', 'create migration', 'model database') is unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 607d11b

Reviewed: 3 days 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.