CtrlK
BlogDocsLog inGet started
Tessl Logo

check-schedulers

Run a phased scheduler audit from modules/sd_samplers_diffusers.py and scheduler UI definitions: verify class loadability first, then config validity against scheduler capabilities, then SamplerData correctness and UI option alignment.

60

Quality

72%

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

Quality

Content

77%

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

The body is a well-sequenced, actionable audit procedure with strong validation checkpoints and concrete codebase anchors. Its main weaknesses are minor redundancy between the guarantees and procedure sections and the absence of any progressive-disclosure file structure.

Suggestions

Collapse the 'Required Guarantees' list into the Procedure steps (or reference them) to remove the redundancy and tighten conciseness.

Move the detailed per-family config-key checklists (flow-matching, DPM families) into a reference file linked from the body to add progressive-disclosure structure.

DimensionReasoningScore

Conciseness

Mostly efficient and task-specific, but the 'Required Guarantees' list overlaps the subsequent Procedure steps and could be tightened; minor redundancy keeps it just below the lean-and-efficient anchor.

2 / 3

Actionability

Gives highly concrete, codebase-specific guidance — named files, functions (create_sampler_and_steps_selection, create_sampler_options), exact config keys, and specific code patterns to detect (if 'EDM' in name), which is actionable for an instruction-only audit skill.

3 / 3

Workflow Clarity

A clear six-step sequence with explicit validation checkpoints — 'mark those explicitly as unverified-at-runtime', 'Do not mark compile as passed if only static checks were done', and a Pass Criteria gate — providing the feedback loops the rubric rewards.

3 / 3

Progressive Disclosure

Well-organized into clear sections, but the skill is a single ~160-line monolithic SKILL.md with no bundle files or one-level-deep references to split detail into, so it stops short of the 'appropriately split, easy navigation' anchor.

2 / 3

Total

10

/

12

Passed

Description

67%

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 clearly distinct, but leans on internal jargon and omits any explicit 'when to use' trigger guidance. Adding a 'Use when...' clause with more natural user-facing terms would raise completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' trigger clause naming natural user phrases (e.g., 'Use when auditing schedulers, debugging sampler config mismatches, or validating scheduler UI options').

Reduce reliance on internal module names in the description; surface user-facing terms like 'schedulers', 'samplers', and 'sampler config' alongside the technical anchors.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in sequence — 'verify class loadability first, then config validity against scheduler capabilities, then SamplerData correctness and UI option alignment' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers 'what' with a phased audit description, but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Contains some natural terms ('scheduler audit', 'scheduler') but is dominated by codebase-internal jargon ('SamplerData', 'sd_samplers_diffusers.py', 'UI option alignment'), so common user-facing variations are missing.

2 / 3

Distinctiveness Conflict Risk

Scoped to a very specific SD.Next scheduler registry audit, giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

14

/

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.