PlotJuggler 4 Perf Profiling
PlotJuggler/PlotJuggler
Guides CPU profiling of PlotJuggler 4 on Linux with perf: count first, record cheaply with LBR, then read per-thread, flat, flamegraph or time-window views.
Guides perf-based profiling of Linux programs through five flows: quick hardware counters, hotspot profiling, cache contention, core-scaling, and a report.
$ npx skills add intel/intel-performance-skills --skill linux-perf -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install intel/intel-performance-skills linux-perf --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/intel/intel-performance-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/linux-perf .claude/skills/linux-perf && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "linux-perf" agent skill from https://github.com/intel/intel-performance-skills/tree/main/skills/linux-perf into .claude/skills/linux-perf/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-perf", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/intel/intel-performance-skills/tree/main/skills/linux-perfType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add intel/intel-performance-skills --skill linux-perf -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install intel/intel-performance-skills linux-perf --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intel/intel-performance-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/linux-perf .agents/skills/linux-perf && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linux-perf" agent skill from https://github.com/intel/intel-performance-skills/tree/main/skills/linux-perf into .agents/skills/linux-perf/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-perf", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add intel/intel-performance-skills --skill linux-perf -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install intel/intel-performance-skills linux-perf --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intel/intel-performance-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/linux-perf .cursor/skills/linux-perf && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linux-perf" agent skill from https://github.com/intel/intel-performance-skills/tree/main/skills/linux-perf into .cursor/skills/linux-perf/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-perf", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/intel/intel-performance-skills.git --path skills/linux-perf--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add intel/intel-performance-skills --skill linux-perf -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install intel/intel-performance-skills linux-perf --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intel/intel-performance-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/linux-perf .gemini/skills/linux-perf && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linux-perf" agent skill from https://github.com/intel/intel-performance-skills/tree/main/skills/linux-perf into .gemini/skills/linux-perf/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-perf", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install intel/intel-performance-skills linux-perfInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add intel/intel-performance-skills --skill linux-perf -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/intel/intel-performance-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/linux-perf .github/skills/linux-perf && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linux-perf" agent skill from https://github.com/intel/intel-performance-skills/tree/main/skills/linux-perf into .github/skills/linux-perf/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-perf", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add intel/intel-performance-skills --skill linux-perf -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install intel/intel-performance-skills linux-perf --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intel/intel-performance-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/linux-perf .opencode/skills/linux-perf && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linux-perf" agent skill from https://github.com/intel/intel-performance-skills/tree/main/skills/linux-perf into .opencode/skills/linux-perf/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linux-perf", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
linux-perfGuides perf-based profiling of Linux programs through five flows: quick hardware counters, hotspot profiling, cache contention, core-scaling, and a report.
This skill always checks /proc/sys/kernel/perf_event_paranoid first and asks the user to choose between running with sudo, lowering the paranoia level, or skipping collection whenever root access is needed, and insists on compiling with -g alongside existing optimization flags so perf report and perf annotate can show real function names and source lines.
It chooses a flow based on the question: perf stat for IPC and cache or branch-miss rates in seconds, perf record plus perf report for hot functions and lines, perf c2c for cache-line contention and false sharing in multi-threaded code, a dual-profile comparison for core-count scaling problems, and a formatted hotspot report with annotated source. It pairs each flow with named fix patterns such as a TTAS spinlock, SIMD upconversion, or a parallel accumulator.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 3e33aec. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
opensslFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Linux perf Profiling Guide loads about 3.1k tokens when it runs, and up to ~22k if it reads all its reference files. Until then it costs about 230 tokens; SKILL.md has 1,417 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
echo 0 | sudo tee /proc/sys/kernel/perf_event_paranoidsudo perf list # full list including hardware events (requires root)Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,417 words (~3,081 tokens).
“Guide the user through profiling with Linux perf — from setup and data collection through reporting and interpretation.”
SKILL.md and 8 other files (references) in skills/linux-perf of intel/intel-performance-skills.
Open the folder on GitHubat commit 3e33aec
Linux perf Profiling Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linux perf Profiling Guide this skillintel/intel-performance-skills | 332 | — | ~3.1k | Automated safety check: Notes | Custom licence | |
| PlotJuggler 4 Perf ProfilingPlotJuggler/PlotJuggler | 6.2k | — | ~1.6k | Automated safety check: Notes | MPL-2.0 | |
| The Art of Debuggingstas00/the-art-of-debugging | 1.7k | — | ~6.1k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Dotnet Debuggingnovotnyllc/dotnet-artisan | 233 | — | ~2.1k | Automated safety check: Pass | MIT | |
| PerftestBrowserWorks/waterfox-android | 376 | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Heaptrackmohitmishra786/low-level-dev-skills | 253 | — | ~1.3k | Automated safety check: Notes | MIT |
PlotJuggler/PlotJuggler
Guides CPU profiling of PlotJuggler 4 on Linux with perf: count first, record cheaply with LBR, then read per-thread, flat, flamegraph or time-window views.
stas00/the-art-of-debugging
Condensed debugging method and tool recipes for Unix, Python and PyTorch programs: crashes, hangs, segfaults, wrong output, CUDA OOM, NaN values and slowness.
novotnyllc/dotnet-artisan
Debugs Windows and Linux/macOS applications (native, .NET/CLR, mixed-mode) with WinDbg MCP (crash dumps, !analyze, !syncblk, !dlk, !runaway, !dumpheap, !gcroot, BSOD), dotnet-dump, lldb with SOS…
BrowserWorks/waterfox-android
Run Firefox performance tests locally or in CI. An agent skill from BrowserWorks/waterfox-android.
mohitmishra786/low-level-dev-skills
heaptrack memory profiler skill for Linux. An agent skill from mohitmishra786/low-level-dev-skills.
mohitmishra786/low-level-dev-skills
Linux perf profiler skill for CPU performance analysis. An agent skill from mohitmishra786/low-level-dev-skills.
intel/intel-performance-skills
Installs, runs, parses and optimizes Phoronix Test Suite benchmarks, saving scores and comparing results before and after code changes.
intel/intel-performance-skills
Spots and fixes known x86 C and C++ performance problems from source or profiler output, such as false sharing, missing restrict and narrow SIMD.
Works with
Categories
Guides perf-based profiling of Linux programs through five flows: quick hardware counters, hotspot profiling, cache contention, core-scaling, and a report. This skill always checks /proc/sys/kernel/perf_event_paranoid first and asks the user to choose between running with sudo, lowering the paranoia level, or skipping collection whenever root access is needed, and insists on compiling with -g alongside existing optimization flags so perf report and perf annotate can show real function names and source lines.
Linux perf Profiling Guide fits situations like: finding out why a Linux program is CPU-bound or slow; diagnosing cache-line contention in multi-threaded code; checking why a workload doesn't scale with more cores.
Run `npx skills add intel/intel-performance-skills --skill linux-perf -a claude-code`. Or copy the skill folder (skills/linux-perf in intel/intel-performance-skills) into .claude/skills/linux-perf in your project. Claude Code loads it when a task matches its description.
Run `npx skills add intel/intel-performance-skills --skill linux-perf -a codex`. Or copy the skill folder (skills/linux-perf in intel/intel-performance-skills) into .agents/skills/linux-perf in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add intel/intel-performance-skills --skill linux-perf -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linux-perf, .gemini/skills/linux-perf, .github/skills/linux-perf and .opencode/skills/linux-perf in your project.
Going by SKILL.md and its folder, Linux perf Profiling Guide needs Python for the scripts in its folder and the command-line tools its instructions call (openssl). Our summary lists: Linux perf tool; Debug symbols (-g) for annotated source.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Linux perf Profiling Guide has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 19k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Linux perf Profiling Guide: PlotJuggler 4 Perf Profiling (PlotJuggler/PlotJuggler, 6.2k stars), The Art of Debugging (stas00/the-art-of-debugging, 1.7k stars), Dotnet Debugging (novotnyllc/dotnet-artisan, 233 stars) and Perftest (BrowserWorks/waterfox-android, 376 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
intel (a GitHub organization, an official publisher) maintains it in intel/intel-performance-skills, which has 332 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 28, 2026.
Source: intel/intel-performance-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.