Iron Proxy Gateway for NanoClaw
nanocoai/nanoclaw
Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.
Capture GPU kernel ATT (Advanced Thread Trace) via rocprofv3 on a remote Docker container or locally.
Install Capture Kernel Trace
$ npx skills add ROCm/FlyDSL --skill capture-kernel-trace -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ROCm/FlyDSL capture-kernel-trace --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/capture-kernel-trace .claude/skills/capture-kernel-trace && 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 "capture-kernel-trace" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/capture-kernel-trace into .claude/skills/capture-kernel-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capture-kernel-trace", 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/capture-kernel-traceType 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 capture-kernel-trace -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ROCm/FlyDSL capture-kernel-trace --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/capture-kernel-trace .agents/skills/capture-kernel-trace && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "capture-kernel-trace" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/capture-kernel-trace into .agents/skills/capture-kernel-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capture-kernel-trace", 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 capture-kernel-trace -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ROCm/FlyDSL capture-kernel-trace --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/capture-kernel-trace .cursor/skills/capture-kernel-trace && 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 "capture-kernel-trace" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/capture-kernel-trace into .cursor/skills/capture-kernel-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capture-kernel-trace", 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/capture-kernel-trace--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 capture-kernel-trace -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ROCm/FlyDSL capture-kernel-trace --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/capture-kernel-trace .gemini/skills/capture-kernel-trace && 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 "capture-kernel-trace" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/capture-kernel-trace into .gemini/skills/capture-kernel-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capture-kernel-trace", 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 capture-kernel-traceInstalls 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 capture-kernel-trace -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/capture-kernel-trace .github/skills/capture-kernel-trace && 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 "capture-kernel-trace" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/capture-kernel-trace into .github/skills/capture-kernel-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capture-kernel-trace", 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 capture-kernel-trace -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 capture-kernel-trace --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/capture-kernel-trace .opencode/skills/capture-kernel-trace && 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 "capture-kernel-trace" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/capture-kernel-trace into .opencode/skills/capture-kernel-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capture-kernel-trace", 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.
Facts
- Skill name
capture-kernel-trace- GitHub stars
- 288
- Token cost
- ~2.5k tokens
- SKILL.md length
- 652 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Capture GPU kernel ATT (Advanced Thread Trace) via rocprofv3 on a remote Docker container or locally.
- Works in 5 steps: Deploy Test Script → Kernel Discovery (if no pattern provided) → Configure input.yaml → …
- Tasks that involve Containers
- SKILL.md covers Arguments, Connection Info, Workflow and Step 1: Deploy Test Script, plus 7 more sections
- Calls ssh, scp and python3
What it does
Capture Kernel Trace is an agent skill from ROCm/FlyDSL. Capture GPU kernel ATT (Advanced Thread Trace) via rocprofv3 on a remote Docker container or locally. Discovers kernel names, configures input.yaml with the target kernelincluderegex, runs rocprofv3 -i input.yaml with FLYDSLDEBUGENABLEDEBUGINFO=1, and downloads the latest uioutputagent directory for analysis. Usage: /capture-kernel-trace <testscript.py [kernelnamepattern]
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Containers. It works with Docker. 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.
When your agent uses it
- Tasks that involve Containers
Example prompts
- “/capture-kernel-trace”
Requirements
- Python 3
- Docker
- Pre-approved tools (allowed-tools): Bash, Read, Write, Edit, Grep, Glob
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Deploy Test Script
- Kernel Discovery (if no pattern provided)
- Configure input.yaml
- Run rocprofv3 with ATT
- Download Trace Output
What it can do on your machine
Read from SKILL.md and the folder at commit 1941889. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadWriteEditGrepGlob
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
sshscppython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use ssh and scp, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Capture Kernel Trace loads about 2.5k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 652 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.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Write, Edit, Grep, Glob
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.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 652 words (~2,492 tokens).
“Capture rocprofv3 ATT traces from a GPU environment (local or remote Docker container), then download the trace output for analysis.”
- name
- capture-kernel-trace
- allowed-tools
- Bash, Read, Write, Edit, Grep, Glob
Files
Just SKILL.md in .claude/skills/capture-kernel-trace of ROCm/FlyDSL.
Open the folder on GitHubat commit 1941889
Compare with similar skills
Capture Kernel Trace 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 |
|---|---|---|---|---|---|---|
| Capture Kernel Trace this skillROCm/FlyDSL | 288 | — | ~2.5k | Automated safety check: Notes | Custom licence | |
| Iron Proxy Gateway for NanoClawnanocoai/nanoclaw | 31k | — | ~4.6k | Automated safety check: Notes | MIT | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| LangBot Deployment Guidelangbot-app/LangBot | 18k | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Build Openshell Mxc WindowsNVIDIA/OpenShell | 15k | — | ~4.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
LangBot Deployment Guide
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
- Official
Build Openshell Mxc Windows
NVIDIA/OpenShell
Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.
Omnigent Docker Compose Deploy
omnigent-ai/omnigent
Brings up the Omnigent server and Postgres as a Docker compose stack on any Docker host, and covers the Dockerfile's runtime and host build targets for extending it to a new platform.
More from ROCm/FlyDSL
All 19 skills in this repoLlvm
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.
Isa Resource Diff
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.
API Stability
ROCm/FlyDSL
Review a FlyDSL PR, commit, branch, kernel, or consuming module for API-stability compliance.
Build Rocm Image
ROCm/FlyDSL
Connect to a remote host via SSH and build a Docker image with rocprofv3, aiter, and FlyDSL.
Debug Flydsl Kernel
ROCm/FlyDSL
Debug FlyDSL GPU kernels that produce NaN, inf, wrong results, or crash.
Flydsl Tile Programming
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.
Related
Works with
Categories
Questions about Capture Kernel Trace
What does Capture Kernel Trace do?
Capture GPU kernel ATT (Advanced Thread Trace) via rocprofv3 on a remote Docker container or locally. Capture Kernel Trace is an agent skill from ROCm/FlyDSL. Capture GPU kernel ATT (Advanced Thread Trace) via rocprofv3 on a remote Docker container or locally.
When should I use Capture Kernel Trace?
Capture Kernel Trace fits situations like: tasks that involve Containers.
How do I install Capture Kernel Trace in Claude Code?
Run `npx skills add ROCm/FlyDSL --skill capture-kernel-trace -a claude-code`. Or copy the skill folder (.claude/skills/capture-kernel-trace in ROCm/FlyDSL) into .claude/skills/capture-kernel-trace in your project. Claude Code loads it when a task matches its description.
How do I install Capture Kernel Trace in Codex?
Run `npx skills add ROCm/FlyDSL --skill capture-kernel-trace -a codex`. Or copy the skill folder (.claude/skills/capture-kernel-trace in ROCm/FlyDSL) into .agents/skills/capture-kernel-trace in your project. Codex loads it when a task matches its description.
Can I use Capture Kernel Trace in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ROCm/FlyDSL --skill capture-kernel-trace -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/capture-kernel-trace, .gemini/skills/capture-kernel-trace, .github/skills/capture-kernel-trace and .opencode/skills/capture-kernel-trace in your project.
What does Capture Kernel Trace need to run?
Going by SKILL.md and its folder, Capture Kernel Trace needs the command-line tools its instructions call (ssh, scp and python3). Our summary lists: Python 3; Docker. Its frontmatter pre-approves these tools: Bash, Read, Write, Edit, Grep, Glob.
Does Capture Kernel Trace access the network?
SKILL.md contains no URLs. Its commands use ssh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Capture Kernel Trace safe to install?
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. Review the folder before installing.
What licence does Capture Kernel Trace use?
Capture Kernel Trace has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Capture Kernel Trace use?
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Capture Kernel Trace?
Skills that share tags, products or a category with Capture Kernel Trace: Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars) and LangBot Deployment Guide (langbot-app/LangBot, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Capture Kernel Trace?
ROCm (a GitHub organization) maintains it in ROCm/FlyDSL, which has 288 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 8, 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.