What problem does it solve? Misconfigured MongoDB connection pools cause pool exhaustion, connection churn, timeouts, and wasted server memory. This Skill guides you to size pools and set timeouts based on your actual deployment context instead of blindly copying arbitrary parameter values. ## Core Features & Use Cases - Context-Driven Configuration: Gathers environment details (serverless vs. traditional, OLTP vs. OLAP, concurrency, traffic patterns) before recommending pool sizes and timeout values. - Scenario-Based Recommendations: Provides tuned parameter tables for serverless functions, long-running OLTP servers, analytical workloads, and high-traffic bursty applications. - Connection Troubleshooting: Diagnoses pool exhaustion, ECONNREFUSED and socket timeouts, connection churn, and high latency, separating client config issues from infrastructure problems. - Use Case: A Node.js API deployed on AWS Lambda keeps hitting MongoWaitQueueTimeoutError under load. The Skill walks you through initializing the client outside the handler, setting maxPoolSize to 3-5, and tuning maxIdleTimeMS for warm invocations. ## Quick Start Ask the assistant to review your MongoDB client connection code and recommend pool and timeout settings for your deployment environment.