spb/ultra-sharp-agent-skills Public

1<!--2Author: Simon-Pierre Boucher3Contact: contact@spboucher.ai4-->56# db-skills — Database Management Skill Collection78**Author:** Simon-Pierre Boucher9**Contact:** contact@spboucher.ai1011Ten ultra-sharp database-management skills following the method in12[../RESEARCH-SYNTHESIS.md](../RESEARCH-SYNTHESIS.md), grounded in current13practice (3NF-first design, measure-before-tuning with EXPLAIN ANALYZE /14pg_stat_statements, index every foreign key, expand→migrate→contract15zero-downtime migrations, 3-2-1 backups with restore drills). PostgreSQL is16the default dialect; deviations for MySQL/SQLite are noted where they matter.17All pass `python3 ../tools/validate_skills.py`.1819## The collection and its boundaries2021| Skill | Handles | Explicitly does NOT handle |22|---|---|---|23| `writing-sql-queries` | correct, readable, parameterized SQL; CTEs; window functions; NULL traps | schema design → `designing-database-schemas`; tuning → `optimizing-sql-performance` |24| `designing-database-schemas` | domain modeling, 3NF, keys, types, constraints, naming | query writing; migration mechanics; NoSQL → `modeling-nosql-data` |25| `optimizing-sql-performance` | EXPLAIN ANALYZE, indexes, plans, N+1, keyset pagination | incidents → `troubleshooting-databases`; fresh schema design |26| `managing-database-migrations` | versioned, immutable, reversible migrations; zero-downtime patterns | target-schema design; one-off data fixes |27| `backing-up-databases` | scheduled backups, logical vs physical, PITR, 3-2-1, restore drills | HA/replication setup; migrations |28| `securing-databases` | least-privilege roles, injection defense, secrets, TLS, RLS, auditing | app-level auth (sessions/JWT); general firewalls |29| `administering-postgresql` | roles, config knobs, autovacuum, monitoring, upgrades | app query tuning; backup strategy |30| `managing-sqlite` | WAL, pragmas, transactions, safe backup, type affinity | server databases; generic SQL writing |31| `modeling-nosql-data` | access-pattern-first modeling, embed vs reference, key design, TTL | relational schemas; JSON columns in SQL databases |32| `troubleshooting-databases` | incident triage runbook: connections → locks → slow queries → disk → replication | proactive tuning; server configuration |3334## Shared conventions3536- Description = WHAT + "Use when …" (literal phrases) + "Do not use for …"37- Measure before changing anything; capture evidence before restarting anything38- One default per decision (tool, key type, journal mode) with an escape hatch39- Every workflow ends with a validation step (test restore, rollback rehearsal, EXPLAIN before/after)40- `SKILL.md` <150 lines; depth in `references/patterns.md` (with TOC)41