port-pipeline

Port custom model pipeline implementations to Diffusers using phased priorities: preserve behavior first, avoid new dependencies second, and keep device/attention handling configurable throughout. Use when migrating custom or non-Diffusers pipeline code into SD.Next repo-local pipeline files such as pipelines/model_<name>.py or pipelines/<model>/pipeline.py.

Quality

81%

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

Quality

Content

62%

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

A well-structured, clearly sequenced porting workflow with strong validation checkpoints, but it is weakened by redundancy across sections, directional rather than executable porting guidance, and a monolithic structure with no progressive disclosure into reference files.

Suggestions

Consolidate the redundant input-collection guidance: the "Mandatory Clarification Gate" duplicates Workflow Step 1, and "Constraints" restates the description's phased priorities — fold these into a single location to tighten the document.

Add a concrete code skeleton (e.g., a minimal `from_pretrained`/`__call__` signature or pipeline class stub) so the core porting guidance is copy-paste ready rather than directional.

Split detailed reference material (the full Review Checklist and per-step porting details) into a file under `references/` with one-level-deep links from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	It avoids explaining concepts Claude already knows, but the "Mandatory Clarification Gate" restates Workflow Step 1's input collection and "Constraints" repeats the phased priorities already in the description. Not a 3 due to this redundancy; not a 1 because there is no basic-concept padding.	2 / 3
Actionability	Provides executable linter commands (`pnpm ruff`, `pnpm pylint`, `source venv/bin/activate`) and concrete path patterns, but core porting guidance like "Choose the most appropriate Diffusers base class" is directional with no executable code skeleton. Not a 3 because nothing is copy-paste ready for the actual port; not a 1 because lint commands and paths are concrete.	2 / 3
Workflow Clarity	An 8-step sequence with an explicit validation feedback loop ("Re-run both linters after fixes to confirm a clean result before proceeding"), a behavior-parity validation step, and a final Review Checklist. Not a 2 because validation checkpoints and feedback loops are explicit, not implicit.	3 / 3
Progressive Disclosure	Sections are well-organized, but it is a single ~116-line monolithic file and the only reference (`.github/instructions/core.instructions.md`) is an external repo file, not a skill bundle. Not a 3 because no one-level-deep reference files are split out; not a 1 because the section organization is clear rather than a wall of text.	2 / 3
	Total	9 / 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 actions, gives an explicit 'Use when' trigger with natural domain terms, and is tightly scoped to a distinctive niche. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions: "Port custom model pipeline implementations to Diffusers", "preserve behavior first", "avoid new dependencies second", and "keep device/attention handling configurable throughout".	3 / 3
Completeness	Explicitly answers both what ("Port custom model pipeline implementations to Diffusers...") and when ("Use when migrating custom or non-Diffusers pipeline code..."). Not a 2 because the 'when' is explicit, not merely implied.	3 / 3
Trigger Term Quality	The "Use when migrating custom or non-Diffusers pipeline code into SD.Next repo-local pipeline files" clause covers natural terms (migrate, pipeline, Diffusers, SD.Next) with concrete path patterns a developer would say. Not a 2 because keyword coverage is strong rather than just a couple of relevant terms.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (SD.Next repo-local Diffusers pipeline ports) with concrete path-based triggers, making it unlikely to fire for the wrong skill. Not a 2 because the triggers are highly specific rather than broadly overlapping.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: vladmandic/sdnext
Path: .github/skills/port-pipeline/SKILL.md
Commit: 058a7f0

Reviewed: about 23 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.