flame-graph-generator
Generate flame graph generator operations. Auto-activating skill for Performance Testing. Triggers on: flame graph generator, flame graph generator Part of the Performance Testing skill category. Use when working with flame graph generator functionality. Trigger with phrases like "flame graph generator", "flame generator", "flame". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill flame-graph-generator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Flame Graph Generator ## Overview This skill provides automated assistance for flame graph generator tasks within the Performance Testing domain. ## When to Use This skill activates automatically when you: - Mention "flame graph generator" in your request - Ask about flame graph generator patterns or best practices - Need help with performance testing skills covering load testing, stress testing
What does the flame-graph-generator skill do?
Generate flame graph generator operations. Auto-activating skill for Performance Testing. Triggers on: flame graph generator, flame graph generator Part of the Performance Testing skill category. Use when working with flame graph generator functionality. Trigger with phrases like "flame graph generator", "flame generator", "flame". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill flame-graph-generator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
