npx skills add ...
npx skills add grafana/skills --skill pyroscope
Continuously profile applications with Grafana Pyroscope and read the result as flame graphs. Covers three instrumentation paths — language SDK push (Go / Java / Python / Ruby / Node / .NET / Rust), Alloy eBPF auto-instrumentation (no code change, requires kernel 5.8+ with BTF), and SDK → Alloy receiver — plus ProfileQL queries, profile types (CPU / memory / allocations / goroutines / mutex), Grafana Cloud Profiles endpoint, and Span Profiles trace-to-profile linking. Use when adding profiling to a service, deploying Alloy as a cluster-wide eBPF profiler, hunting CPU / memory hotspots from a flame graph, comparing two profiles to find a regression, or correlating a slow Tempo trace to its profile — even when the user says "find what's burning CPU", "flame graph this app", "continuous profiling", "heap hotspots", or "why is allocation so high" without naming Pyroscope.
npx skills add grafana/skills --skill pyroscope
Continuous profiling — flame graphs of CPU, memory, allocations, mutex contention, goroutines.
pyroscope.receive_http, Alloy forwardsOther SDKs (Java agent, Node, Ruby, .NET, Rust) + Cloud auth + tunable env vars: references/sdks.md.
Profile-type list + full ProfileQL grammar: references/ebpf-and-query.md.
start() / configure() (some SDKs are lazy); check server_address reachable from inside the containerunhealthy with BPF errors → kernel < 5.8 or BTF missing; ls /sys/kernel/btf/vmlinuxbasic_auth_username (must be the numeric stack id, not the slug)PYROSCOPE_FORMAT=jfr; for Python on Alpine, ensure procfs and glibc compatibilityreferences/sdks.md — Java/Node/Ruby/.NET/Rust install + config + env-var table + profile-type matrixreferences/ebpf-and-query.md — full Alloy eBPF pipeline + ProfileQL