stall — Claude Code skill for GPU stall analysis
This Claude Code skill maps measured stall counters from a .ncu-rep profile to SASS instructions. It helps locate where GPU execution is losing time.
Apache-2.0 ★ 339 updated 2026-11-11
~/.claude/skills/stall/SKILL.mdWhat stall does
The skill turns PC-sampling counters from a .ncu-rep profile into a per-instruction SASS ledger. stall_tools.py prints rows until they account for at least 90% of stall samples, then ends with either STALL-OK or STALL-FAIL.
For plateau diagnosis, the driver runs stall_price_run.py on the best tree; the collection command is python3 notes/stall_price_run.py. Add --pm to collect a PM-sampling timeline in the same job. A student does not run this collection directly and requests a probe with PROBE_REQUEST instead. A locus priced at 1% in the ledger does not count as the bottleneck, even if it looks plausible.
What it helps with
- map
.ncu-repstall samples to SASS instructions - identify loci covering at least 90% of stall samples
- collect counters during plateau diagnosis
- rule out a low-share locus as the bottleneck
Example prompts for the agent
- Analyze
.ncu-repand show which SASS instructions account for the stalls. - Request a probe with
PROBE_REQUESTduring plateau diagnosis. - Add a PM-sampling timeline with
python3 notes/stall_price_run.py --pm.
How to install stall
Manually: put the files in place
~/.claude/skills/stall/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/stall/
Manually: put the files in place
.agents/skills/stall/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/stall/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OpenBMB/ForgeKernel skills/stall2Manually: put the files in place
.github/skills/stall/SKILL.mdPlatform CLI
gemini skills install https://github.com/OpenBMB/ForgeKernel --path skills/stallManually: put the files in place
.devin/skills/stall/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about stall
How do I install stall in Claude Code?
Place SKILL.md at ~/.claude/skills/stall/SKILL.md.
What does the stall skill do?
It maps PC-sampling counters from a .ncu-rep profile to SASS instructions and produces a stall ledger covering at least 90% of samples.
What does stall need to run?
It uses a .ncu-rep profile. Counter collection uses Python 3 with python3 notes/stall_price_run.py; add --pm for a PM-sampling timeline.
Source text
SKILL.md · Apache-2.0
# stall Where the time actually leaks: the measured PC-sampling stall counters of a `.ncu-rep` joined per SASS instruction into a ledger. - `stall_tools.py` -- the ledger. Rows are printed until they cover at least 90% of all stall samples, between `=== STALL LEDGER BEGIN ===` / `=== STALL LEDGER END ===`, and the run ends in exactly one `STALL-OK ...` or `STALL-FAIL reason=...` line. - `stall_price_run.py` -- the frozen collection recipe the driver runs on the best tree at a plateau diagnosis (`python3 notes/stall_price_run.py`, with `--pm` to collect the PM-sampling timeline in the same job). Not a student tool: a student asks for a probe with `PROBE_REQUEST` instead. Read the ledger before naming a bottleneck: a locus the ledger prices at 1% is not the bottleneck however plausible it reads.
© OpenBMB · Apache-2.0 · OpenBMB/ForgeKernel