Individual skill

tune-triton-ascend-kernels

Add standard or advanced autotuning to Triton-Ascend kernels, define shape keys and candidate meta-parameters, and structure kernels so automatic split and tiling analysis can recognize their axes. Use when an agent needs to benchmark block-size or multibuffer choices, use configs=[] for generated vector-kernel candidates, or diagnose why Triton-Ascend autotune cannot infer a tunable axis.

skills/tune-triton-ascend-kernels/SKILL.md

Read pinned source

Source commit 4ab5ee7adf47755ecd42723f55f4c58e38be95a7

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
189
Repository last updated
Aug 15, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Tune Triton-Ascend Kernels

## Goal

Select a correct kernel configuration for each relevant input shape without hardcoding one block size for all workloads.

## Workflow

1. Establish a correct untuned kernel and reference test.
2. Choose standard autotune when candidate configurations are known.
3. Choose advanced autotune when Triton-Ascend should infer vector split or tiling candidates.
4. Put only values that can change the winner in key.
5. Derive the launch grid from meta-parameters and omit tunable meta-parameters at launch.
6. Validate the tuned result, then benchmark representative shapes.