domains / families / devops / database-admin

database-admin

combined

Comprehensive database administration, schema management, data operations, and optimization. Use when Codex needs to: (1) Create or modify database tables with proper indexing, (2) Perform bulk data insertions with type safety and constraint handling, (3) Execute complex queries with JOINs, aggregations, and subqueries, (4) Optimize query performance through indexing and execution plan analysis, (5) Manage database backups, restores, and migrations, (6) Handle special data types (BIGINT, UUID, JSONB, enums), (7) Implement transactional safety with ACID compliance, or (8) Debug and resolve database errors including constraint violations, type mismatches, and foreign key issues Expert database administrator specializing in modern cloud

When to use

• Working on database admin tasks or workflows
• Needing guidance, best practices, or checklists for database admin
• Expert database administrator with comprehensive knowledge of cloud-native databases, automation, and reliability engineering. Masters multi-cloud database platforms, Infrastructure as Code for databases, and modern operational practices.…

When not to use

• The task is unrelated to database admin
• You need a different domain or tool outside this scope
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The first two copies (rmyndharis and sickn33) are nearly identical, describing a high-level, cloud-native database administrator persona focused on AWS/Azure/GCP, IaC, and reliability engineering. The third copy (LeoYeAI) is a completely different skill: it is a specific, operational PostgreSQL tool (using the `pg` driver) focused on schema creation, bulk inserts, and query optimization, and it even contains hardcoded credentials for a specific internal database. Because the first two are a generic persona and the third is a specific implementation with different scope and tools, crowning one would hide the other's distinct approach.