CtrlK
BlogDocsLog inGet started
Tessl Logo

veomni-new-model

Use this skill when adding support for a new model to VeOmni. Owns the lifecycle around the modeling itself: analyzing the HuggingFace model, choosing the category, the training config, trainer and data-pipeline integration, tests and docs. The modeling patch itself is delegated to /veomni-patchgen-model. Trigger: 'add model', 'support new model', 'integrate a model', 'new model support'.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 orchestration skill with a clear phased workflow, explicit validation checkpoints and feedback loops, and disciplined deferral of modeling detail to a sibling skill. Slightly less copy-paste code and a few trimmable explanations keep it just short of full marks on conciseness and actionability.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence — it deliberately defers pitfalls to /veomni-patchgen-model rather than restating them — with a few explanatory passages (e.g., the parallel_plan FSDP note) that could be trimmed but earn their place as domain-specific clarification.

4 / 5

Actionability

Gives concrete file paths, commands (make patchgen, make quality, pytest tests/models/), and exact landing spots (TEST_CASES, test_model_registry.py); mostly executable guidance with minor gaps since the core codegen is delegated out.

4 / 5

Workflow Clarity

A clearly sequenced five-phase plan with explicit validation checkpoints ("Come back here once the model loads and its registry / patch tests pass", strict loading + checkpoint round-trip tests) and a feedback loop for checkpoint-key conflicts that requires user decision before proceeding.

5 / 5

Progressive Disclosure

Acts as an overview that defers detail to well-signaled one-level-deep references (/veomni-patchgen-model, .agents/knowledge/multimodal_metadata.md, testing.md, architecture.md), keeping the body appropriately split and navigable.

5 / 5

Total

18

/

20

Passed

Description

92%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 clearly answers what and when with concrete trigger phrases and an explicit handoff boundary to a sibling skill. Trigger term coverage is good though not exhaustive.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the lifecycle — "analyzing the HuggingFace model, choosing the category, the training config, trainer and data-pipeline integration, tests and docs" — giving comprehensive coverage of what the skill owns.

5 / 5

Completeness

Explicitly states both what ("adding support for a new model to VeOmni" owning the modeling lifecycle) and when ("Use this skill when adding support..." plus a concrete Trigger clause), matching the top anchor.

5 / 5

Trigger Term Quality

Provides four natural trigger phrases ("add model", "support new model", "integrate a model", "new model support") users would plausibly say, but misses common variations like "register a model"; good but not exhaustive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (new-model lifecycle in VeOmni) and explicitly delineates the boundary by delegating the modeling patch to /veomni-patchgen-model, minimizing wrong-skill triggering.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ByteDance-Seed/VeOmni
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.