flamegraphs

Convert profiler outputs into SVG flamegraphs for performance analysis.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/awfixers-stuff/opencode-config --skill flamegraphs-awfixers-stuff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flamegraphs
Source: https://github.com/awfixers-stuff/opencode-config/tree/main/skills/flamegraphs
Command: npx skills add https://github.com/awfixers-stuff/opencode-config --skill flamegraphs-awfixers-stuff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Convert raw profiler output into visual flamegraphs and provide interpretation so engineers can quickly identify CPU hotspots and regressions without manual stack analysis.

Core Features & Use Cases

  • Profiler conversion: Step-by-step guidance for turning perf, Callgrind, Go pprof, async-profiler, DTrace and other profiler outputs into folded stacks and SVG flamegraphs.
  • Interpretation & action: Explain wide vs tall frames, leaf hotspots, and how to identify the actionable frame to prioritise optimisations.
  • Differential analysis: Produce and read before/after diffs to surface regressions and improvements.
  • Use case: Profile a release build with perf, generate a flamegraph, identify the widest leaf frame, and convert that insight into a targeted optimization plan.

Quick Start

Generate a flamegraph SVG from perf data and identify the top CPU hotspots to prioritise optimization.

Frequently Asked Questions about flamegraphs

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

FAQPage Schema
How do I convert perf output to a flamegraph for CPU hotspot analysis?

To convert perf output to a flamegraph, process raw profiler traces through stackcollapse to fold stacks, then generate an SVG flamegraph to visually identify CPU hotspots for optimization.

What is differential flamegraph analysis and when do I need it?

Differential flamegraph analysis compares before and after folded stack inputs to surface performance regressions and improvements, helping engineers identify if recent code changes introduced CPU hotspots.

Does this flamegraph conversion approach work with Go pprof and async-profiler?

Yes, flamegraph conversion supports profiler outputs from Go pprof, async-profiler, Callgrind, and DTrace, folding their stack traces into SVG visualizations to identify hotspots across different environments.

How do I interpret a flamegraph to find actionable optimization targets?

To interpret a flamegraph, identify wide leaf frames which indicate high CPU consumption, distinguishing them from tall frames, to pinpoint the specific actionable functions requiring performance optimization.

Do I need Brendan Gregg's flamegraph.pl script to generate SVG visualizations?

Yes, generating SVG flamegraphs requires Brendan Gregg's FlameGraph stackcollapse and flamegraph.pl scripts, or compatible collapse tools, to process pre-collapsed profiler output or raw folded-stack inputs.