Observe Trace
ruvnet/ruflo
Trace agent execution by collecting spans and building a trace tree for a task
Profile GPU kernels using rocprofv3 to collect ATT instruction-level traces, then analyze the trace data using hotspotanalyzer.py to identify top-K stall hotspots (VMEM-load, VMEM-wait…
$ npx skills add ROCm/FlyDSL --skill kernel-trace-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ROCm/FlyDSL kernel-trace-analysis --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/ROCm/FlyDSL.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/kernel-trace-analysis .claude/skills/kernel-trace-analysis && 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 "kernel-trace-analysis" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/kernel-trace-analysis into .claude/skills/kernel-trace-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kernel-trace-analysis", 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/ROCm/FlyDSL/tree/main/.claude/skills/kernel-trace-analysisType 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 ROCm/FlyDSL --skill kernel-trace-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ROCm/FlyDSL kernel-trace-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ROCm/FlyDSL.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/kernel-trace-analysis .agents/skills/kernel-trace-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "kernel-trace-analysis" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/kernel-trace-analysis into .agents/skills/kernel-trace-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kernel-trace-analysis", 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 ROCm/FlyDSL --skill kernel-trace-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ROCm/FlyDSL kernel-trace-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ROCm/FlyDSL.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/kernel-trace-analysis .cursor/skills/kernel-trace-analysis && 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 "kernel-trace-analysis" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/kernel-trace-analysis into .cursor/skills/kernel-trace-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kernel-trace-analysis", 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/ROCm/FlyDSL.git --path .claude/skills/kernel-trace-analysis--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 ROCm/FlyDSL --skill kernel-trace-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ROCm/FlyDSL kernel-trace-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ROCm/FlyDSL.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/kernel-trace-analysis .gemini/skills/kernel-trace-analysis && 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 "kernel-trace-analysis" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/kernel-trace-analysis into .gemini/skills/kernel-trace-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kernel-trace-analysis", 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 ROCm/FlyDSL kernel-trace-analysisInstalls 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 ROCm/FlyDSL --skill kernel-trace-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ROCm/FlyDSL.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/kernel-trace-analysis .github/skills/kernel-trace-analysis && 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 "kernel-trace-analysis" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/kernel-trace-analysis into .github/skills/kernel-trace-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kernel-trace-analysis", 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 ROCm/FlyDSL --skill kernel-trace-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ROCm/FlyDSL kernel-trace-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ROCm/FlyDSL.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/kernel-trace-analysis .opencode/skills/kernel-trace-analysis && 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 "kernel-trace-analysis" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/kernel-trace-analysis into .opencode/skills/kernel-trace-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kernel-trace-analysis", 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.
kernel-trace-analysisProfile GPU kernels using rocprofv3 to collect ATT instruction-level traces, then analyze the trace data using hotspotanalyzer.py to identify top-K stall hotspots (VMEM-load, VMEM-wait…
Kernel Trace Analysis is an agent skill from ROCm/FlyDSL. Profile GPU kernels using rocprofv3 to collect ATT instruction-level traces, then analyze the trace data using hotspotanalyzer.py to identify top-K stall hotspots (VMEM-load, VMEM-wait, LDS/SMEM-wait, barrier, MFMA stalls) mapped back to source lines, and produce an actionable optimization plan. Usage: /kernel-trace-analysis <cmd Can also analyze an existing dispatch dir directly: /kernel-trace-analysis --dir <path
Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/hotspot_analyzer.py` and `scripts/pmc_l2_analyzer.py`).
The repository describes itself as: FlyDSL is the Python front‑end of the project: a Flexible Layout Python DSL for expressing tiling, partitioning, data movement, and kernel structure at a high level.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1941889. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadEditBashGrepGlobAgentWriteFrom allowed-tools in the SKILL.md frontmatter.
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonsqlite3wgetFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom 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.
Kernel Trace Analysis loads about 5k tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 1,708 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.
allowed-tools: Read, Edit, Bash, Grep, Glob, Agent, WriteAutomated 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); the scripts in this folder 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,708 words (~5,038 tokens).
“Profile and analyze GPU kernel ATT traces to identify stall hotspots and produce an optimization plan.”
SKILL.md and 2 other files (scripts) in .claude/skills/kernel-trace-analysis of ROCm/FlyDSL.
Open the folder on GitHubat commit 1941889
Kernel Trace Analysis 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 |
|---|---|---|---|---|---|---|
| Kernel Trace Analysis this skillROCm/FlyDSL | 287 | — | ~5k | Automated safety check: Notes | Custom licence | |
| Observe Traceruvnet/ruflo | 74k | — | ~522 | Automated safety check: Notes | MIT | |
| Metal Kernelpytorch/pytorch | 104k | — | ~4.9k | Automated safety check: Pass | Custom licence | |
| Dotnet Trace Collectdotnet/skills | 5.6k | 2 repos | ~6.1k | Automated safety check: Pass | MIT | |
| Optimize For GPUK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Acreadiness Generate Instructionsgithub/awesome-copilot | 40k | 1 repos | ~2.1k | Automated safety check: Pass | MIT |
ruvnet/ruflo
Trace agent execution by collecting spans and building a trace tree for a task
pytorch/pytorch
Write Metal/MPS kernels for PyTorch operators. An agent skill from pytorch/pytorch.
dotnet/skills
Guide developers through capturing diagnostic artifacts to diagnose production .NET performance issues.
K-Dense-AI/scientific-agent-skills
GPU-accelerates scientific Python on NVIDIA hardware and verifies that the result is correct and faster.
github/awesome-copilot
Generate tailored AI agent instruction files via AgentRC instructions command.
sgl-project/sglang
Step-by-step tutorial for adding a new lightweight JIT CUDA kernel to sglang.kernels JIT infrastructure and public operator groups
ROCm/FlyDSL
Tune and analyse a FlyDSL kernel at the LLVM level: pick a compile hint, function attribute, or AMDGPU backend flag, then PROVE it reached codegen.
ROCm/FlyDSL
Detect per-kernel GPU resource regressions (VGPR, SGPR, register spills, scratch, static LDS) by diffing the final ISA before and after a change, using its isaresourcetable.py helper.
ROCm/FlyDSL
Review a FlyDSL PR, commit, branch, kernel, or consuming module for API-stability compliance.
ROCm/FlyDSL
Connect to a remote host via SSH and build a Docker image with rocprofv3, aiter, and FlyDSL.
ROCm/FlyDSL
Debug FlyDSL GPU kernels that produce NaN, inf, wrong results, or crash.
ROCm/FlyDSL
Guided step-by-step wizard for producing a new FlyDSL GPU kernel from a requirement: classify the kernel type, pick a skeleton, fill in compute, add control flow / sync / LDS, then test on GPU.
Profile GPU kernels using rocprofv3 to collect ATT instruction-level traces, then analyze the trace data using hotspotanalyzer.py to identify top-K stall hotspots (VMEM-load, VMEM-wait…. Kernel Trace Analysis is an agent skill from ROCm/FlyDSL.py to identify top-K stall hotspots (VMEM-load, VMEM-wait, LDS/SMEM-wait, barrier, MFMA stalls) mapped back to source lines, and produce an actionable optimization plan.
Run `npx skills add ROCm/FlyDSL --skill kernel-trace-analysis -a claude-code`. Or copy the skill folder (.claude/skills/kernel-trace-analysis in ROCm/FlyDSL) into .claude/skills/kernel-trace-analysis in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ROCm/FlyDSL --skill kernel-trace-analysis -a codex`. Or copy the skill folder (.claude/skills/kernel-trace-analysis in ROCm/FlyDSL) into .agents/skills/kernel-trace-analysis 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 ROCm/FlyDSL --skill kernel-trace-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kernel-trace-analysis, .gemini/skills/kernel-trace-analysis, .github/skills/kernel-trace-analysis and .opencode/skills/kernel-trace-analysis in your project.
Going by SKILL.md and its folder, Kernel Trace Analysis needs Python for the scripts in its folder and the command-line tools its instructions call (python, sqlite3 and wget). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Edit, Bash, Grep, Glob, Agent, Write.
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Kernel Trace Analysis has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 5k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Kernel Trace Analysis: Observe Trace (ruvnet/ruflo, 74k stars), Metal Kernel (pytorch/pytorch, 104k stars), Dotnet Trace Collect (dotnet/skills, 5.6k stars) and Optimize For GPU (K-Dense-AI/scientific-agent-skills, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ROCm (a GitHub organization) maintains it in ROCm/FlyDSL, which has 287 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.
Source: ROCm/FlyDSL on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.