CtrlK
BlogDocsLog inGet started
Tessl Logo

debug-model

Debug a broken SD.Next or Diffusers model integration. Use when a newly added or ported model fails to load, misdetects, crashes during prompt encoding or sampling, or produces incorrect outputs.

79

Quality

100%

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

100%

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

A well-structured, lean instruction-only debugging skill: concise, highly actionable with specific file paths and functions, a clear outside-in workflow with explicit validation checkpoints, and clean section organization. It avoids the common pitfalls of concept-padding and vague direction.

DimensionReasoningScore

Conciseness

Lean throughout with no explanations of concepts Claude already knows (no diffusion-model primer, no library walkthroughs); every section — Debugging Order, Failure Classification, Common Root Causes — earns its place with terse, direct phrasing.

3 / 3

Actionability

Instruction-only skill with no code, but guidance is concrete and actionable: specific file paths (modules/sd_detect.py, pipelines/<model>/pipeline.py), named functions (sd_models.path_to_repo, generic.load_transformer), and exact fixes ('Add the missing modeldata branch instead of patching downstream task handling').

3 / 3

Workflow Clarity

Clear sequenced workflow (Debugging Order outside-in, Minimal Debug Procedure) with explicit validation checkpoints in 'Validate In Layers' (compileall → ruff → import smoke test → loader smoke test → full run only when lower layers stable) and a closing Validation Checklist serving as a feedback loop.

3 / 3

Progressive Disclosure

No bundle directories exist; the body is well-organized into clearly labeled sections and points one level deep to repo-level reference files (.github/instructions/core.instructions.md) that are real and clearly signaled, satisfying the simple-skills note.

3 / 3

Total

12

/

12

Passed

Description

100%

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, third-person description that states concrete debugging actions, gives an explicit 'Use when' trigger covering several natural failure phrasings, and carves out a distinct niche. It does not pad or over-claim.

DimensionReasoningScore

Specificity

Uses third person voice ('Debug a broken... integration') and lists multiple concrete failure modes — 'fails to load, misdetects, crashes during prompt encoding or sampling, or produces incorrect outputs' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers what ('Debug a broken SD.Next or Diffusers model integration') and when ('Use when a newly added or ported model fails to load, misdetects, crashes... or produces incorrect outputs') with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Includes natural terms a user would actually say ('model fails to load', 'crashes during prompt encoding or sampling', 'incorrect outputs', 'SD.Next', 'Diffusers') with good coverage of variations, not just one keyword.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (SD.Next/Diffusers model port debugging) with distinct triggers unlikely to conflict with other skills.

3 / 3

Total

12

/

12

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.