A Claude Code plugin marketplace for database experts. One repo, four database engines — each packaged as a plugin you install once and use everywhere.
# Add the marketplace (once)
/plugin marketplace add rajivonai/skills
# Then add the engines you work with
/plugin add postgres-expert
/plugin add mysql-expert
/plugin add oracle-expert
/plugin add mongo-expertOnce installed, Claude automatically engages the right expert skill when you ask a database question — no slash commands needed. Just ask naturally:
"Why is this query slow on my Postgres cluster?" "My MySQL replica is lagging — what do I check?" "Explain this Oracle AWR wait event" "How should I index this MongoDB query?"
| Plugin | Engine | Activates when you ask about… |
|---|---|---|
postgres-expert |
PostgreSQL / Aurora | slow queries, vacuum/bloat, locks, replication, config tuning |
mysql-expert |
MySQL / MariaDB | InnoDB stalls, replication lag, buffer pool, bad query plans |
oracle-expert |
Oracle DB | AWR/ASH, wait events, optimizer/plan regression, SGA/PGA |
mongo-expert |
MongoDB | COLLSCAN, ESR indexes, WiredTiger cache, shard keys |
plugins/<engine>-expert/
├── .claude-plugin/plugin.json # Claude Code metadata
├── .codex-plugin/plugin.json # Codex CLI metadata
└── skills/<engine>-expert/
├── SKILL.md # Diagnostic workflow + config knobs + common root causes
└── references/
└── diagnostics.md # Copy-pasteable queries/commands, loaded on demand
The SKILL.md defines when to engage and how to reason — the diagnostic workflow,
the config knobs that actually matter, and the common root causes to pattern-match first.
The references/ files are loaded only when needed, so the skill stays cheap until relevant.
Depth over breadth. Every finding comes with a read-only diagnostic that proves the diagnosis before recommending a change. No guessing, no generic advice.
- Lead with
pg_stat_statements,EXPLAIN (ANALYZE, BUFFERS),SHOW ENGINE INNODB STATUS, AWR wait events — measure before changing anything. - Index suggestions always include the exact DDL (non-blocking form) with reasoning.
- Config changes always include the apply method (reload vs restart) and the why.