Use this skill when designing database schemas for relational (SQL) or document (NoSQL) databases. Provides normalization guidelines, indexing strategies, migration patterns, and performance optimization techniques. Ensures scalable, maintainable, and performant data models.
SkillScore88Maintained
Automatic
◆Data Engineer packdatabaseschema-designsql
Last verified 9/2/2026
What it changes
Passed 22 of 25 test cases with the skill, and 21 of 25 without it.
Without skill84%
With skill88%
Checks it passed that the model alone missed
Uses TIMESTAMP data type
1 fixed21 passed either way3 still failing0 broke
Pass-rate lift
+4 pp
Tokens
+248%
Agent turns
0%
Response time
-7%
Model gemini-3.6-flashMeasured 9/2/2026v122 of 25 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
We need a creation timestamp column for our user account records in MySQL that defaults to current time when a row is inserted and automatically updates when modified. How should this column be defined in SQL?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses TIMESTAMP data type
Missed
Passed
Includes DEFAULT CURRENT_TIMESTAMP clause
Passed
Passed
Includes ON UPDATE CURRENT_TIMESTAMP clause
Passed
Passed
case-02 · gemini-3.6-flash · 9/2/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md710 lines2 files
Database Schema Designer
Overview
This skill provides comprehensive guidance for designing robust, scalable database schemas for both SQL and NoSQL databases. Whether building from scratch or evolving existing schemas, this framework ensures data integrity, performance, and maintainability.
When to use this skill:
Designing new database schemas
Refactoring or migrating existing schemas
Optimizing database performance
Choosing between SQL and NoSQL approaches
Creating database migrations
Establishing indexing strategies
Modeling complex relationships
Planning data archival and partitioning
Database Design Philosophy
Core Principles
1. Model the Domain, Not the UI
Schema reflects business entities and relationships
Don't let UI requirements drive data structure
Separate presentation concerns from data model
2. Optimize for Reads or Writes (Not Both)
OLTP (transactional): Normalized, optimized for writes
OLAP (analytical): Denormalized, optimized for reads
Use when implementing data validation for API payloads, form inputs, or database writes.
Triggers for: Pydantic models, Zod schemas, input sanitization, type validation,
field constraints, or request/response schemas.
NOT for: business logic (use domain services) or authentication/authorization.