Evidence-first performance profiling — tool selection, methodology, interpretation. Use BEFORE guessing at performance issues. Tools first, logs second, code last. Covers: slow queries, high latency, CPU spikes, memory growth, throughput regressions (including 'got slower after deploy' — measure before assuming the deploy diff is the cause). Not for: crashes / logic errors (→ debug), tests being slow as test design issue (→ test-strategy).
$npx -y skills add cookys/autopilot --skill profilingInstalls into the current project.
Run `npx skills use "https://github.com/cookys/autopilot" --skill "cookys/autopilot/profiling"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/cookys/autopilot" that are relevant to the current task. Run `npx skills add "https://github.com/cookys/autopilot"` and select the relevant skills, then follow their instructions.