database-schema-designer

Use when the user asks to create ERD diagrams, normalize database schemas, design table relationships, or plan schema migrations.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./engineering/skills/database-schema-designer/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

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

The content is well-structured, actionable, and token-efficient, with sensible offloading of the full schema to a reference file. Its main weakness is the absence of validation/verification checkpoints in a workflow that generates migrations and RLS policies for destructive database operations.

Suggestions

Add explicit validation steps to the schema-design workflow, e.g. 'apply migration in a transaction, verify with a non-superuser role, roll back on error' before promoting changes.

Fix the syntax error in the seed TypeScript block (missing comma between object fields) so the example is copy-paste ready.

Consider moving the large RLS and seed code blocks into reference files to keep SKILL.md a tighter overview and raise the progressive-disclosure score.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence (no explain-what-a-database-is padding), but the ~60-line inline seed TypeScript block could be referenced rather than fully inlined, leaving minor trim opportunities.	4 / 5
Actionability	Provides executable RLS SQL, seed TypeScript, and bash ERD commands, but the schema-design steps are illustrative rather than copy-paste runnable and the seed snippet contains a syntax error (missing comma), keeping it just below fully executable.	4 / 5
Workflow Clarity	A clear Step 1-3 design sequence exists, but schema/migration/RLS generation is destructive and batch-oriented with no validation or verification checkpoints in the workflow; the rubric caps such skills at 3.	3 / 5
Progressive Disclosure	Well-organized sections with a real, clearly signaled one-level-deep reference (references/full-schema-examples.md), though sizable RLS and seed code blocks remain inlined rather than split out, leaving minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 has strong, distinctive natural triggers but is missing any explicit statement of what the skill does, which the rubric penalizes heavily in completeness. Adding a capabilities clause before the "Use when" trigger would lift it significantly.

Suggestions

Prepend an explicit 'what' clause stating capabilities, e.g. 'Designs relational database schemas and generates migrations, TypeScript/Python types, RLS policies, and seed data.'

Broaden trigger-term coverage with synonyms users actually say, such as 'ER diagrams', 'schema design', and '.prisma' files.

Keep third person ('Designs', 'Generates') and avoid the implied-action-only structure so 'what' and 'when' are both explicit.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("create ERD diagrams", "normalize database schemas", "design table relationships", "plan schema migrations"), but omits the generation outputs the body covers (migrations, types, RLS), so it stops short of comprehensive.	4 / 5
Completeness	It provides an explicit "when" ("Use when the user asks to...") but never states what the skill does — the capabilities are only inferable from the trigger phrases, matching the "only 'when' is present without 'what'" anchor.	2 / 5
Trigger Term Quality	Natural user-facing phrases like "ERD diagrams", "database schemas", and "schema migrations" give good keyword coverage, though synonyms and file extensions (e.g. "ER diagrams", ".prisma") are absent.	4 / 5
Distinctiveness Conflict Risk	The triggers carve a clear niche (ERD diagrams, schema normalization, table relationships, schema migrations) that is unlikely to fire for unrelated skills, matching the top anchor.	5 / 5
	Total	15 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: engineering/skills/database-schema-designer/SKILL.md
Commit: 19392f7

Reviewed: ~6 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.