oma-db
Database specialist for SQL, NoSQL, and vector database modeling, schema design, normalization, indexing, transactions, integrity, concurrency control, backup, capacity planning, data standards, anti-pattern review, and compliance-aware database design. Use for database, schema, ERD, table design, document model, vector index design, RAG retrieval architecture, migration, query tuning, glossary, capacity estimation, backup strategy, database anti-pattern remediation work, and ISO 27001, ISO 27002, or ISO 22301-aware database recommendations.
npx skills add first-fluke/oh-my-agent --skill oma-db --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# DB Agent - Data Modeling & Database Architecture Specialist ## Scheduling ### Goal Design, review, optimize, and document SQL, NoSQL, vector, and retrieval-oriented data systems with explicit schema layers, integrity rules, transaction behavior, capacity assumptions, and audit-aware tradeoffs. ### Intent signature - User asks about database, schema, ERD, table design, document model, vector index, RAG retrieval, migration, query tuning, glossary, backup, capacity, or database anti-patterns. - User needs database recommendations aligned with security, continuity, integrity, or compliance concerns. ### When to use - Relational database modeling, ERD, and schema design - NoSQL document, key-value, wide-column, or graph data modeling - Vector database and retrieval architecture design for semantic search and RAG - SQL/NoSQL technology selection and tradeoff analysis - Normalization, denormalization, indexing, and partitioning - Transaction design, locking, isolation level, and concurrency control - Data standards, glossary, naming rules, and metadata governance - Capacity estimation, storage planning, hot/cold data separation, and backup strategy - Database anti-pattern review and re
- Scheduling
- Goal
- Intent signature
- When to use
- When NOT to use
- Expected inputs
- Expected outputs
- Dependencies
- Control-flow features
- Structural Flow
- Entry
- Scenes
- Transitions
- Failure and recovery
rg --files -g '*.sql' -g '*prisma*' -g '*schema*' -g '*migration*' rg "CREATE TABLE|model |index|foreign key|transaction|embedding|vector" .
What does the oma-db skill do?
Database specialist for SQL, NoSQL, and vector database modeling, schema design, normalization, indexing, transactions, integrity, concurrency control, backup, capacity planning, data standards, anti-pattern review, and compliance-aware database design. Use for database, schema, ERD, table design, document model, vector index design, RAG retrieval architecture, migration, query tuning, glossary, capacity estimation, backup strategy, database anti-pattern remediation work, and ISO 27001, ISO 27002, or ISO 22301-aware database recommendations.
How do I install it?
Run `npx skills add first-fluke/oh-my-agent --skill oma-db --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From first-fluke/oh-my-agent, a repository with 1,204 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.