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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill designing-database-schemas54
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
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 | Reasoning | Score |
|---|---|---|
Specificity | 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'. | 2 / 3 |
Completeness | 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. | 3 / 3 |
Trigger Term Quality | 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. | 3 / 3 |
Distinctiveness Conflict Risk | 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. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
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 | Reasoning | Score |
|---|---|---|
Conciseness | 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. | 1 / 3 |
Actionability | 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. | 1 / 3 |
Workflow Clarity | 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. | 2 / 3 |
Progressive Disclosure | 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. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- Reviewed
Table of Contents
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.