Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
Diagnose TileLang compilation, host argument, memory-liveness, runtime, and numerical failures.
Install Debugging Tilelang Programs
$ npx skills add sablin39/tilelang-cuda-skills --skill debugging-tilelang-programs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sablin39/tilelang-cuda-skills debugging-tilelang-programs --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/sablin39/tilelang-cuda-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tilelang/debugging-tilelang-programs .claude/skills/debugging-tilelang-programs && 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 "debugging-tilelang-programs" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/debugging-tilelang-programs into .claude/skills/debugging-tilelang-programs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-tilelang-programs", 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/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/debugging-tilelang-programsType 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 sablin39/tilelang-cuda-skills --skill debugging-tilelang-programs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sablin39/tilelang-cuda-skills debugging-tilelang-programs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sablin39/tilelang-cuda-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tilelang/debugging-tilelang-programs .agents/skills/debugging-tilelang-programs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debugging-tilelang-programs" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/debugging-tilelang-programs into .agents/skills/debugging-tilelang-programs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-tilelang-programs", 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 sablin39/tilelang-cuda-skills --skill debugging-tilelang-programs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sablin39/tilelang-cuda-skills debugging-tilelang-programs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sablin39/tilelang-cuda-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tilelang/debugging-tilelang-programs .cursor/skills/debugging-tilelang-programs && 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 "debugging-tilelang-programs" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/debugging-tilelang-programs into .cursor/skills/debugging-tilelang-programs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-tilelang-programs", 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/sablin39/tilelang-cuda-skills.git --path skills/tilelang/debugging-tilelang-programs--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 sablin39/tilelang-cuda-skills --skill debugging-tilelang-programs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sablin39/tilelang-cuda-skills debugging-tilelang-programs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sablin39/tilelang-cuda-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tilelang/debugging-tilelang-programs .gemini/skills/debugging-tilelang-programs && 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 "debugging-tilelang-programs" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/debugging-tilelang-programs into .gemini/skills/debugging-tilelang-programs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-tilelang-programs", 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 sablin39/tilelang-cuda-skills debugging-tilelang-programsInstalls 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 sablin39/tilelang-cuda-skills --skill debugging-tilelang-programs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sablin39/tilelang-cuda-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tilelang/debugging-tilelang-programs .github/skills/debugging-tilelang-programs && 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 "debugging-tilelang-programs" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/debugging-tilelang-programs into .github/skills/debugging-tilelang-programs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-tilelang-programs", 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 sablin39/tilelang-cuda-skills --skill debugging-tilelang-programs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sablin39/tilelang-cuda-skills debugging-tilelang-programs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sablin39/tilelang-cuda-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tilelang/debugging-tilelang-programs .opencode/skills/debugging-tilelang-programs && 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 "debugging-tilelang-programs" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/debugging-tilelang-programs into .opencode/skills/debugging-tilelang-programs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-tilelang-programs", 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
debugging-tilelang-programs- GitHub stars
- 145
- Token cost
- ~1.6k tokens
- SKILL.md length
- 670 words
- Files
- 6 (incl. references)
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- None found
At a glance
Diagnose TileLang compilation, host argument, memory-liveness, runtime, and numerical failures.
- Failing kernels
- SKILL.md covers Select the failing layer, Compilation and host failures, Runtime failures and Numerical failures, plus 2 more sections
- Calls python
- Buffer lifetime
What it does
Debugging Tilelang Programs is an agent skill from sablin39/tilelang-cuda-skills. Diagnose TileLang compilation, host argument, memory-liveness, runtime, and numerical failures. Use for failing kernels, buffer lifetime or shared-memory reuse analysis, generated-code and TVM-pass inspection, lowering traces, layout diagnostics, and minimal reproducers.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/buffer-lifetime-analysis.md`, `references/compiler-tools.md` and `references/debug-tools-doc.md`).
It sits in Development, covering Debugging. The repository describes itself as: Skills for writing tilelang and debugging with CUDA toolkits.
When your agent uses it
- Failing kernels
- Buffer lifetime
- Shared-memory reuse analysis
- Generated-code and TVM-pass inspection
Example prompts
- “/debugging-tilelang-programs”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 502a514. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Debugging Tilelang Programs loads about 1.6k tokens when it runs, and up to ~7.4k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 670 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 passed
The automated check found no risky patterns in SKILL.md.
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 670 words (~1,560 tokens).
“Reproduce with the user's interpreter, command, input contract, and target. Record TileLang/PyTorch/toolkit versions and the full error. Use a fixed seed for numerical comparisons; a seed alone does not eliminate races.”
- name
- debugging-tilelang-programs
Files
SKILL.md and 5 other files (references) in skills/tilelang/debugging-tilelang-programs of sablin39/tilelang-cuda-skills.
- SKILL.md
- references/buffer-lifetime-analysis.md
- references/compiler-tools.md
- references/debug-tools-doc.md
- references/error-catalog.md
- references/interpreting-debug-output.md
Open the folder on GitHubat commit 502a514
Compare with similar skills
Debugging Tilelang Programs 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 |
|---|---|---|---|---|---|---|
| Debugging Tilelang Programs this skillsablin39/tilelang-cuda-skills | 145 | — | ~1.6k | Automated safety check: Pass | None | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Native Data FetchingCherryHQ/cherry-studio-app | 4k | 6 repos | ~2.9k | Automated safety check: Notes | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Aoti Debugpytorch/pytorch | 104k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Herdr Throwaway Reproductionherdrdev/herdr | 43k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
More from sablin39/tilelang-cuda-skills
All 10 skills in this repoTorch Profiling Tilelang Programs
sablin39/tilelang-cuda-skills
Inspect a PyTorch baseline with torch.compile graphs/code and torch.profiler before drafting a custom kernel, then compare TileLang and PyTorch timelines, forward/backward regions, and allocations.
Writing Tilelang Design Docs
sablin39/tilelang-cuda-skills
Write human-facing TileLang design documents for proposed or completed kernel implementations.
Cuda
sablin39/tilelang-cuda-skills
Draft, debug, and measure CUDA kernels and host launch workflows.
Designing With Tilefoundry
sablin39/tilelang-cuda-skills
Describe model or operator HIR with TileFoundry, inspect topology and placement, run static cost analysis, visualize authored dataflow, and check a runtime implementation against its evaluator.
Profiling Tilelang Programs
sablin39/tilelang-cuda-skills
Measure TileLang kernel and workflow performance, choose benchmark or timeline tools, and compare implementations fairly.
Optimizing Tilelang Programs
sablin39/tilelang-cuda-skills
Tune a correct TileLang kernel using measured bottlenecks, tile sizes, layouts, pipelining, fusion, and autotuning.
Related
Categories
Questions about Debugging Tilelang Programs
What does Debugging Tilelang Programs do?
Diagnose TileLang compilation, host argument, memory-liveness, runtime, and numerical failures. Debugging Tilelang Programs is an agent skill from sablin39/tilelang-cuda-skills. Diagnose TileLang compilation, host argument, memory-liveness, runtime, and numerical failures.
When should I use Debugging Tilelang Programs?
Debugging Tilelang Programs fits situations like: failing kernels; buffer lifetime; shared-memory reuse analysis; generated-code and TVM-pass inspection.
How do I install Debugging Tilelang Programs in Claude Code?
Run `npx skills add sablin39/tilelang-cuda-skills --skill debugging-tilelang-programs -a claude-code`. Or copy the skill folder (skills/tilelang/debugging-tilelang-programs in sablin39/tilelang-cuda-skills) into .claude/skills/debugging-tilelang-programs in your project. Claude Code loads it when a task matches its description.
How do I install Debugging Tilelang Programs in Codex?
Run `npx skills add sablin39/tilelang-cuda-skills --skill debugging-tilelang-programs -a codex`. Or copy the skill folder (skills/tilelang/debugging-tilelang-programs in sablin39/tilelang-cuda-skills) into .agents/skills/debugging-tilelang-programs in your project. Codex loads it when a task matches its description.
Can I use Debugging Tilelang Programs 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 sablin39/tilelang-cuda-skills --skill debugging-tilelang-programs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-tilelang-programs, .gemini/skills/debugging-tilelang-programs, .github/skills/debugging-tilelang-programs and .opencode/skills/debugging-tilelang-programs in your project.
What does Debugging Tilelang Programs need to run?
Going by SKILL.md and its folder, Debugging Tilelang Programs needs the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Debugging Tilelang Programs access the network?
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.
Is Debugging Tilelang Programs safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Debugging Tilelang Programs use?
No licence was found for Debugging Tilelang Programs or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Debugging Tilelang Programs use?
About 1.6k tokens (SKILL.md is roughly 6.2k 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 5.8k tokens, read only when the agent opens those files.
What are the alternatives to Debugging Tilelang Programs?
Skills that share tags, products or a category with Debugging Tilelang Programs: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debugging Tilelang Programs?
sablin39 (a GitHub user) maintains it in sablin39/tilelang-cuda-skills, which has 145 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 15, 2026.
Source: sablin39/tilelang-cuda-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.