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.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/check-schedulers/SKILL.md

Quality

Content

88%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, highly actionable audit procedure with explicit validation checkpoints and clear sequencing. It is concise and competence-assuming, with only minor redundancy and limited use of separate reference files.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient and assumes competence (no basic-concept padding), but the 'What Loaded And Compiled Means' section and 'Pass Criteria' partially restate earlier procedure and guarantees, so minor trimming is possible.	4 / 5
Actionability	Steps name exact files and symbols and prescribe executable checks (enumerate samplers_data_diffusers, inspect __init__ signatures, run set_timesteps/dummy step), giving fully actionable guidance for this instruction-only audit skill.	5 / 5
Workflow Clarity	A clear six-step sequence with explicit validation gates and feedback loops (mark unverified-at-runtime, do not pass compile on static-only checks, report partial scope with explicit limitations) suits this batch audit operation.	5 / 5
Progressive Disclosure	Content is well-sectioned with clear headers and a single clearly-signaled one-level external reference (.github/instructions/core.instructions.md); however the full procedure is inlined monolithically with no per-step split into separate files.	4 / 5
	Total	18 / 20 Passed

Description

67%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, well-scoped, and distinctive, clearly conveying a four-facet phased scheduler audit. Its main weakness is the absence of explicit 'when to use' trigger guidance, which caps completeness and leaves trigger terms more technical than natural.

Suggestions

Add a 'Use when ...' clause stating natural trigger conditions, e.g. 'Use when auditing scheduler/sampler setup, debugging sampler selection, or verifying scheduler UI options'.

Include a few natural user-facing synonyms alongside technical terms (e.g. 'samplers', 'scheduler UI options', 'scheduler config').

Confirm the description alone communicates the trigger context rather than relying on the separate argument-hint field.

Dimension	Reasoning	Score
Specificity	Names the scheduler-audit domain and lists four concrete, sequenced verification actions (class loadability, config validity, SamplerData correctness, UI option alignment), matching the comprehensive-coverage anchor.	5 / 5
Completeness	It clearly states what the skill does (a phased scheduler audit of four facets) but provides no 'Use when...' trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Domain keywords like 'scheduler audit', 'SamplerData', and 'UI option alignment' are present but lean technical; common natural variations a user would say (e.g. 'check samplers', 'scheduler UI') are missing.	3 / 5
Distinctiveness Conflict Risk	The SD.Next diffusers scheduler-registry and SamplerData-contract niche is highly specific with minimal overlap risk against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: .github/skills/check-schedulers/SKILL.md
Commit: c40fc01

Reviewed: ~18 hours ago

Table of Contents

Discovery Implementation Validation

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.