database-skill
Design and manage relational databases including table creation, migrations, and schema design. Use for database modeling and maintenance.
Best use case
database-skill is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Design and manage relational databases including table creation, migrations, and schema design. Use for database modeling and maintenance.
Teams using database-skill should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/database-skill/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How database-skill Compares
| Feature / Agent | database-skill | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Design and manage relational databases including table creation, migrations, and schema design. Use for database modeling and maintenance.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Database Skill – Schema Design & Migrations ## Instructions 1. **Table Creation** - Define clear and consistent table structures - Use appropriate data types and constraints - Apply primary keys and foreign keys correctly 2. **Schema Design** - Normalize data where appropriate - Model relationships explicitly - Design for scalability and maintainability 3. **Migrations** - Create forward and backward migrations - Ensure migrations are idempotent and safe - Avoid destructive changes without backups 4. **Indexes & Constraints** - Add indexes for frequently queried columns - Enforce uniqueness and referential integrity - Use constraints to protect data correctness ## Best Practices - Use consistent naming conventions - Keep schemas simple and well-documented - Version control all migrations - Test migrations in non-production environments - Follow relational database design principles ## Example Structure ```sql CREATE TABLE users ( id UUID PRIMARY KEY, email TEXT UNIQUE NOT NULL, password_hash TEXT NOT NULL, created_at TIMESTAMP DEFAULT NOW() );
Related Skills
docker-database
Configure database containers with security, persistence, and health checks
Database Sync
Automate database synchronization, replication, migration, and cross-platform data integration
database-architect
Database design and optimization specialist. Schema design, query optimization, indexing strategies, data modeling, and migration planning for relational and NoSQL databases.
arch-database
DB architecture: relational vs document vs graph vs vector, schema design, indexing, replication, sharding
acsets-algebraic-databases
ACSets (Attributed C-Sets): Algebraic databases as in-memory data structures. Category-theoretic formalism for relational databases generalizing graphs and data frames.
vercel-kv-database-rules
Defines how to interact with Vercel's KV database for storing and retrieving session and application data.
Validate with Database
Connect to live PostgreSQL database to validate schema assumptions, compare pg_dump vs pgschema output, and query system catalogs interactively
sqlmap-database-pentesting
This skill should be used when the user asks to "automate SQL injection testing," "enumerate database structure," "extract database credentials using sqlmap," "dump tables and columns...
relational-database-mcp-cloudbase
This is the required documentation for agents operating on the CloudBase Relational Database. It lists the only four supported tools for running SQL and managing security rules. Read the full content to understand why you must NOT use standard Application SDKs and how to safely execute INSERT, UPDATE, or DELETE operations without corrupting production data.
railway-database
Add official Railway database services (Postgres, Redis, MySQL, MongoDB). Use when user wants to add a database, says "add postgres", "add redis", "add database", "connect to database", or "wire up the database". For other templates (Ghost, Strapi, n8n), use the railway-templates skill.
prisma-database-setup
Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on "configure postgres", "connect to mysql", "setup mongodb", "sqlite setup".
playerhoods-database
Authoritative database governance, schema, and RPC invariant model for playerhoods.com (docs v1.4 aligned). Enforces club identity system and RPC-only write posture.