CtrlK
BlogDocsLog inGet started
Tessl Logo

check-models

Audit SD.Next model integrations end-to-end: loaders, detect/routing, reference catalogs, and pipeline API contracts.

60

Quality

70%

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/check-models/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The content is a well-structured, actionable audit skill with clear sequencing, validation checkpoints, and a defined reporting format. Its main gaps are the lack of an explicit fix-retry feedback loop and the absence of any executable command examples.

Suggestions

Add an explicit validate-fix-retry loop for batch audit findings (e.g., 'after fixing a flagged loader, re-run Audit A on that family before proceeding').

Include a few concrete executable commands (e.g., grep/ast-grep patterns or a one-line JSON validation command) to make the checks copy-paste ready rather than descriptive.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, referencing specific functions (sd_models.path_to_repo, model_quant.get_dit_args) without explaining them; a few bullet lists could be marginally tightened.

4 / 5

Actionability

Provides concrete, actionable guidance via specific file paths, function names, and per-audit check lists; as an instruction-only skill it lacks copy-paste commands but the checks are executable in direction with minor gaps.

4 / 5

Workflow Clarity

Audits A-D are explicitly ordered, with Runtime Validation and Pass Criteria providing checkpoints and per-audit checklists; however there is no explicit validate-fix-retry feedback loop for this batch operation.

4 / 5

Progressive Disclosure

Well-organized into clear sections with a single clearly-signaled one-level reference to .github/instructions/core.instructions.md and no nested references; minor organization gaps since all four audits are inlined rather than split into reference files.

4 / 5

Total

16

/

20

Passed

Description

66%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 and well-targeted to an SD.Next contributor audience, clearly conveying what the skill audits. Its main weakness is the missing 'Use when...' trigger clause, which caps completeness.

Suggestions

Append a 'Use when...' clause with concrete triggers (e.g., 'Use when auditing a new model family, before a model-related PR, or when loader/detect/reference/pipeline behavior looks inconsistent').

Use multiple distinct action verbs (audit, verify, validate, flag) instead of a single 'Audit' verb governing four objects to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('SD.Next model integrations') and enumerates four concrete audit surfaces (loaders, detect/routing, reference catalogs, pipeline API contracts), but uses a single verb 'Audit' across four objects rather than multiple distinct action verbs, leaving it just shy of comprehensive.

4 / 5

Completeness

Clearly states what the skill does, but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes relevant natural terms for the target audience ('model integrations', 'loaders', 'detect/routing', 'reference catalogs', 'pipeline API contracts') with good coverage, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The SD.Next-specific audit niche is clearly distinct, but the description combines four surfaces that overlap with sibling skills (check-loaders, check-detect-routing, etc.), creating minor overlap risk.

4 / 5

Total

15

/

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.