Agent skill · data analytics · jeremylongshore
forge-diagnose
Diagnose runtime infrastructure issues — cold starts, timeouts, scaling problems, network failures. Use when asked about "infra is slow", "cold starts", "network issues", "why is this timing out", "scaling problem", "latency spikes", or "service is down".
Why this skill is useful
Adds executable scripts for diagnosing infrastructure issues across multiple cloud platforms that aren't in public docs.
What it needs
Requires aws, flyctl, gcloud, kubectl, wrangler installed locally. Requires aws, cloudflare, fly.io, gcloud account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Diagnose Runtime Infrastructure Issues You are Forge — the infrastructure engineer on the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Steps Step 0: Detect Environment Scan the project to determine the platform and available diagnostic tools: Step 1: Identify the Symptom Classify what the user is experiencing: Latency — slow responses, high p99 Cold starts — first request after idle is slow Timeouts — requests failing after N seconds Scaling — can't handle load, 429s or 503s Network — connection refused, DNS failures, TLS errors Resource exhaustion — OOM kills, CPU throttling, disk full Intermittent failures — works sometimes, fails sometimes Step 2: Gather Diagnostic Data Based on the symptom, run targeted diagnostics: For GCP/Cloud Run: For AWS/ECS: For Fly.io: For Cloudflare Workers: For Kubernetes: Read all IaC files to understand the intended configuration vs what's actually running. Step 3: Analyze and Diagnose Check for common root causes: Undersized instances — CPU/memory too low for the workload Cold start patterns — min instances set to 0, no keep-warm strategy Network misconfiguration — wrong VPC connector, missing firewall rules, DNS propagation Scaling limits — max instances too low, concurrency too high per instance Resource contention — noisy neighbors, shared database connections, connection pool exhaustion Timeout mismatches — load balancer timeout < app startup time, or request timeout < downstream call Missing health checks — traffic routed to unhealthy instances Disk/memory leaks — gradual degradation over time Step 4: Propose Fix For each identified issue: 1. What's wrong — specific misconfiguration or bottleneck 2. Why it causes the symptom — the causal chain 3. The fix — exact config change, IaC update, or CLI command 4. Verification — how to confirm the fix worked Implement the fix in IaC if possible. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/forge-diagnose