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.

Install with Tessl CLI

npx tessl i github:softaworks/agent-toolkit --skill database-schema-designer

What are skills?

Overall
score

81%

Review — 77%

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/skill

Learn more

Validation — 13 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

68%

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 excels at specificity and distinctiveness, clearly articulating concrete database design capabilities in a well-defined technical niche. However, it lacks explicit trigger guidance ('Use when...') which is critical for skill selection, and could benefit from more natural user-facing keywords beyond technical jargon.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about database design, table structures, schema planning, or data modeling.'

Include more natural trigger terms users might say: 'tables', 'ERD', 'entity relationship', 'data model', 'foreign keys', 'database structure', 'schema migration'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Design robust, scalable database schemas', 'normalization guidelines', 'indexing strategies', 'migration patterns', 'constraint design', and 'performance optimization'. Uses third person voice correctly.	3 / 3
Completeness	Clearly answers 'what does this do' with detailed capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through the domain description.	2 / 3
Trigger Term Quality	Includes relevant terms like 'SQL', 'NoSQL', 'database schemas', 'normalization', 'indexing', 'migration', but misses common user variations like 'tables', 'ERD', 'data model', 'foreign keys', 'primary keys', or file extensions.	2 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on database schema design with distinct technical domain (SQL/NoSQL, normalization, indexing). Unlikely to conflict with general coding or document skills.	3 / 3
	Total	10 / 12 Passed

Implementation

85%

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

This is a well-structured, highly actionable skill with excellent progressive disclosure through collapsible sections. The workflow is clear with proper validation checkpoints. The main weakness is some verbosity in explaining concepts Claude already knows (basic database terminology) and trigger tables that add bulk without significant value.

Suggestions

Remove or significantly trim the 'Key Terms' section - Claude already understands normalization, foreign keys, and OLTP/OLAP concepts

Consider removing the 'Triggers' table as it adds tokens without providing actionable guidance

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some unnecessary content like the 'Key Terms' section explaining basic concepts Claude already knows (normalization, OLTP/OLAP, foreign keys). The trigger table and some explanatory text could be trimmed.	2 / 3
Actionability	Provides fully executable SQL code examples throughout, including complete CREATE TABLE statements, migration templates, index creation syntax, and specific commands. The examples are copy-paste ready and cover multiple scenarios.	3 / 3
Workflow Clarity	The Process Overview provides a clear 4-phase workflow with explicit steps. The verification checklist serves as a validation checkpoint, and the migration section includes explicit backward compatibility and rollback considerations for destructive operations.	3 / 3
Progressive Disclosure	Excellent use of collapsible details sections for deep dives, keeping the main content scannable while providing comprehensive reference material. The structure moves from Quick Start to Quick Reference to detailed sections, with clear navigation.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 13 / 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
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning

	Total	13 / 16 Passed

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