CtrlK
BlogDocsLog inGet started
Tessl Logo

port-model

Port or add a model to SD.Next using a phased integration flow: select the least-new-code path that follows SD.Next conventions, then implement loader and routing updates, then validate.

63

Quality

75%

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 ./.github/skills/port-model/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 content is a well-sequenced, actionable instruction skill with explicit validation checkpoints and failure-mode guidance. Its main limitations are minor verbosity and a fully-inline structure with no progressive disclosure to separate reference files.

DimensionReasoningScore

Conciseness

The body is dense and largely assumes Claude's competence (no explanations of what SD.Next, a VAE, or a tokenizer is), with concrete file paths and conventions throughout; minor enumerations could be trimmed and there is a typo ("completness"), keeping it just below fully lean.

4 / 5

Actionability

Concrete touchpoints (pipelines/model_<name>.py, modules/sd_models.py, modules/sd_detect.py, modules/modeldata.py) and specific function calls (generic.load_transformer(...), sd_models.path_to_repo(...), model_quant.get_dit_args(...)) give mostly executable guidance, with one copy-paste CHANGELOG example, but the core loader work is instruction-level rather than copy-paste code.

4 / 5

Workflow Clarity

A clear phased sequence (collect inputs → mandatory questions → inspect repo → decision tree → touchpoints → conventions → validation) is paired with an explicit ordered Validation Checklist and a Common Failure Modes section that serves as error-recovery feedback.

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers and one clearly signaled external reference (.github/instructions/core.instructions.md), but all guidance lives inline in a single ~290-line file with no bundle reference files, so it is well-structured rather than progressively split.

4 / 5

Total

17

/

20

Passed

Description

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

The description is specific, third-person, and clearly distinct, but it omits an explicit "Use when..." trigger clause, which caps completeness. Adding concrete trigger phrases would raise it across completeness and trigger-term dimensions.

Suggestions

Append an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when adding a new model family, wiring an upstream Diffusers pipeline, or loading a raw checkpoint/safetensors repo into SD.Next.'

Include natural synonyms and file formats users mention (checkpoint, safetensors, Diffusers pipeline, .ckpt) to broaden trigger-term coverage.

Tighten the action list with one artifact-level concrete term (e.g. 'loader and routing updates in modules/sd_models.py and sd_detect.py') to push specificity toward comprehensive.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Port or add a model", "select the least-new-code path", "implement loader and routing updates", "then validate" — but they stay somewhat abstract without artifact-level specifics, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

The "what" is clearly stated via the phased flow, but there is no explicit "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Natural phrases like "Port or add a model to SD.Next" and "loader and routing updates" map to what users would say, but common synonyms users mention (checkpoint, pipeline, Diffusers, safetensors) are absent.

4 / 5

Distinctiveness Conflict Risk

The SD.Next model-porting niche is specific and unlikely to fire for unrelated skills, giving it a clear distinct trigger surface with minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
vladmandic/sdnext
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.