CtrlK
BlogDocsLog inGet started
Tessl Logo

mflux-debugging

Debug MLX ports by comparing against a PyTorch/diffusers reference via exported tensors/images (export-then-compare).

74

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A well-crafted, highly actionable debugging skill: concise and competence-assuming, with concrete code/commands, an explicit validate-and-narrow feedback loop, and clean section organization. The main minor weakness is light repetition of the 'do not commit' hygiene reminder across sections.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence (no explanations of what MLX, PyTorch, or diffusers are); every section earns its place, though the 'do not commit unless asked' reminder repeats a few times.

3 / 3

Actionability

Provides concrete, executable guidance — real commands (uv run python, np.savez, torch.save, /usr/bin/time -p), a complete runnable Python block, and exact tolerance starting points (atol=1e-5/1e-2) — copy-paste ready.

3 / 3

Workflow Clarity

Clear sequenced workflow (steps 1-4) with explicit validation feedback loops ('If a checkpoint fails: add an earlier checkpoint and repeat') and a results-interpretation table, plus a dedicated inject-latents procedure with its own Step 1/Step 2.

3 / 3

Progressive Disclosure

A self-contained single SKILL.md with well-organized sections and named cross-links to sibling skills (mflux-model-porting, mflux-testing); no external bundle files are needed, so the simple-skill note allows a top score for clear organization.

3 / 3

Total

12

/

12

Passed

Description

82%Weight 40%Scale 1-3

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 specific, well-scoped description with strong natural trigger terms and low conflict risk, held back only by the absence of an explicit 'Use when...' clause in the description itself. Third-person voice is correctly used throughout.

Suggestions

Add an explicit 'Use when...' clause to the description, e.g. 'Use when porting a model to MLX and you need to prove numerical parity versus a PyTorch/diffusers reference.'

Keep the concise 'export-then-compare' framing; it is a strong distinctive trigger phrase worth retaining.

DimensionReasoningScore

Specificity

Names a concrete domain ("MLX ports") and multiple specific actions — "comparing against a PyTorch/diffusers reference via exported tensors/images (export-then-compare)" — matching the anchor that lists several concrete actions.

3 / 3

Completeness

It clearly states what (debug MLX ports via export-then-compare) but lacks an explicit 'Use when...' trigger clause; the when-guidance lives in the body, not the description, capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Natural terms a developer would say are present ("MLX ports", "PyTorch/diffusers reference", "tensors/images", "export-then-compare"), giving good coverage rather than jargon-only language.

3 / 3

Distinctiveness Conflict Risk

The narrow niche of MLX-vs-PyTorch/diffusers parity debugging with the distinctive 'export-then-compare' trigger makes it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
filipstrand/mflux
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.