designing-database-schemas

Name: designing-database-schemas
Rating: 54 (1 reviews)
Author: jeremylongshore

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill designing-database-schemas

github.com/jeremylongshore/claude-code-plugins-plus-skills

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".

Review Score

54%

Validation Score

13/16

Implementation Score

20%

Activation Score

82%

SKILL.md

Review

Evals

Generated

12 days ago

Warnings & errors only

Criteria	Score
allowed_tools_field	'allowed-tools' contains unusual tool name(s)
metadata_version	'metadata' field is not a dictionary
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata

Overall Assessment

This skill is a generic template with no database-specific content whatsoever. It lacks any SQL examples, migration tool commands (Alembic, Flyway, etc.), schema design patterns, or concrete guidance for database work. The content could apply to literally any technical task and provides no value beyond what Claude already knows about software development processes.

Suggestions

Add concrete SQL examples for common schema operations (CREATE TABLE, ALTER TABLE, foreign keys, indexes) with specific syntax
Include executable migration commands for at least one migration tool (e.g., Alembic, Flyway, or raw SQL migrations)
Replace generic steps with database-specific workflows: schema validation queries, migration dry-run commands, rollback procedures with actual SQL
Remove all generic software development advice (backup data, test in staging, monitor) and focus only on schema-specific guidance Claude doesn't already know

Dimension	Score	Reasoning
Conciseness	1/3	Extremely verbose with generic boilerplate that applies to any task. Contains no database-specific content - phrases like 'Review current configuration, setup, and baseline metrics' and 'Define optimal approach based on best practices' are padding that Claude already knows.
Actionability	1/3	No concrete code, SQL examples, migration commands, or specific database schema patterns. Everything is abstract guidance like 'Execute implementation in non-production environment first' with zero executable content for schema design.
Workflow Clarity	2/3	Steps are numbered and sequenced, but they're generic software development steps, not database schema design workflows. No specific validation for schema changes (e.g., foreign key checks, migration dry-runs) or database-specific checkpoints.
Progressive Disclosure	2/3	References external files in Resources section, but the main content is a monolithic wall of generic text. The referenced files use placeholder paths that may not exist, and the Overview/Examples sections at the bottom are empty placeholders.

Overall Assessment

This description has good trigger term coverage and completeness with explicit trigger phrases, but lacks specificity in describing concrete capabilities. The phrase 'comprehensive guidance and automation' is vague fluff that doesn't communicate what the skill actually does. The opening 'Process use when' appears to be a grammatical error.

Suggestions

Replace vague language like 'comprehensive guidance and automation' with specific actions such as 'create table definitions, define foreign key relationships, generate migration files, validate schema changes'
Fix the grammatical error at the start - 'Process use when' should be revised to proper sentence structure

Dimension	Score	Reasoning
Specificity	2/3	Names the domain (database schema design) and mentions some actions ('schema design', 'migrations', 'guidance and automation'), but lacks concrete specific actions like 'create tables', 'define relationships', 'generate SQL migration files'.
Completeness	3/3	Clearly answers both what ('schema design and migrations with comprehensive guidance and automation') and when ('Trigger with phrases like...' provides explicit trigger guidance). The 'Use when' equivalent is present.
Trigger Term Quality	3/3	Explicitly lists natural trigger phrases users would say: 'design schema', 'create migration', 'model database'. These are realistic terms users would naturally use when needing this skill.
Distinctiveness Conflict Risk	2/3	Reasonably specific to database schema work, but could overlap with general database skills or ORM-related skills. The triggers help distinguish it, but 'database' alone is somewhat broad.