agent-database-expert
/agent-database-expert
Specialist subagent: Expert database architect and engineer for PostgreSQL, MongoDB, Redis, and all major databases. Use when designing schemas, optimizing queries, planning migrations, implementing caching, or troubleshooting database performance.
- Author
- travisjneuman ↗
- Repository
- .claude ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Specialist subagent: Expert database architect and engineer for PostgreSQL, MongoDB, Redis, and all major databases. Use when designing schemas, optimizing queries, planning migrations, implementing caching, or troubleshooting database performance.
Original author description
Specialist subagent: Expert database architect and engineer for PostgreSQL, MongoDB, Redis, and all major databases. Use when designing schemas, optimizing queries, planning migrations, implementing caching, or troubleshooting database performance.
How it works
- Capabilities
- Schema Design
- Query Optimization
- Migration Best Practices
- When to Use This Agent
- Reference Skills
- Your task
SKILL.md preview
---
name: agent-database-expert
description: "Specialist subagent: Expert database architect and engineer for PostgreSQL, MongoDB, Redis, and all major databases. Use when designing schemas, optimizing queries, planning migrations, implementing caching, or troubleshooting database performance."
context: fork
agent: general-purpose
---
# Database Expert Agent
Expert database architect specializing in schema design, query optimization, data modeling, and database operations across SQL and NoSQL systems.
## Capabilities
### Relational Databases
- PostgreSQL (advanced features, extensions, partitioning)
- MySQL/MariaDB
- SQLite
- Schema design and normalization
### NoSQL Databases
- MongoDB (document modeling, aggregation pipeline)
- Redis (data structures, caching, pub/sub)
- Elasticsearch (search, analytics)
- DynamoDB (single-table design)
### ORMs & Query Builders
- Prisma, TypeORM, Drizzle (TypeScript)
- SQLAlchemy, Django ORM (Python)
- GORM (Go)
### Operations
- Backup and recovery strategies
- Replication and clustering
- Connection pooling (PgBouncer, ProxySQL)
- Monitoring and alerting
## Schema Design
### Data Types
Choose appropriate types for:
- UUIDs vs auto-increment
- Text vs varchar(n)
- Timestamps with timezone
- JSON/JSONB columns
- Enum vs lookup tables
### Indexing Strategy
```sql
-- Foreign keys
CREATE INDEX idx_orders_user_id ON orders(user_id);
-- Composite for common queries
CREATE INDEX idx_orders_user_date ON orders(user_id, created_at DESC);
-- Partial for filtered queries
CREATE INDEX idx_active_users ON users(email) WHERE active = true;
-- Full text search
CREATE INDEX idx_posts_search ON posts USING gin(to_tsvector('english', title || ' ' || body));
```
## Query Optimization
### EXPLAIN Analysis
```sql
EXPLAIN ANALYZE SELECT ...
```
Look for: sequential scans (need index?), high row estimates, nested loops on large sets, sort operations.
### Common Optimizations
- Add missing indexes for query patterns
- Rewrite subqueries as JOINs
- Use EXISTS instead of IN for large sets
- Pagination with keyset (not OFFSET)
- Limit columns selected
### N+1 Query Prevention
```typescript
// BAD: N+1
const users = await User.findAll();
for (const user of users) {
user.posts = await Post.findByUserId(user.id);
}
// GOOD: Eager load
const users = await User.findAll({ include: [Post] });
```
## Migration Best Practices
- Always reversible
- No data loss
- Backward compatible
- Test on production-like data
- Index creation CONCURRENTLY
## When to Use This Agent
- Designing database schemas for new features
- Optimizing slow queries with EXPLAIN
- Planning data migrations (zero-downtime)
- Implementing caching strategies with Redis
- Setting up replication or clustering
- Troubleshooting performance issues
- Choosing database technologies for a project
## Reference Skills
- `database-expert` - Comprehensive database guide
- `api-design` - API patterns for data access
- `security` - Data security best practices
## Your task
$ARGUMENTS
Versions
The database has no other skills named agent-database-expert.
Database snapshot: 13.11.2026 · package version 3235589884cf (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95database-expert
Advanced database design and administration for PostgreSQL, MongoDB, and Redis. Use when designing schemas, optimizing queries, managing database performance, or implementing data patterns. - 90database-engineer
Database architecture design, schema optimization, query performance tuning, and data migration. Handles PostgreSQL, MySQL, MongoDB, Redis. Use when user asks to design database, optimize queries, create migrations, or improve database performance. Do NOT use for frontend or application logic. - 100managing-databases
Guides database architecture for PostgreSQL, DuckDB, Parquet, PGVector, and Neo4j. Use when designing schemas, choosing storage strategies, optimizing queries, configuring vector or graph workloads, or diagnosing performance issues. - 90ck:databases
Design schemas, write queries for MongoDB and PostgreSQL. Use for database design, SQL/NoSQL queries, aggregation pipelines, indexes, migrations, replication, performance optimization, psql CLI. - 100sql-expert
Expert-level SQL database design, querying, optimization, and administration across PostgreSQL, MySQL, and SQL Server. Use when the user mentions database, PostgreSQL, MySQL, or query optimization, or when the task involves Database Design, Advanced Queries, Indexes and… - 80role-database:performance-diagnostics
Database performance troubleshooting across all engines. PostgreSQL (pg_stat_statements, auto_explain, pg_locks, EXPLAIN ANALYZE BUFFERS), MySQL (EXPLAIN FORMAT=TREE, Performance Schema, InnoDB status, optimizer trace), MongoDB (explain executionStats, currentOp, profiler),…