database-specialist
Expert analysis for schema design, SQL performance, transactional logic, and migration safety.
Install
mkdir -p .claude/skills/database-specialist && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15451" && unzip -o skill.zip -d .claude/skills/database-specialist && rm skill.zipInstalls to .claude/skills/database-specialist
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when the task centers on database design or behavior: schema modeling, SQL, indexes, constraints, migrations, query tuning, data integrity, transactional logic, or tradeoffs across engines such as SQLite, PostgreSQL, and MySQL.Key capabilities
- →Reason about relational schema design and entity relationships.
- →Analyze SQL queries, joins, aggregations, and filtering for performance.
- →Develop index strategies, constraints, and uniqueness rules.
- →Plan migrations, backfills, and safe data evolution.
- →Evaluate engine tradeoffs across SQLite, PostgreSQL, and MySQL.
How it works
The skill provides guidance on database design and behavior by understanding data access patterns, preferring explicit constraints, and evaluating reads, writes, cardinality, and growth expectations. It emphasizes operational safety and data integrity.
Inputs & outputs
When to use database-specialist
- →Tune SQL queries
- →Design database schema
- →Safety-check migrations
- →Optimize database indexing
About this skill
Database Specialist
Overview
This skill is for reasoning about databases with emphasis on schema quality, integrity, performance, and operational safety.
When To Use
Use this skill when the user asks for work involving:
- Relational schema design and entity relationships
- SQL queries, joins, aggregations, filtering, and performance analysis
- Index strategy, constraints, uniqueness, and data integrity
- Migrations, backfills, and safe data evolution
- Engine tradeoffs across SQLite, PostgreSQL, MySQL, or similar systems
Working Style
- Understand data access patterns before proposing schema or index changes.
- Prefer explicit constraints in the database when correctness depends on them.
- Evaluate reads, writes, cardinality, and growth expectations together.
- Distinguish clearly between application-layer validation and database-layer guarantees.
- Treat destructive migrations and data rewrites as high-risk operations.
Implementation Rules
- New indexes should be justified by actual query paths, not guesswork.
- Schema changes must consider backward compatibility and migration order.
- Denormalization should only be introduced with a clear read-performance reason.
- Large data changes should be planned to avoid long locks or irreversible failures.
- Queries should be readable first, then optimized with evidence.
Review Checklist
- Does the schema reflect the business rules accurately?
- Are key constraints enforced at the database layer?
- Will the proposed queries scale for expected usage?
- Is the migration path safe for existing data?
- Are engine-specific assumptions called out explicitly?
When not to use it
- →When the task does not center on database design or behavior.
- →When proposing schema or index changes without understanding data access patterns.
- →When introducing denormalization without a clear read-performance reason.
Limitations
- →New indexes must be justified by actual query paths.
- →Schema changes must consider backward compatibility and migration order.
- →Large data changes should be planned to avoid long locks or irreversible failures.
How it compares
This skill offers specialized expertise in database design, performance, and safety, providing a structured approach to data management that goes beyond basic SQL operations.
Compared to similar skills
database-specialist side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| database-specialist (this skill) | 0 | 5mo | No flags | Advanced |
| database-design | 6 | 6mo | Review | Intermediate |
| database-schema-designer | 6 | 6mo | No flags | Intermediate |
| databases | 1 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
database-design
davila7
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
database-schema-designer
davila7
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.
databases
mrgoonie
Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.
schema-designer
clidey
Help design database schemas, create tables, and plan data models. Activates when users ask to create tables, design schemas, or model data relationships.
managing-database-sharding
jeremylongshore
Process use when you need to work with database sharding. This skill provides horizontal sharding strategies with comprehensive guidance and automation. Trigger with phrases like "implement sharding", "shard database", or "distribute data".
database-schema
alinaqi
Schema awareness - read before coding, type generation, prevent column errors