db-agent

Design database schemas, write reversible migrations, and optimize queries.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/clouseryan/agentic-skills --skill db-agent-clouseryan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-agent
Source: https://github.com/clouseryan/agentic-skills/tree/main/dev-team/database
Command: npx skills add https://github.com/clouseryan/agentic-skills --skill db-agent-clouseryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design database schemas, write migrations, optimize queries, and document data models. It analyzes existing schema patterns and follows them strictly across PostgreSQL, MySQL, SQLite, MongoDB, and other databases.

Core Features & Use Cases

  • Schema Design: Tables, indexes, constraints, relationships
  • Migrations: Safe, reversible migration files
  • Query Optimization: Identify and fix slow queries
  • Data Modeling: Document entities, relationships, and access patterns
  • Integrity and Auditing: Enforce constraints and track changes

Quick Start

Initialize a new schema following the project's conventions and generate a safe, reversible migration plan.

Frequently Asked Questions about db-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design scalable database schemas that follow existing project conventions?

Design scalable database schemas by analyzing existing patterns for tables, indexes, and constraints, then following those conventions strictly to maintain consistency across PostgreSQL, MySQL, SQLite, or MongoDB.

What is the safest way to write reversible database migrations for production?

Safe database migrations for production are reversible migration files that enforce data integrity and constraints, allowing you to roll back schema changes without losing data or breaking existing query access patterns.

How do I optimize slow SQL queries and identify missing indexes?

Optimize slow SQL queries by auditing schema patterns, access patterns, and existing indexes to identify bottlenecks, then applying constraints and relationships that enforce data integrity and improve query performance.

Can I use this approach to document data models and access patterns?

Yes, you can document data models by defining entities, relationships, and access patterns, while enforcing constraints and tracking schema changes to maintain strict data integrity and auditing across your database.