What problem does it solve? Deployments on Render fail for many reasons—missing environment variables, port binding errors, out-of-memory crashes, or database connection failures—and finding the root cause requires digging through logs, metrics, and database state manually. This Skill provides a systematic debugging workflow that identifies the error pattern and applies the correct fix. ## Core Features & Use Cases - Log-Based Error Detection: Query build, runtime, and HTTP error logs via Render MCP tools or CLI, then match errors against a catalog of 15 known patterns (missing env vars, EADDRINUSE, OOM, health check timeouts, and more). - Metrics and Database Diagnosis: Inspect CPU, memory, HTTP latency, and connection metrics, plus run direct PostgreSQL queries to find slow queries, lock contention, and connection pool exhaustion. - Guided Fix and Verification: Apply fixes such as updating environment variables, then verify with deploy status, error logs, and request metrics. - Use Case: Your web service keeps crashing after deploy. The skill pulls error logs, detects a missing DATABASE_URL pattern, adds the variable via update_environment_variables, and confirms the next deploy goes live. ## Quick Start Debug why my Render service failed to deploy and suggest a fix using the logs and metrics.
