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

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/database/database-schema-designer/skills/designing-database-schemas/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The content is highly actionable with concrete SQL patterns and a well-sequenced workflow, but it spends tokens explaining normalization basics and omits validation checkpoints plus references to its own bundled scripts and assets.

Suggestions

Trim the 1NF/2NF/3NF definitions to a one-line reminder, assuming Claude's knowledge of normalization.

Add an explicit validation step to the workflow, e.g. 'Execute DDL via psql/mysql, review errors, fix, and re-run until it applies cleanly'.

Reference the bundled scripts and assets from the body (e.g. point to scripts/schema_validation.py for verification and assets/example_schemas/ for patterns).

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, actionable technical guidance, but step 3 re-explains 1NF/2NF/3NF normalization concepts Claude already knows, which is unnecessary padding.	2 / 3
Actionability	It provides numerous concrete, executable SQL fragments (e.g. 'BIGSERIAL', 'NUMERIC(12,2)', 'orders.customer_id REFERENCES customers(id)', 'CREATE POLICY ... USING (...)') and specific type/constraint/index guidance that is copy-paste ready.	3 / 3
Workflow Clarity	The ten-step Instructions give a clear sequence, but there is no explicit validation or testing checkpoint (e.g. run DDL via psql, verify, fix, re-run) for destructive schema operations, capping the score per the rubric.	2 / 3
Progressive Disclosure	The body is organized into clear sections and links external resources, but it never references the bundled scripts/ (schema_validation.py, erd_generator.py, sql_generator.py) or assets/ (example_schemas/, erd_examples/), leaving those bundle files orphaned.	2 / 3
	Total	9 / 12 Passed

Description

65%Weight 40%Scale 1-3

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

The description establishes a clear niche and includes explicit triggers, but it is weakened by vague buzzwords and second-person phrasing. Tightening the action list and removing fluff would raise specificity.

Suggestions

Replace 'comprehensive guidance and automation' with concrete actions, e.g. 'Design normalized 3NF schemas, generate PostgreSQL/MySQL DDL, and create migration files'.

Remove second-person voice ('when you need to work with') in favor of third person ('Use when designing or migrating database schemas').

Broaden trigger terms to include natural variations like 'database design', 'schema migration', and 'create tables'.

Dimension	Reasoning	Score
Specificity	It names the domain ('database schema design') and two actions ('schema design and migrations') but pads with vague fluff ('comprehensive guidance and automation') rather than listing multiple concrete actions; the second-person phrasing ('when you need to work with') further lowers specificity per the rubric.	1 / 3
Completeness	Both 'what' (provides schema design and migrations) and 'when' are present, with an explicit trigger clause ('Trigger with phrases like...'), satisfying the rubric's requirement for explicit triggers.	3 / 3
Trigger Term Quality	It offers three natural trigger phrases ('design schema', 'create migration', 'model database') but misses common variations users would also say, such as 'database design', 'schema migration', or 'create tables'.	2 / 3
Distinctiveness Conflict Risk	'Database schema design' is a clear niche with distinct triggers ('design schema', 'create migration', 'model database') that are unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 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
Path: plugins/database/database-schema-designer/skills/designing-database-schemas/SKILL.md
Commit: 0540a62

Reviewed: about 4 hours 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.