Agent skill

Tilelang Pass Workflow Analyzer

by tile-ai in tile-ai/tilelang-ascend

TileLang Ascend Pass 工作流分析。用于理解 Pass 之间的关系、执行顺序、数据依赖,以及帮助定位新 Pass 应该在哪里添加。触发时机:用户询问 Pass pipeline、Pass 执行顺序、Pass 之间的关系、如何添加新 Pass、Pass 依赖关系、"Pass 工作流"、"Pass 顺序"、"在哪里加 Pass" 等关键词时。

MITAuto-check passed

Install Tilelang Pass Workflow Analyzer

skills CLI
$ npx skills add tile-ai/tilelang-ascend --skill tilelang-pass-workflow-analyzer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tile-ai/tilelang-ascend tilelang-pass-workflow-analyzer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tile-ai/tilelang-ascend.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/tilelang-pass-workflow-analyzer .claude/skills/tilelang-pass-workflow-analyzer && rm -rf skills-src

Use ~/.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/

Facts

Skill name
tilelang-pass-workflow-analyzer
GitHub stars
400
Token cost
~1.4k tokens
SKILL.md length
419 words
Files
5 (incl. references)
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

TileLang Ascend Pass 工作流分析。用于理解 Pass 之间的关系、执行顺序、数据依赖,以及帮助定位新 Pass 应该在哪里添加。触发时机:用户询问 Pass pipeline、Pass 执行顺序、Pass 之间的关系、如何添加新 Pass、Pass 依赖关系、"Pass 工作流"、"Pass 顺序"、"在哪里加 Pass" 等关键词时。

  • Works in 3 steps: 识别用户意图 → 选择合适的分析方式 → 提供分析报告
  • SKILL.md covers ⭐ 核心约束:分阶段信息获取, 核心目标, 工作流程 and 两阶段 Pipeline 架构概要, plus 6 more sections
  • Calls python

What it does

Tilelang Pass Workflow Analyzer is an agent skill from tile-ai/tilelang-ascend. TileLang Ascend Pass 工作流分析。用于理解 Pass 之间的关系、执行顺序、数据依赖,以及帮助定位新 Pass 应该在哪里添加。触发时机:用户询问 Pass pipeline、Pass 执行顺序、Pass 之间的关系、如何添加新 Pass、Pass 依赖关系、"Pass 工作流"、"Pass 顺序"、"在哪里加 Pass" 等关键词时。

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `evals/evals.json`, `references/new-pass-placement-guide.md` and `references/pass-dependency-graph.md`).

The repository describes itself as: Ascend TileLang adapter. The licence is MIT.

Example prompts

  • “Pass 工作流”
  • “Pass 顺序”
  • “在哪里加 Pass”
  • “/tilelang-pass-workflow-analyzer”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. 识别用户意图
  2. 选择合适的分析方式
  3. 提供分析报告

What it can do on your machine

Read from SKILL.md and the folder at commit 3d17c28. 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

Tilelang Pass Workflow Analyzer loads about 1.4k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 419 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

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

The full file from tile-ai/tilelang-ascend at commit 3d17c28, republished under its MIT licence (© tile-ai). 419 words, ~1,438 tokens.

Download SKILL.mdSave it as .claude/skills/tilelang-pass-workflow-analyzer/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
tilelang-pass-workflow-analyzer
description
TileLang Ascend Pass 工作流分析。用于理解 Pass 之间的关系、执行顺序、数据依赖,以及帮助定位新 Pass 应该在哪里添加。触发时机:用户询问 Pass pipeline、Pass 执行顺序、Pass 之间的关系、如何添加新 Pass、Pass 依赖关系、"Pass 工作流"、"Pass 顺序"、"在哪里加 Pass" 等关键词时。

TileLang Pass 工作流分析 Skill

⭐ 核心约束:分阶段信息获取

严格遵守以下信息获取优先级:

查询阶段信息来源工具使用
首次回答✅ 优先使用 reference 文件read(references/*.md)
用户追问深入细节✅ 读取源码补充read(tilelang/engine/phase.py)

执行规则:

用户首次提问 Pass 工作流
  ↓
1. 立即读取 reference 文件(pass-pipeline-overview.md / pass-dependency-graph.md)
  ↓
2. 基于 reference 信息生成报告(足够回答 90% 的查询)
  ↓
3. 仅在用户追问"具体实现"、"源码细节"时才读取源码

禁止行为:

  • ❌ 首次回答就读取源码文件
  • ❌ 忽略 reference 文件中的已有信息
  • ❌ 首次回答就并行读取 reference 和源码

核心目标

这个 skill 用于:

  1. 串联 Pass 关系 - 展示 Pass 之间的依赖关系和数据流传递
  2. 解释 Pipeline 架构 - 说明两阶段编译流程及其设计原理
  3. 定位新 Pass - 帮助用户确定新 Pass 应该添加在 Pipeline 的哪个位置

与 tilelang-pass-analyzer 的区别:

  • tilelang-pass-analyzer:侧重于单个 Pass 的功能、原理、实现细节
  • tilelang-pass-workflow-analyzer:侧重于 Pass 之间的关系、整体工作流、新 Pass 定位

工作流程

当用户提出与 Pass 工作流相关的询问时,按照以下步骤响应:

Step 1: 识别用户意图

判断用户是想要:

  • 了解整体架构 → 提供 Pipeline overview
  • 理解 Pass 关系 → 展示依赖关系图
  • 添加新 Pass → 提供定位指南和建议
  • 查询特定阶段 → 定位到具体阶段并解释
Step 2: 选择合适的分析方式

根据意图,使用以下工具:

用户意图参考文档分析方式
了解整体架构references/pass-pipeline-overview.md展示两阶段架构图,解释设计原理
理解 Pass 关系references/pass-dependency-graph.md展示依赖关系图,说明数据传递
添加新 Passreferences/new-pass-placement-guide.md分析 Pass 功能特征,给出定位建议
查询特定阶段根据阶段名称查找定位到具体 Pass,展示上下游关系
Step 3: 提供分析报告

输出格式:

markdown
# Pass 工作流分析报告

## 用户问题
[用户的具体问题]

## 分析结果

### [根据意图提供对应内容]

### 关键要点
- [要点 1]
- [要点 2]

### 建议操作
[如果用户要添加新 Pass,给出具体建议]

两阶段 Pipeline 架构概要

TileLang-Ascend 采用两阶段编译流程:

Python DSL (@tilelang.jit)
    ↓
[Phase 1: LowerAndLegalize] ← 前端标准化、Lowering
    - 目标:将高级 DSL 转换为标准化 TIR
    - 特点:语义保持、平台无关优化
    ↓
[Phase 2: OptimizeForTarget] ← 后端优化、平台特化
    - 目标:针对 Ascend 硬件特性的优化
    - 特点:硬件相关、性能导向
    ↓
CANN 工具链 → NPU 执行

详细架构请查阅: references/pass-pipeline-overview.md

Pass 依赖关系核心概念

数据传递方式

Pass 之间通过 PrimFunc attrs 传递数据:

数据名称Attr 键产生 Pass消费 Pass
Buffer Scopebuffer annotationsAscendInferBufferScopeCrossCorePipeline, CombineCV
Buffer Shapesbuffer_shapessCollectBufferShapesAscendMemoryPlanning
Address Mapaddress_mapAscendMemoryPlanningAscendSyncInsert
Size Mapsize_mapAscendMemoryPlanningAscendSyncInsert

详细依赖关系请查阅: references/pass-dependency-graph.md

新 Pass 定位指南核心原则

定位原则

添加新 Pass 时,遵循以下原则:

  1. 功能归属 - Pass 的功能属于哪个阶段?

    • 前端 Lowering → Phase 1 (LowerAndLegalize)
    • 后端优化 → Phase 2 (OptimizeForTarget)
  2. 数据依赖 - Pass 需要哪些输入数据?

    • 识别上游 Pass 产生的 attrs
    • 确保上游 Pass 已经执行
  3. 输出供给 - Pass 产生哪些输出数据?

    • 识别下游 Pass 需要的 attrs
    • 确保下游 Pass 可以访问
  4. 语义范围 - Pass 是平台无关还是平台特定?

    • 平台无关 → Phase 1
    • Ascend 特定 → Phase 2
典型定位场景
Pass 功能特征推荐位置理由
IR 合法化检查Phase 1 末尾确保 lowered IR 正确性
新 Tile 操作 loweringPhase 1,LowerTileOp 后紧跟核心 lowering pass
内存优化Phase 2,AscendStorageRewrite 后利用 memory planning 信息
同步优化Phase 2,AscendSyncInsert 前为 sync insert 提供信息

详细定位指南请查阅: references/new-pass-placement-guide.md

Show full SKILL.md (167 more words)Show less

参考资料

当需要详细信息时,查阅以下文档:

  • Pipeline 架构详解:references/pass-pipeline-overview.md(两阶段架构、每个阶段的 Pass 列表、设计原理)
  • 依赖关系图:references/pass-dependency-graph.md(数据流、依赖链、关键 Pass 之间的关系)
  • 新 Pass 定位指南:references/new-pass-placement-guide.md(定位原则、典型场景、案例分析)
  • 已有 Pass 注册表:.agents/skills/tilelang-pass-analyzer/references/pass-registry-ascend.md(所有 Pass 的详细信息)

输出报告模板

当用户询问 Pass 工作流时,使用以下模板生成报告:

markdown
# Pass 工作流分析报告

## 问题类型
[整体架构 / Pass 关系 / 新 Pass 定位 / 特定阶段查询]

## 核心分析

### [根据问题类型提供对应分析]

#### [具体分析内容]
- [要点 1]
- [要点 2]
- [要点 3]

## 数据流分析

### 输入依赖
- [上游 Pass 1]: [提供的数据 1]
- [上游 Pass 2]: [提供的数据 2]

### 输出供给
- [下游 Pass 1]: [需要的数据 1]
- [下游 Pass 2]: [需要的数据 2]

## 定位建议

### 推荐位置
[具体位置描述,如 "Phase 2,在 Pass X 和 Pass Y 之间"]

### 理由
1. [理由 1]
2. [理由 2]

### 需要注意的依赖
- [依赖说明 1]
- [依赖说明 2]

## 实现建议

### 参考实现
可以参考以下 Pass 的实现:
- [Pass A]: [文件路径]
- [Pass B]: [文件路径]

### 关键步骤
1. C++ 实现:[说明]
2. Python Wrapper:[说明]
3. Pipeline 集成:[说明]

## 相关文件路径
- Pipeline 定义:`tilelang/engine/phase.py`
- Pass 注册:`src/transform/*.cc`
- Python API:`tilelang/transform/__init__.py`

使用示例

示例 1: 用户询问整体架构

用户问题: "整个 Pass pipeline 是怎么组织的?"

响应策略:

  1. 读取 references/pass-pipeline-overview.md
  2. 展示两阶段架构图
  3. 解释 Phase 1 和 Phase 2 的设计原理
  4. 提供关键 Pass 的简要说明
示例 2: 用户询问 Pass 关系

用户问题: "AscendMemoryPlanning 和 AscendSyncInsert 有什么关系?"

响应策略:

  1. 读取 references/pass-dependency-graph.md
  2. 展示数据流:AscendMemoryPlanning → address_map → AscendSyncInsert
  3. 解释依赖关系:Sync Insert 需要 Memory Planning 提供的地址映射
  4. 说明如果要在它们之间添加新 Pass,需要注意数据传递
示例 3: 用户想添加新 Pass

用户问题: "我想加一个 Pass 来优化 L0C buffer 的数据布局,应该加在哪里?"

响应策略:

  1. 读取 references/new-pass-placement-guide.md
  2. 分析 Pass 功能特征:
    • 功能:优化 buffer 数据布局
    • 依赖:需要知道 buffer scope (L0C)
    • 平台:Ascend 特定
  3. 推荐位置:Phase 2,在 AscendStorageRewrite 后
  4. 理由:
    • AscendStorageRewrite 已经完成存储优化
    • 此时 buffer scope 和 shape 信息已经完备
    • 属于 Ascend 后端优化范畴
  5. 给出实现建议和参考 Pass

注意事项

  1. 区分单个 Pass 分析 vs 工作流分析

    • 用户询问单个 Pass 功能 → 使用 tilelang-pass-analyzer skill
    • 用户询问 Pass 关系/工作流 → 使用此 skill
  2. 优先展示关键信息

    • 避免一次性输出过多细节
    • 先展示概要,再根据用户追问提供详细信息
  3. 定位建议需明确

    • 提供具体位置(如 "Phase 2,第 X 步,在 Pass Y 之后")
    • 解释理由,不要只给出结论
  4. 关联已有文档

    • 充分利用 tilelang-pass-analyzer skill 的注册表文档
    • 当用户询问特定 Pass 时,引导其查看详细注册信息

© tile-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in .agents/skills/tilelang-pass-workflow-analyzer of tile-ai/tilelang-ascend.

  • SKILL.md
  • evals/evals.json
  • references/new-pass-placement-guide.md
  • references/pass-dependency-graph.md
  • references/pass-pipeline-overview.md

Open the folder on GitHubat commit 3d17c28

Compare with similar skills

Tilelang Pass Workflow Analyzer 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.

Tilelang Pass Workflow Analyzer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tilelang Pass Workflow Analyzer this skilltile-ai/tilelang-ascend400—~1.4kAutomated safety check: PassMIT
Agent Code Analyzerruvnet/ruflo74k3 repos~1.5kAutomated safety check: PassMIT
Agent Pagerank Analyzerruvnet/ruflo74k3 repos~2.9kAutomated safety check: PassMIT
Agent Performance Analyzerruvnet/ruflo74k2 repos~1.3kAutomated safety check: PassMIT
Diff Analyzeruvnet/ruflo74k—~450Automated safety check: NotesMIT
Analyze GitHub Flakeflutter/flutter179k—~1.1kAutomated safety check: PassBSD-3-Clause

Similar skills

  • Agent skill for code-analyzer - invoke with $agent-code-analyzer

    74k GitHub starsUsed in 3 repos~1.5k tokens
    DevelopmentAuto-check passed
  • Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer

    74k GitHub starsUsed in 3 repos~2.9k tokens
    Auto-check passed
  • Agent skill for performance-analyzer - invoke with $agent-performance-analyzer

    74k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check passed
  • Diff Analyze

    ruvnet/ruflo

    Analyze git diffs for risk scoring, reviewer recommendations, and change classification.

    74k GitHub stars~450 tokensUpdated today
    DevelopmentAuto-check: notes
  • Analyze GitHub Flake

    flutter/flutter

    Expertise in analyzing flake github issues in the flutter/flutter repository.

    179k GitHub stars~1.1k tokensUpdated today
    MobileAuto-check passed
  • Agent skill for analyze-code-quality - invoke with $agent-analyze-code-quality

    74k GitHub starsUsed in 2 repos~1.2k tokens
    DevelopmentAuto-check passed

More from tile-ai/tilelang-ascend

All 20 skills in this repo
  • Tilelang Submodule Pull

    tile-ai/tilelang-ascend

    Automatically pull tilelang repository and its third-party code.

    400 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Tilelang Debug Helper

    tile-ai/tilelang-ascend

    How to add debugging capabilities to TileLang Ascend example operators.

    400 GitHub stars~1.7k tokensUpdated today
    Auto-check: notes
  • Tilelang A5 Sim Convert

    tile-ai/tilelang-ascend

    将 tilelang example 脚本转换为可在 A5 camodel 仿真器上直接运行的版本。输入脚本路径,输出一个新的 sim.py 文件,不覆盖原始文件。触发:仿真运行、camodel、A5 仿真、sim 模式、转换脚本为仿真、不需要 NPU 跑 kernel、simulate A5。

    400 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Tilelang Env Check

    tile-ai/tilelang-ascend

    TileLang-Ascend 环境检查与配置验证技能。检查代码仓库完整性、编译安装状态、环境变量配置,并运行简单测试验证环境。发现问题会自动调用相关 skill 进行修复,并按依赖顺序重新执行后续步骤。触发关键词:"环境检查"、"检查环境"、"验证环境"、"环境配置"、"环境搭建"、"env check"、"check environment"、"verify…

    400 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Tilelang Op Test Design

    tile-ai/tilelang-ascend

    TileLang-Ascend 算子测试设计技能。支持多种场景:(1) 从 design.md 设计测试配置 (2) 从 examples/{op}/.py 补充测试 (3) 手动提供算子信息生成测试 (4) 测试覆盖率分析。理解算子实现逻辑后智能判断测试策略。触发:设计算子测试、生成测试用例、补充测试、测试覆盖率不足。

    400 GitHub stars~5.6k tokensUpdated today
    Auto-check passed
  • Tilelang Review

    tile-ai/tilelang-ascend

    检查代码格式是否符合 CI 规则。自动检测并安装缺失工具(ruff、clang-format),先运行检查生成报告,使用醒目方式询问用户后,仅在用户同意时执行修复。工作流程:检测环境→自动安装缺失工具→运行检查→生成报告→醒目询问→用户确认→执行修复。使用此技能当:用户要求"格式检查"、"格式化代码"、"代码格式化"、"检查代码格式"、"代码…

    400 GitHub stars~2.8k tokensUpdated today
    Auto-check: notes

Questions about Tilelang Pass Workflow Analyzer

What does Tilelang Pass Workflow Analyzer do?

TileLang Ascend Pass 工作流分析。用于理解 Pass 之间的关系、执行顺序、数据依赖,以及帮助定位新 Pass 应该在哪里添加。触发时机:用户询问 Pass pipeline、Pass 执行顺序、Pass 之间的关系、如何添加新 Pass、Pass 依赖关系、"Pass 工作流"、"Pass 顺序"、"在哪里加 Pass" 等关键词时。. Tilelang Pass Workflow Analyzer is an agent skill from tile-ai/tilelang-ascend.

How do I install Tilelang Pass Workflow Analyzer in Claude Code?

Run `npx skills add tile-ai/tilelang-ascend --skill tilelang-pass-workflow-analyzer -a claude-code`. Or copy the skill folder (.agents/skills/tilelang-pass-workflow-analyzer in tile-ai/tilelang-ascend) into .claude/skills/tilelang-pass-workflow-analyzer in your project. Claude Code loads it when a task matches its description.

How do I install Tilelang Pass Workflow Analyzer in Codex?

Run `npx skills add tile-ai/tilelang-ascend --skill tilelang-pass-workflow-analyzer -a codex`. Or copy the skill folder (.agents/skills/tilelang-pass-workflow-analyzer in tile-ai/tilelang-ascend) into .agents/skills/tilelang-pass-workflow-analyzer in your project. Codex loads it when a task matches its description.

Can I use Tilelang Pass Workflow Analyzer 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 tile-ai/tilelang-ascend --skill tilelang-pass-workflow-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tilelang-pass-workflow-analyzer, .gemini/skills/tilelang-pass-workflow-analyzer, .github/skills/tilelang-pass-workflow-analyzer and .opencode/skills/tilelang-pass-workflow-analyzer in your project.

What does Tilelang Pass Workflow Analyzer need to run?

Going by SKILL.md and its folder, Tilelang Pass Workflow Analyzer needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Tilelang Pass Workflow Analyzer 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 Tilelang Pass Workflow Analyzer 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 Tilelang Pass Workflow Analyzer use?

Tilelang Pass Workflow Analyzer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tilelang Pass Workflow Analyzer use?

About 1.4k tokens (SKILL.md is roughly 5.8k 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 12k tokens, read only when the agent opens those files.

What are the alternatives to Tilelang Pass Workflow Analyzer?

Skills that share tags, products or a category with Tilelang Pass Workflow Analyzer: Agent Code Analyzer (ruvnet/ruflo, 74k stars), Agent Pagerank Analyzer (ruvnet/ruflo, 74k stars), Agent Performance Analyzer (ruvnet/ruflo, 74k stars) and Diff Analyze (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tilelang Pass Workflow Analyzer?

tile-ai (a GitHub organization) maintains it in tile-ai/tilelang-ascend, which has 400 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 8, 2026.

Source: tile-ai/tilelang-ascend on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.