Name: database-schema-designer
Rating: 61.6 (1 reviews)
Author: alirezarezvani

database-schema-designer

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

Quality

72%

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 ./.gemini/skills/database-schema-designer/SKILL.md

The canonical home for this skill is database-schema-designer in alirezarezvani/claude-skills

Quality

Content

61%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 concrete and well-sectioned with genuinely useful domain guidance, but it is held back by a broken reference to a missing bundle file, a syntax error in the seed example, and a design workflow that lacks validation checkpoints for destructive migrations.

Suggestions

Create references/full-schema-examples.md (or remove the dangling pointer) so the deferred 'Full Schema Example' is actually reachable, and consider splitting the long RLS/seed/ERD blocks into that reference file.

Fix the syntax error in the seed TypeScript (add the missing comma after `name: "fakercompanycatchphrase"`) so the example is copy-paste executable.

Add validation checkpoints to the Schema Design Process — e.g., 'verify normalization (no redundant data)', 'test migration rollback on a copy', 'EXPLAIN query plans to confirm indexes' — so destructive migration work has an explicit feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete and efficient (RLS SQL, seed TypeScript, ERD Mermaid, tight pitfall bullets), but the Overview and Core Capabilities overlap, the seed example runs long, and a few Best Practices restate well-known DB conventions Claude already knows.	4 / 5
Actionability	Provides several concrete, executable examples (RLS policies, Mermaid ERD, seed script) and a worked design process, but the seed TypeScript contains a syntax error (missing comma after `name: "fakercompanycatchphrase"`) so it is not copy-paste runnable — a minor gap keeping it below 5.	4 / 5
Workflow Clarity	The Schema Design Process is a clear 3-step sequence (Requirements → Relationships → Cross-cutting Concerns), but it has no validation checkpoints (e.g., verify normalization, test migration rollback, confirm index usage); since migrations are destructive, the missing feedback loop caps this at 3.	3 / 5
Progressive Disclosure	The only external reference — 'See references/full-schema-examples.md for details' — points to a file that does not exist (no references/ directory is present), so the deferred detail is unreachable and the skill is effectively a single inline file with no real bundle.	2 / 5
	Total	13 / 20 Passed

Description

83%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.

A strong, trigger-rich description with concrete actions and a clear niche. Its only weakness is that capability and trigger are merged into a single 'Use when...' clause rather than stating 'what' and 'when' separately.

Dimension	Reasoning	Score
Specificity	Names four concrete actions — 'create ERD diagrams, normalize database schemas, design table relationships, or plan schema migrations' — giving comprehensive coverage of the skill's scope rather than generic phrasing.	5 / 5
Completeness	The 'Use when...' clause gives an explicit, concrete trigger for when to invoke the skill, and the embedded verbs convey what it does, but there is no standalone 'what does this do' statement separating capability from trigger.	4 / 5
Trigger Term Quality	Includes natural terms a user would say (ERD diagrams, normalize schemas, table relationships, schema migrations), but misses common synonyms such as 'data model', 'database design', or 'entity-relationship diagram', so it falls just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The database-schema-design niche is clearly delineated by distinct triggers (ERD, normalization, table relationships, migrations) with minimal overlap risk against unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/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.