optimizing-database-connection-pooling

Quick Review

The skill has a clear, well-organized structure with generic implementation steps, but critically lacks domain-specific content for database connection pooling. The description and steps are extremely generic and could apply to almost any backend task. There's no concrete guidance on connection pool sizing, timeout configuration, pool exhaustion handling, or database-specific pooling strategies (e.g., PgBouncer, HikariCP, c3p0). The task knowledge is minimal beyond boilerplate best practices. While the structure is clean, the actual value-add for connection pooling is unclear—a CLI agent could generate similar generic guidance without this skill. To improve: add specific pooling parameters, sizing formulas, database-specific configurations, monitoring queries for pool metrics, and concrete examples of pool tuning for different workloads.