Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Draft TileLang operators using JIT, tensor contracts, tiled computation, and reusable kernel patterns.
Install Writing Tilelang Kernels
$ npx skills add sablin39/tilelang-cuda-skills --skill writing-tilelang-kernels -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sablin39/tilelang-cuda-skills writing-tilelang-kernels --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/writing-tilelang-kernels .claude/skills/writing-tilelang-kernels && 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 "writing-tilelang-kernels" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-kernels into .claude/skills/writing-tilelang-kernels/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tilelang-kernels", 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/writing-tilelang-kernelsType 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 writing-tilelang-kernels -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sablin39/tilelang-cuda-skills writing-tilelang-kernels --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/writing-tilelang-kernels .agents/skills/writing-tilelang-kernels && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-tilelang-kernels" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-kernels into .agents/skills/writing-tilelang-kernels/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tilelang-kernels", 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 writing-tilelang-kernels -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sablin39/tilelang-cuda-skills writing-tilelang-kernels --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/writing-tilelang-kernels .cursor/skills/writing-tilelang-kernels && 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 "writing-tilelang-kernels" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-kernels into .cursor/skills/writing-tilelang-kernels/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tilelang-kernels", 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/writing-tilelang-kernels--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 writing-tilelang-kernels -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sablin39/tilelang-cuda-skills writing-tilelang-kernels --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/writing-tilelang-kernels .gemini/skills/writing-tilelang-kernels && 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 "writing-tilelang-kernels" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-kernels into .gemini/skills/writing-tilelang-kernels/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tilelang-kernels", 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 writing-tilelang-kernelsInstalls 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 writing-tilelang-kernels -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/writing-tilelang-kernels .github/skills/writing-tilelang-kernels && 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 "writing-tilelang-kernels" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-kernels into .github/skills/writing-tilelang-kernels/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tilelang-kernels", 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 writing-tilelang-kernels -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 writing-tilelang-kernels --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/writing-tilelang-kernels .opencode/skills/writing-tilelang-kernels && 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 "writing-tilelang-kernels" agent skill from https://github.com/sablin39/tilelang-cuda-skills/tree/main/skills/tilelang/writing-tilelang-kernels into .opencode/skills/writing-tilelang-kernels/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-tilelang-kernels", 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
writing-tilelang-kernels- GitHub stars
- 145
- Token cost
- ~1.3k tokens
- SKILL.md length
- 539 words
- Files
- 5 (incl. references)
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- None found
At a glance
Draft TileLang operators using JIT, tensor contracts, tiled computation, and reusable kernel patterns.
- Works in 5 steps: Reuse the supplied PyTorch reference and… → Use the baseline findings to select the… → Define the grid with T.Kernel, tile… → …
- Choosing between eager and PrimFunc-factory programming styles
- SKILL.md covers Choose the programming model, Draft the computation, Inspect before adding complexity and Completion evidence
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Writing Tilelang Kernels is an agent skill from sablin39/tilelang-cuda-skills. Draft TileLang operators using JIT, tensor contracts, tiled computation, and reusable kernel patterns. Use for new kernels, ports, dynamic shapes, and choosing between eager and PrimFunc-factory programming styles.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/api-quick-reference.md`, `references/kernel-templates.md` and `references/language-docs.md`).
It sits in Development. The repository describes itself as: Skills for writing tilelang and debugging with CUDA toolkits.
When your agent uses it
- Choosing between eager and PrimFunc-factory programming styles
Example prompts
- “/writing-tilelang-kernels”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Reuse the supplied PyTorch reference and its contract; create a reference
- Use the baseline findings to select the closest pattern from
- Define the grid with T.Kernel, tile bounds, and memory scopes. Fragments
- Use T.copy, T.Parallel, and tile reductions/GEMM for the main algorithm.
- Validate a small case, representative sizes, tails, and supported strides.
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
No scripts in the folder and no shell commands in SKILL.md.
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
Writing Tilelang Kernels loads about 1.3k tokens when it runs, and up to ~8.4k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 539 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 539 words (~1,308 tokens).
“Identify the input/output contract: mathematical operation, shapes, dtypes, strides, device, mutation, and accuracy. Use the user's active environment and inspect the installed TileLang version before selecting newer APIs.”
- name
- writing-tilelang-kernels
Files
SKILL.md and 4 other files (references) in skills/tilelang/writing-tilelang-kernels of sablin39/tilelang-cuda-skills.
- SKILL.md
- references/api-quick-reference.md
- references/kernel-templates.md
- references/language-docs.md
- references/tilelang-examples.md
Open the folder on GitHubat commit 502a514
Compare with similar skills
Writing Tilelang Kernels 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 |
|---|---|---|---|---|---|---|
| Writing Tilelang Kernels this skillsablin39/tilelang-cuda-skills | 145 | — | ~1.3k | Automated safety check: Pass | None | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
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.
Debugging Tilelang Programs
sablin39/tilelang-cuda-skills
Diagnose TileLang compilation, host argument, memory-liveness, runtime, and numerical failures.
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.
Related
Categories
Questions about Writing Tilelang Kernels
What does Writing Tilelang Kernels do?
Draft TileLang operators using JIT, tensor contracts, tiled computation, and reusable kernel patterns. Writing Tilelang Kernels is an agent skill from sablin39/tilelang-cuda-skills. Draft TileLang operators using JIT, tensor contracts, tiled computation, and reusable kernel patterns.
When should I use Writing Tilelang Kernels?
Writing Tilelang Kernels fits situations like: choosing between eager and PrimFunc-factory programming styles.
How do I install Writing Tilelang Kernels in Claude Code?
Run `npx skills add sablin39/tilelang-cuda-skills --skill writing-tilelang-kernels -a claude-code`. Or copy the skill folder (skills/tilelang/writing-tilelang-kernels in sablin39/tilelang-cuda-skills) into .claude/skills/writing-tilelang-kernels in your project. Claude Code loads it when a task matches its description.
How do I install Writing Tilelang Kernels in Codex?
Run `npx skills add sablin39/tilelang-cuda-skills --skill writing-tilelang-kernels -a codex`. Or copy the skill folder (skills/tilelang/writing-tilelang-kernels in sablin39/tilelang-cuda-skills) into .agents/skills/writing-tilelang-kernels in your project. Codex loads it when a task matches its description.
Can I use Writing Tilelang Kernels 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 writing-tilelang-kernels -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-tilelang-kernels, .gemini/skills/writing-tilelang-kernels, .github/skills/writing-tilelang-kernels and .opencode/skills/writing-tilelang-kernels in your project.
What does Writing Tilelang Kernels need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing Tilelang Kernels is instructions for the agent only. Our summary lists: Python 3.
Does Writing Tilelang Kernels 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 Writing Tilelang Kernels 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 Writing Tilelang Kernels use?
No licence was found for Writing Tilelang Kernels or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Writing Tilelang Kernels use?
About 1.3k tokens (SKILL.md is roughly 5.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 7.1k tokens, read only when the agent opens those files.
What are the alternatives to Writing Tilelang Kernels?
Skills that share tags, products or a category with Writing Tilelang Kernels: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Tilelang Kernels?
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.