veomni-new-op

Use this skill when adding a new optimized kernel or operator to veomni/ops/. Covers the full lifecycle: understanding VeOmni's ops architecture (KERNEL_REGISTRY + OpSlot dispatch, with a thin function-pointer shim for a few legacy global ops), implementing the kernel, registering it, adding tests, and documenting it. Trigger: 'add op', 'new kernel', 'add attention variant', 'new fused op', 'add triton kernel', 'optimize operator'.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body that phases a complex op-addition workflow with concrete code and validation checkpoints, while deferring deep detail to one-level-deep referenced docs. It is lean for its complexity, with only minor room to tighten inline architecture exposition and to surface validation-failure recovery inline.

Suggestions

Add an inline feedback loop in Phase 5 (e.g., 'If the variant is missing from KERNEL_REGISTRY.dump(), re-check the register() call and import path') so error recovery sits next to the validation step rather than only in Common Pitfalls.

Consider moving the full veomni/ops ASCII directory tree into a referenced doc (e.g. architecture.md) and keeping only the dispatch-relevant subset inline to reduce token cost.

Tighten the three-mechanism coexistence section into a compact decision table (mechanism → when to use → key entry point) to improve scannability.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence — it explains repo-specific concepts (KERNEL_REGISTRY, OpSlot, patchgen) rather than basics Claude already knows. Minor trimming possible in the ASCII directory tree and the three-mechanism coexistence breakdown, but every section earns its place.	4 / 5
Actionability	Provides concrete, executable guidance: copy-paste KernelSpec registration and OpSlot declaration code, specific file paths, and real commands (pytest tests/ops/ -v, make quality, KERNEL_REGISTRY.dump()). Template placeholders (my_op) are appropriate for a skill, with only minor gaps in fully worked examples.	4 / 5
Workflow Clarity	Clearly sequenced into Before-You-Start + Phases 1–5 with explicit validation in Phase 5 (verify dump shows variant, OpSlot rebound, run /veomni-review) plus a Common Pitfalls checklist. The error-recovery feedback on failed validation lives in the separate Pitfalls section rather than inline, keeping it just below a 5.	4 / 5
Progressive Disclosure	Clear overview structure that points to one-level-deep external docs (kernel_selection.md, unified_kernel_registry.md, README.md, testing.md, architecture.md) for detail; no bundle files exist. The inline architecture tree and mechanism explanation are somewhat heavy but justified for a complex multi-mechanism codebase.	4 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that explicitly covers what the skill does across the full op lifecycle and when to invoke it via natural trigger phrases. It uses the canonical 'Use this skill when' opener (consistent with the rubric's good examples) rather than penalizable first/second-person voice.

Dimension	Reasoning	Score
Specificity	Names the domain ('adding a new optimized kernel or operator to veomni/ops/') and lists multiple concrete lifecycle actions — understanding the architecture, implementing, registering, testing, and documenting — for comprehensive coverage.	5 / 5
Completeness	Clearly answers both 'what' (full lifecycle of adding an op) and 'when' (concrete trigger phrases), matching the anchor that requires explicit what-and-when with triggers.	5 / 5
Trigger Term Quality	Explicit 'Trigger:' clause lists natural phrases users would say ('add op', 'new kernel', 'add attention variant', 'new fused op', 'add triton kernel', 'optimize operator') with good synonym coverage.	5 / 5
Distinctiveness Conflict Risk	Highly specific niche tied to veomni/ops and its KERNEL_REGISTRY/OpSlot architecture, with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ByteDance-Seed/VeOmni
Path: .agents/skills/veomni-new-op/SKILL.md
Commit: b8a3edc

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.