CtrlK
BlogDocsLog inGet started
Tessl Logo

diffusers-code

Create or edit code that is compliant with Hugging Face diffusers conventions, including models, pipelines, schedulers, tests, docs, and PR preparation targeting diffusers.

61

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/diffusers-code/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 concise, well-structured, and offers a clearly sequenced workflow with validation, but it is short on executable code examples and points to an external instructions file that is not present in the bundle.

Suggestions

Add at least one complete, executable code snippet (e.g., a minimal ModelMixin/register_to_config skeleton or a from_pretrained round-trip) to lift actionability.

Resolve or remove the broken reference to '.github/instructions/core.instructions.md' — either include the file in the bundle or drop the pointer so progressive disclosure is clean and one-level-deep.

DimensionReasoningScore

Conciseness

Lean, rule-oriented body that assumes Claude knows diffusers internals; no padding or explanation of concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

Gives concrete directives and commands ('make style', 'make fix-copies', 'register_to_config', '@torch.no_grad()') but is mostly rules/checklists with little copy-paste-ready executable code, fitting the 'some concrete guidance but incomplete' anchor.

2 / 3

Workflow Clarity

The Change Workflow is clearly sequenced (Gather, Plan, Implement, Validate, Polish) with an explicit validation step and a PR Quality Checklist with feedback loops, matching the top anchor.

3 / 3

Progressive Disclosure

Sections are well-organized, but the sole external reference '.github/instructions/core.instructions.md' does not exist in the bundle, leaving a dangling pointer rather than a clean one-level-deep reference.

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 niched to diffusers, but it omits an explicit 'Use when' trigger clause, which limits trigger-term quality and completeness. Adding a natural-language trigger sentence would lift the two lowest dimensions.

Suggestions

Add an explicit 'Use when...' trigger clause naming natural user phrases (e.g., 'Use when implementing or PR-ing code to the diffusers library — models, pipelines, schedulers, tests, or docs').

Surface common natural trigger terms a user would actually say ('diffusers pipeline', 'add a scheduler to diffusers', 'diffusers PR') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Create or edit code', 'models, pipelines, schedulers, tests, docs, and PR preparation' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly states what the skill does but provides no explicit 'Use when...' trigger clause, so the 'when' is only implied — capping completeness at 2 per the guideline.

2 / 3

Trigger Term Quality

Contains relevant domain terms ('Hugging Face diffusers', 'models, pipelines, schedulers', 'PR') a contributor would say, but lacks common natural variations and a 'Use when' phrasing to reach full coverage.

2 / 3

Distinctiveness Conflict Risk

Narrowly scoped to the diffusers library with distinct triggers ('targeting diffusers', 'diffusers conventions'), making conflict with other skills unlikely.

3 / 3

Total

10

/

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.