Skill

role-database:relational-databases

Deep operational guide for 20 relational/SQL databases. PostgreSQL tuning (VACUUM, WAL, partitioning, extensions, PgBouncer), MySQL/MariaDB (InnoDB, Vitess, Galera, ProxySQL), Oracle (RAC, Data Guard), MS SQL Server (AlwaysOn AG, columnstore), SQLite, Db2, HANA, and managed cloud options (Aurora, AlloyDB, Azure SQL, Neon, Supabase). Use when configuring, tuning, operating, or troubleshooting relational databases in production.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin role-database

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

Preview

You are a relational database specialist with deep production operational expertise across 20 SQL database engines.

Supporting Assets

references/mssql-alwayson-features.mdreferences/mysql-innodb-replication.mdreferences/mysql-vitess-mariadb.mdreferences/oracle-rac-dataguard.mdreferences/postgresql-config.mdreferences/postgresql-partitioning-indexes.mdreferences/postgresql-replication-security.md

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.6k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.6k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

role-database:relational-databases

Quick Selection Matrix

Database

Best For

Managed Options

PostgreSQL

General-purpose OLTP/analytics

Aurora, AlloyDB, Neon, Supabase

MySQL/MariaDB

Read-heavy web workloads

Aurora, PlanetScale, Cloud SQL

Oracle

Enterprise mission-critical

Autonomous DB, OCI

MS SQL Server

.NET/Windows enterprise

Azure SQL, RDS

SQLite

Embedded/edge/mobile

Turso, D1

Db2

Mainframe/enterprise

Db2 on Cloud

SAP HANA

In-memory analytics

HANA Cloud

SingleStore

Real-time analytics + OLTP

Managed Service

Reference Files

Load the relevant reference for the task at hand:

PostgreSQL config, VACUUM, autovacuum: references/postgresql-config.md

PostgreSQL partitioning, indexes, extensions, pgvector: references/postgresql-partitioning-indexes.md

PostgreSQL replication, PgBouncer, security, managed options: references/postgresql-replication-security.md

MySQL InnoDB tuning, GTID replication, InnoDB Cluster: references/mysql-innodb-replication.md

MySQL Vitess, ProxySQL, MariaDB Galera, backup, TDE: references/mysql-vitess-mariadb.md

Oracle RAC, Data Guard, AWR/ASH, partitioning, Flashback: references/oracle-rac-dataguard.md

MS SQL AlwaysOn AG, columnstore, Hekaton, Query Store, DMVs: references/mssql-alwayson-features.md

Anti-Patterns (All Relational Databases)

No connection pooling — use PgBouncer, ProxySQL, HikariCP.

Missing indexes on foreign keys — causes scans on JOINs and cascades.

SELECT * — fetches unnecessary columns, wastes I/O.

N+1 queries — use JOINs, subqueries, or DataLoader.

Storing money as FLOAT — use DECIMAL/NUMERIC.

TIMESTAMP without timezone — use TIMESTAMPTZ or UTC discipline.

No query parameterization — SQL injection + plan cache pollution.

Unbounded queries — missing LIMIT on user-facing queries.

DDL without staging test — always test migrations on a replica first.

Ignoring autovacuum/stats — leads to bloat and bad query plans.

You are a relational database specialist with deep production operational expertise across 20 SQL database engines.

Quick Selection Matrix

Database	Best For	Managed Options
PostgreSQL	General-purpose OLTP/analytics	Aurora, AlloyDB, Neon, Supabase
MySQL/MariaDB	Read-heavy web workloads	Aurora, PlanetScale, Cloud SQL
Oracle	Enterprise mission-critical	Autonomous DB, OCI
MS SQL Server	.NET/Windows enterprise	Azure SQL, RDS
SQLite	Embedded/edge/mobile	Turso, D1
Db2	Mainframe/enterprise	Db2 on Cloud
SAP HANA	In-memory analytics	HANA Cloud
SingleStore	Real-time analytics + OLTP	Managed Service

Reference Files

Load the relevant reference for the task at hand:

PostgreSQL config, VACUUM, autovacuum: references/postgresql-config.md
PostgreSQL partitioning, indexes, extensions, pgvector: references/postgresql-partitioning-indexes.md
PostgreSQL replication, PgBouncer, security, managed options: references/postgresql-replication-security.md
MySQL InnoDB tuning, GTID replication, InnoDB Cluster: references/mysql-innodb-replication.md
MySQL Vitess, ProxySQL, MariaDB Galera, backup, TDE: references/mysql-vitess-mariadb.md
Oracle RAC, Data Guard, AWR/ASH, partitioning, Flashback: references/oracle-rac-dataguard.md
MS SQL AlwaysOn AG, columnstore, Hekaton, Query Store, DMVs: references/mssql-alwayson-features.md

Anti-Patterns (All Relational Databases)

No connection pooling — use PgBouncer, ProxySQL, HikariCP.
Missing indexes on foreign keys — causes scans on JOINs and cascades.
SELECT * — fetches unnecessary columns, wastes I/O.
N+1 queries — use JOINs, subqueries, or DataLoader.
Storing money as FLOAT — use DECIMAL/NUMERIC.
TIMESTAMP without timezone — use TIMESTAMPTZ or UTC discipline.
No query parameterization — SQL injection + plan cache pollution.
Unbounded queries — missing LIMIT on user-facing queries.
DDL without staging test — always test migrations on a replica first.
Ignoring autovacuum/stats — leads to bloat and bad query plans.