CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

veomni-new-model

Integrate an existing external model into VeOmni, adapting modeling, data, training, and weight loading as needed. Use for new model support or migration from Transformers, Diffusers, or standalone implementations.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/veomni-new-model/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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.

The body delivers an exceptionally well-sequenced six-phase migration workflow with explicit exit-evidence checkpoints and deeply actionable, repo-specific guidance. Its weaknesses are length and layout: meta-commentary and dense contract/test detail are inlined in a single long file instead of being tightened or split into one-level-deep reference files.

Suggestions

Trim or remove meta-commentary about skill auxiliary files and report templates (e.g., the paragraph 'Add skill auxiliary files only for demonstrated repeated needs...') — a single sentence suffices, saving context tokens.

Move the detailed test-placement and parallel-coverage specifics from Phase 5 (tiny_configs factory registration, eager-ops setup, e2e table policy) into a reference file under references/ and link to it from the phase, keeping SKILL.md as the overview.

Extract the configuration-ownership and ops-binding contract details (ops_implementation precedence, VeomniOp handle lifecycle) into a linked reference document, leaving the phase with the decision-level rules and pointers.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific contracts and avoids explaining concepts Claude already knows, but at ~380 lines it includes unnecessary meta-commentary ("They are not forbidden, but no analyzer, YAML scaffold, or report template is required by this skill") and policy prose that could be tightened or trimmed. It matches the mostly-efficient-but-could-be-tightened anchor rather than the minor-trimming 4 anchor.

3 / 5

Actionability

Guidance is highly concrete: exact paths (veomni/models/registry.py, scripts/model_conversion/<model_name>.py, configs/dit/), a runnable command (make quality), a specific parallel test matrix (dense (SP1, EP1)/(SP2, EP1), MoE (SP1, EP1)/(SP2, EP2)), and a precise N+1-step resume procedure. It stops short of copy-paste-ready commands for the common run cases (e.g., trainer invocation), keeping it at 4 rather than 5.

4 / 5

Workflow Clarity

Six clearly sequenced phases each end with an explicit "**Exit evidence:**" checkpoint, and validation loops are woven throughout: strict loading with rejection of strict=False, fresh-process registry verification, declare-tolerances-before-running parity checks, and blocked-vs-passed check reporting. This matches the anchor for clear sequence with explicit validation steps and error-recovery feedback.

5 / 5

Progressive Disclosure

There are no bundle files (no references/, scripts/, or assets/), so all content lives inline in one ~380-line file. Repo-doc references (docs/design/module_config.md, .agents/knowledge/testing.md) are clearly signaled and one level deep, but detailed contract and test-matrix material that would fit separate reference files is inlined, matching the some-structure-but-could-be-better-organized anchor.

3 / 5

Total

15

/

20

Passed

Description

83%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 description with a clear statement of capability, an explicit "Use for" trigger clause, and concrete framework-level trigger terms. It is specific to the VeOmni integration niche with low conflict risk; only minor refinements — firmer capability wording and a few more trigger synonyms — would raise it further.

DimensionReasoningScore

Specificity

The description lists several concrete action areas — "adapting modeling, data, training, and weight loading" — grounded in a specific task ("Integrate an existing external model into VeOmni"). The hedge "as needed" and the omission of registration/validation work keep it below the comprehensive 5 anchor.

4 / 5

Completeness

It clearly answers "what" (integrate an external model, adapting modeling, data, training, and weight loading) and explicitly answers "when" with a concrete trigger clause: "Use for new model support or migration from Transformers, Diffusers, or standalone implementations."

5 / 5

Trigger Term Quality

"new model support", "migration", "Transformers", "Diffusers", and "standalone implementations" are natural phrases a user would say when needing this skill. Common variations like "port a model" or "add a model" are missing, so it does not reach comprehensive 5-level coverage.

4 / 5

Distinctiveness Conflict Risk

The VeOmni-scoped niche with framework-specific triggers (Transformers/Diffusers migration) is mostly distinct. Minor overlap risk remains with closely related VeOmni model skills (e.g., patchgen-only refresh), which the skill body disambiguates but the description itself does not.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

ByteDance-Seed/VeOmni

Path

.agents/skills/veomni-new-model/SKILL.md

Reviewed

Table of Contents

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.