migrating-new-op

Name: migrating-new-op
Availability: InStock
Author: tile-ai

Migrate operators into TileOPs with a phased kernel-to-op workflow.

168|55|Updated Jun 3, 2025

Search Tags:#workflow #testing #migration #kernel #tilelang #tileops #op-migration

Ready to run

npx skills add https://github.com/tile-ai/TileOPs --skill migrating-new-op

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrating-new-op
Source: https://github.com/tile-ai/TileOPs/tree/main/.claude/skills/migrating-new-op
Command: npx skills add https://github.com/tile-ai/TileOPs --skill migrating-new-op

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured process for adding or migrating an operator into TileOPs, ensuring a clear kernel-to-op delivery path and a comprehensive validation checklist.

Core Features & Use Cases

Phase-guided migration workflow (A-F) including requirement alignment, strict design-by-layer separation, kernel migration, op wiring, tests, and cleanup.
Enforces Level Confirmation with L1 and L2 paths and deliverables before coding.
Maintains one-way dependency direction: op -> kernel and synchronized exports to prevent stale interfaces.
Reference-aligned development using TileLang kernels and existing TileOPs interfaces.

Quick Start

Confirm the target level (L1 or L2) and follow the required phase sequence (kernel, then op, then tests) to migrate an operator.

Frequently Asked Questions about migrating-new-op

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate an existing CUDA operator into TileOPs?▼

Migrating a CUDA operator into TileOPs requires following a phased workflow: requirement alignment, kernel-first migration using TileLang, op wiring, tests, and cleanup. You must implement the kernel before wiring the op interface.

What is the correct dependency direction when adding a new operator in TileOPs?▼

The correct dependency direction for a new operator in TileOPs is strictly one-way: op depends on kernel. Synchronized exports are enforced to prevent stale interfaces between the op and kernel layers.

How do I validate a migrated operator in TileOPs?▼

To validate a migrated operator in TileOPs, follow the testing phase after completing kernel migration and op wiring. The process enforces Level-based deliverables and a validation checklist to standardize implementation and tests.

Do I need to confirm a target level before migrating a kernel to TileOPs?▼

Yes, you must confirm the target level (L1 or L2) before migrating a kernel to TileOPs. Level Confirmation is an enforced step that defines the required phase sequence and explicit deliverables before coding begins.

What's the best way to structure files when implementing a new TileOPs operator?▼

The best way to structure files for a new TileOPs operator is to follow the design-by-layer separation guidance with explicit file organization and synchronized exports. This maintains the strict one-way op-to-kernel dependency.

Can I migrate a Triton kernel into TileOPs using this workflow?▼

Yes, you can migrate a Triton kernel into TileOPs using the kernel-first migration phase. The workflow standardizes implementation by referencing existing TileLang kernels and TileOPs interfaces for the migration.