database-schema-designer

Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable data models.

1.07x

Quality

63%

Does it follow best practices?

Impact

89%

1.07x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/database-schema-designer/SKILL.md

Quality

Content

56%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 highly actionable with extensive executable examples and a clear phased workflow, but it is held back by verbosity (re-teaching database fundamentals Claude already knows) and weak progressive disclosure (bundle files exist but are duplicated inline rather than referenced).

Suggestions

Remove or collapse concept primers Claude already knows — the Key Terms table, normal-form definitions, data-type range tables, and the N+1 explanation — keeping only decision-oriented guidance.

Replace the inlined "Verification Checklist" and "Migration Template" sections with links to references/schema-design-checklist.md and assets/templates/migration-template.sql, and move the deep dives into one-level-deep reference files.

Wire the Verification Checklist into the Process Overview as an explicit validation gate (e.g. "After Phase 4, run the checklist; only declare production-ready when all items pass") to add the missing feedback loop.

Dimension	Reasoning	Score
Conciseness	The ~680-line body re-explains concepts Claude already knows (Key Terms defines Normalization/3NF/OLTP/OLAP/FK/Index; deep dives re-derive 1NF/2NF/3NF, data-type ranges, FLOAT-vs-DECIMAL, and the N+1 problem) and duplicates the bundle checklist and migration template inline, making it noticeably verbose with several padded sections.	2 / 5
Actionability	Abundant copy-paste-ready SQL/JSON/JS examples (CREATE TABLE, ALTER TABLE zero-downtime migrations, CREATE INDEX, EXPLAIN, MongoDB createIndex) cover common cases, but the "Commands" table uses abstract {domain} placeholders rather than literal executable commands and never invokes the bundled migration-template.sql asset.	4 / 5
Workflow Clarity	A clear four-phase process (ANALYSIS→DESIGN→OPTIMIZE→MIGRATE), a command-iteration workflow, a Verification Checklist, and concrete zero-downtime migration steps provide a clear sequence with most checkpoints present; the cap-at-3 destructive-ops rule does not apply because validation (checklist + staging test) is included.	4 / 5
Progressive Disclosure	The body is well-sectioned with collapsible <details> blocks, but the two bundle files (references/schema-design-checklist.md, assets/templates/migration-template.sql) are never linked — their content is inlined instead — and the bulk of the deep-dive material that belongs in separate reference files is kept inline.	3 / 5
	Total	13 / 20 Passed

Description

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

The description is specific and distinct, listing a comprehensive set of concrete capability areas in correct third-person voice. Its main weakness is the missing "Use when..." trigger guidance, which caps completeness and limits its value as a trigger signal.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when designing database schemas, creating tables, or planning migrations for SQL or NoSQL databases."

Include natural trigger phrases users would say ("create tables", "model data", "database design", "schema for") alongside the technical terms.

Drop mild filler ("robust, scalable") to tighten the opening without losing the concrete capability list.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capability areas — "normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization" plus "data integrity, query performance, and maintainable data models" — giving comprehensive coverage of what the skill provides.	5 / 5
Completeness	Clearly answers "what" (design schemas, provide guidelines/strategies/patterns) but contains no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Good keyword coverage ("SQL and NoSQL", "database schemas", "normalization", "indexing", "migration", "constraints") but leans technical and omits natural phrasings users actually say such as "create tables", "model data", or "database design".	4 / 5
Distinctiveness Conflict Risk	Database schema design for SQL/NoSQL is a clear, distinct niche with minimal conflict risk, but the absence of explicit distinguishing trigger phrases keeps it just below a 5.	4 / 5
	Total	16 / 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
skill_md_line_count	SKILL.md is long (688 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: softaworks/agent-toolkit
Path: skills/database-schema-designer/SKILL.md
Commit: 3027f20

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