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

90%

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

Quality

Content

80%

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

A tight, highly actionable reference dense with executable SQL and minimal padding. Its main gap is workflow safety: migration/batch workflows lack explicit validation checkpoints, and the monolithic single-file structure leaves no room for progressive disclosure via references.

Suggestions

Add an explicit validation checkpoint to migration workflows (e.g. 'Verify the new column is populated and reads correctly before removing the old column') to lift workflow_clarity to 3.

For the safe-migration template, add a verification step inside the transaction such as checking row counts or running a sample query before COMMIT.

Consider moving detailed sections (e.g. Query Optimization, Migration Patterns) into referenced reference files and keeping SKILL.md as an overview, which would let progressive_disclosure score higher.

Dimension	Reasoning	Score
Conciseness	The body is code-forward with terse one-line reminders (e.g. '-- 1NF: Atomic values, no repeating groups') and no padding explaining concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	Nearly every section gives executable, copy-paste-ready SQL — CREATE TABLE, composite/partial/GIN/covering indexes, EXPLAIN (ANALYZE, BUFFERS), keyset pagination — matching the fully-executable top anchor.	3 / 3
Workflow Clarity	The zero-downtime migration lists a 5-step sequence and the safe template uses BEGIN/COMMIT, but neither includes explicit validation/verification checkpoints; per the rubric, missing feedback loops for database/batch operations caps this at 2 rather than 3.	2 / 3
Progressive Disclosure	No bundle files exist and the ~170-line body is a single well-sectioned file with all detail inline; it is organized but content that could be split (e.g. migration patterns, query optimization) has no one-level-deep references, matching the 'structured but inline' anchor rather than the clear-overview-with-references anchor.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 description: concise, third-person, with concrete capabilities and an explicit 'Use for…' trigger clause covering natural terms. It cleanly answers both what and when and occupies a distinct niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Database schema design, optimization, and migration patterns' plus 'designing schemas, writing migrations, or optimizing queries' — matching the top anchor that lists several specific actions.	3 / 3
Completeness	Explicitly answers what ('Database schema design, optimization, and migration patterns...') and when ('Use for designing schemas, writing migrations, or optimizing queries'), satisfying both halves with an explicit trigger clause.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered — 'schema design', 'migrations', 'optimizing queries', and the named engines 'PostgreSQL, MySQL, and NoSQL' — which are exactly what a user would say.	3 / 3
Distinctiveness Conflict Risk	Scoped to database schema work across named DBMS, a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: 039ad59

Reviewed: about 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.