performance-bottleneck-investigator

Diagnose latency, throughput, and scaling bottlenecks across services, databases, queues, and infrastructure.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/koala-man-64/helpful-scripts --skill performance-bottleneck-investigator-koala-man-64
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: performance-bottleneck-investigator
Source: https://github.com/koala-man-64/helpful-scripts/tree/main/exports/codex-skills/repo-local/performance-bottleneck-investigator
Command: npx skills add https://github.com/koala-man-64/helpful-scripts --skill performance-bottleneck-investigator-koala-man-64

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Slow requests, queue lag, worker backlog, and resource saturation are hard to diagnose because symptoms rarely point directly at root causes. This Skill applies a senior performance engineer's workflow to separate symptoms from root causes and produce an evidence-based, prioritized remediation plan. ## Core Features & Use Cases - Evidence-Based Diagnosis: Classifies every finding as Confirmed, Likely, or Possible based on telemetry, traces, profiles, query plans, logs, and load-test results. - Structured Bottleneck Checklists: Systematically inspects application, database, queue/worker, cache, and infrastructure layers, plus a common-mishaps list covering N+1 queries, lock contention, retry storms, cache stampedes, GC pressure, and more. - Ranked Remediation Plan: Ranks findings by severity, confidence, and expected impact, then recommends concrete fixes with tradeoffs, effort estimates, and validation steps. - Use Case: Given an incident where API latency spiked after a deploy, provide the traces, slow query logs, and pool metrics, and receive a ranked root-cause analysis with a validation plan for each proposed fix. ## Quick Start Use the performance-bottleneck-investigator skill to analyze this incident timeline, these traces, and these database metrics, then produce a ranked bottleneck report with a remediation plan.

Frequently Asked Questions about performance-bottleneck-investigator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose the root cause of slow API requests?▼

Provide the available evidence such as traces, APM metrics, logs, and query plans, and the skill identifies the constraining resource or mechanism. It separates symptom from root cause and ranks findings by severity, confidence, and expected impact.

What performance problems can this skill investigate?▼

It covers latency, throughput loss, queue lag, worker backlog, CPU or memory saturation, lock contention, inefficient queries, retry storms, low cache hit rates, and GC pressure across services, databases, queues, caches, and infrastructure.

What inputs does a performance bottleneck analysis need?▼

It accepts source code, architecture descriptions, traces, flame graphs, APM dashboards, query plans, slow query logs, queue metrics, cache statistics, pool metrics, load-test output, and infrastructure metrics. Any mix of these inputs works.

Can it diagnose issues without complete telemetry data?▼

Yes, but it labels unverified findings as Likely or Possible rather than Confirmed. When evidence is thin, it names the specific measurements that would confirm or falsify each hypothesis instead of guessing.

What does the performance investigation report include?▼

The report contains an executive summary, ranked findings with severity and confidence, root-cause analysis, recommended fixes with effort estimates, detected common mishaps, missing data, a validation plan, and a prioritized action list.