Borrowing it
Nothing to install: this file belongs to tile-ai/tilelang-ascend. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tile-ai/tilelang-ascend/ascendc_pto/.agents/skills/tilelang-pass-workflow-analyzer/SKILL.mdgit clone --depth 1 https://github.com/tile-ai/tilelang-ascendWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tile-ai/tilelang-ascend/tilelang-pass-workflow-analyzer)<a href="https://agentmods.dev/skills/tile-ai/tilelang-ascend/tilelang-pass-workflow-analyzer"><img src="https://agentmods.dev/badge/skills/tile-ai/tilelang-ascend/tilelang-pass-workflow-analyzer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tile-ai/tilelang-ascend/tilelang-pass-workflow-analyzer"><img src="https://agentmods.dev/badge/skills/tile-ai/tilelang-ascend/tilelang-pass-workflow-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00098 | $0.02546 |
| Opus 5 | $0.00049 | $0.01273 |
| Sonnet 5 | $0.00020 | $0.00509 |
| Haiku 4.5 | $0.00010 | $0.00255 |
Grade A, and why
tilelang-pass-workflow-analyzer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 用于：
- 串联 Pass 关系 - 展示 Pass 之间的依赖关系和数据流传递
- 解释 Pipeline 架构 - 说明两阶段编译流程及其设计原理
- 定位新 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 |
展示依赖关系图，说明数据传递 |
| 添加新 Pass | references/new-pass-placement-guide.md |
分析 Pass 功能特征，给出定位建议 |
| 查询特定阶段 | 根据阶段名称查找 | 定位到具体 Pass，展示上下游关系 |
Step 3: 提供分析报告
输出格式：
# 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 Scope | buffer annotations | AscendInferBufferScope |
CrossCorePipeline, CombineCV |
| Buffer Shapes | buffer_shapess |
CollectBufferShapes |
AscendMemoryPlanning |
| Address Map | address_map |
AscendMemoryPlanning |
AscendSyncInsert |
| Size Map | size_map |
AscendMemoryPlanning |
AscendSyncInsert |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 283 lines · 98 tokens per session scan A 6fdf916c9494
tilelang-pass-workflow-analyzer is a skill published in the GitHub repository tile-ai/tilelang-ascend (363 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 2,546 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…