database-design

Database schema design, optimization, and migration patterns for PostgreSQL, MySQL, and NoSQL databases. Use for designing schemas, writing migrations, or optimizing queries.

Quality

78%

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 ./skills/database-design/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.

A well-structured, executable reference of database design patterns with lean SQL examples. Its main weakness is the absence of explicit validation/feedback checkpoints in migration workflows, which the rubric caps for destructive database operations.

Suggestions

Add explicit validation checkpoints to the migration workflows, e.g. 'Verify backfill row counts before committing' and a rollback step on failure, to lift workflow_clarity above the destructive-operation cap.

Define or note the referenced tables (orders, posts, customers) so the index and optimization examples are fully self-contained and copy-paste runnable.

Consider moving the larger pattern catalogs (constraints, index patterns) into a separate reference file and linking from SKILL.md to improve progressive_disclosure toward a one-level-deep structure.

Dimension	Reasoning	Score
Conciseness	Mostly lean SQL examples with terse inline comments and little padding; a few explanatory comments ('When read performance matters more than write consistency') could be trimmed, fitting anchor 4 rather than 5.	4 / 5
Actionability	Concrete, executable SQL throughout (index patterns, EXPLAIN, constraints, migration templates), but several examples reference undefined tables (orders, posts) leaving minor gaps, so anchor 4 rather than 5.	4 / 5
Workflow Clarity	A numbered zero-downtime migration sequence and a transactional migration template exist, but for database (destructive/batch) operations there are no explicit validation checkpoints or feedback loops, which per the rubric caps this dimension at 3.	3 / 5
Progressive Disclosure	Well-organized into clear section headers in a single self-contained file with no nested references; content is appropriately placed, though some pattern catalogs (constraints, index patterns) could be split into separate files, fitting anchor 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

87%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, third-person description that clearly states both capabilities and explicit 'Use for' triggers with concrete keywords. Minor room to expand trigger synonyms and action coverage, but overall it directly answers what and when.

Dimension	Reasoning	Score
Specificity	Names the domain ('Database schema design, optimization, and migration patterns') and multiple concrete actions ('designing schemas, writing migrations, or optimizing queries'), with only minor coverage gaps; fits anchor 4 rather than 5 because the action list is solid but not exhaustive.	4 / 5
Completeness	Explicitly answers what ('Database schema design, optimization, and migration patterns...') and when ('Use for designing schemas, writing migrations, or optimizing queries') with concrete trigger phrases, matching the anchor-5 example; not downgraded to 4 because both halves are concrete and explicit.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('designing schemas', 'writing migrations', 'optimizing queries', 'PostgreSQL', 'MySQL', 'NoSQL') with good coverage, but misses some common synonyms and file/format extensions; anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche (database schema design across named engines) with distinct triggers and minimal overlap with other skills; matches anchor 5.	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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: MoizIbnYousaf/ai-agent-skills
Path: skills/database-design/SKILL.md
Commit: 1159592

Reviewed: 18 days 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.