agentleFS
vllm-projectvllm-project/vllm-omni/.claude/skills/dit-npu-fusion-analysis/SKILL.md

dit-npu-fusion-analysis

Skill7.8k starsChanged 3 days agoApache-2.0View on GitHub

Route Ascend NPU diffusion model and operator optimization to MindIE-SD skills. Use for NPU DiT fusion, profiling, kernel/pattern work and related parallelism, VAE or host bottlenecks. Supply Omni context and load the applicable external skill. CUDA/ROCm tuning, pure AR optimization and runner-version upgrades use their own workflows.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about vllm-project/vllm-omni

The biggest 5 of 51 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 51

Talked about on GitHub and Hacker News (51 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the task's MindIE-SD checkout, or an existing sibling MindIE-SD checkout.

    line 15
  2. Very specific:

    Read its AGENTS.md and .agents/README.md, then the selected SKILL.md and required references.

    line 18
  3. Distinctive:

    If GitCode is unavailable, use the official GitHub dev skill index and GitHub dev tree.

    line 23
  4. Distinctive:

    Follow the actual index if names changed.

    line 26
  5. Distinctive:

    If required guidance is unavailable, name the missing resource and continue useful Omni source/configuration inspection.

    line 27
  6. Distinctive:

    Keep Omni, MindIE-SD and installed provider sources distinct.

    line 61
  7. Distinctive:

    Do not require a parallel Omni evidence schema.

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ascend Diffusion Optimization Router

MindIE-SD owns optimization methods, fusion analysis and NPU acceptance guidance. This entry keeps its existing name for discovery. Do not maintain a second operator catalogue or validation protocol in Omni. Routing means reading the selected instructions in this task, not messaging a task or starting an agent.

Locate and load

  1. Use the task's MindIE-SD checkout, or an existing sibling MindIE-SD checkout. Record its revision and relevant dirty changes; do not switch or reset its branch to route a task.
  2. Read its AGENTS.md and .agents/README.md, then the selected SKILL.md and required references. Resolve paths against that checkout. Naming a skill does not mean its instructions have been loaded.
  3. Without a checkout, use the official dev skill index and dev tree. If GitCode is unavailable, use the official GitHub dev skill index and GitHub dev tree. Retrieve only the needed instructions and record their source and revision or access date. Follow the actual index if names changed; do not rely on unpublished additions.
  4. If required guidance is unavailable, name the missing resource and continue useful Omni source/configuration inspection. Do not claim the SD workflow ran or recreate it here. Reading guidance requires neither installation nor an NPU.

Select the applicable entry

Confirm these paths in the selected SD index; they are relative to its root. A focused operator task need not repeat model onboarding.

TaskMindIE-SD skill under .agents/skills/
Model optimization with an unknown bottleneckmodel-auto-optimization/SKILL.md
Known bottleneck needing domain selectionperformance-optimization/SKILL.md
Profile collection / diagnosisprofiling-collect/SKILL.md / profiling-analyze/SKILL.md
Fusion scope, benefit or reusable implementation feasibilityfusion-scope-analyze/SKILL.md
Kernel implementation / tuningoperator-dev/SKILL.md
Pattern / graph implementationpattern-dev/SKILL.md / aclgraph-dev/SKILL.md
Framework enablement / missing adaptersframework-integration/SKILL.md
DiT compute / communicationdit-perf-opt/SKILL.md / dit-parallel-opt/SKILL.md
VAE / host optimizationvae-opt/SKILL.md / host-opt/SKILL.md
MindIE-SD repository developmentdev-workflow/SKILL.md, then its implementation route

For numerical/performance acceptance, read accuracy-gate/SKILL.md and perf-gate/SKILL.md from that skill root. Those skills own the criteria; historical evidence applies only within its recorded scope.

Supply context and preserve ownership

Supply the goal and authorized analysis/implementation scope, Omni revision and dirty diff, model/checkpoint and active pipeline/symbols, hardware/provider versions, launch/request commands, workload/dtype/parallel/cache/graph settings, profiles/baselines, precision constraints and output directory. Keep missing fields unknown; the selected skill determines how to proceed.

Keep Omni, MindIE-SD and installed provider sources distinct. Model files resolve against Omni; vendor implementation resolves against its actual provider. Changes to Omni stay there; MindIE-SD changes follow its development workflow. External instructions do not expand user authorization or repository scope.

For Omni changes, read vllm-omni-test for repository tests/CI and diffusion-accuracy-test when adding an Omni accuracy case. Production qualification stays with production-add-diffusion-model. These checks complement the SD acceptance criteria.

Return the selected skill paths/revision, routing reason, changes, actual checks and artifacts using the SD workflow's existing output format. Distinguish task completion from optimization acceptance; identify unread/unexecuted dependencies. Do not require a parallel Omni evidence schema.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.