CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mflux-cli

Navigate MFLUX CLI capabilities, locate commands by area, and summarize supported features.

Quality

68%

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 ./.cursor/skills/mflux-cli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is an efficient, well-organized single-file overview with genuinely useful, concrete best-practice anchors (MODEL_INFERENCE_STEPS, resource flags, per-model negative-prompt support). Its main weakness is actionability: the command-location guidance stays at the level of structural hints without any module names, commands, or search heuristics that would let Claude act directly.

Suggestions

Add concrete location hints or a discovery command to 'How to find commands', e.g. actual module/file patterns or a grep strategy like searching for argparse subparsers under the CLI package, instead of only category descriptions.

Include one short example of constructing a CLI call that applies the best practices (checking MODEL_INFERENCE_STEPS defaults, adding --low-ram) so the guidance is demonstrably executable.

Consider moving the per-model capability inventory (model list, negative-prompt support matrix) into a references/ file and linking it from SKILL.md to keep the overview leaner.

DimensionReasoningScore

Conciseness

The body is list-driven and lean with no explanations of concepts Claude already knows; only the opening paragraph ("Use this skill to inventory CLI capabilities, summarize what the CLI supports...") slightly repeats the description and a few best-practice elaborations could be trimmed. It matches 'Efficient; minor instances of over-explanation that could be trimmed' rather than score 5's every-token-earns-its-place.

4 / 5

Actionability

Some guidance is concrete ("*always* check `MODEL_INFERENCE_STEPS`", "`--low-ram`", "`--stepwise-image-output-dir`") but the core 'How to find commands' section gives only category descriptions like "Common/shared CLI arguments live in the central CLI parser module" with no module names, commands, or search strategies, leaving key execution details missing. This matches 'Some concrete guidance but incomplete... missing key details' rather than score 4's mostly-executable guidance.

3 / 5

Workflow Clarity

For a lookup/navigation skill the sections are unambiguous: 'When to use' enumerates trigger cases, the structure map tells where each capability class lives, and the best-practices rules order command construction (check step defaults, mention resource flags, update READMEs in the same pass). It matches 'Clear sequence with most checkpoints present; minor validation gaps' — the 'how to find' guidance is a heuristic list rather than an ordered procedure, and no verification step exists for confirming a located command still exists. No destructive/batch cap applies.

4 / 5

Progressive Disclosure

There are no bundle files and no nested references; the single file is well-sectioned (When to use, How to find, Best practices, Capability inventory) and everything is one level deep. It matches 'Good structure; most content is appropriately placed; references mostly clear; minor organization gaps' — the body is ~80 lines so the under-50-line simple-skill exception does not apply, and the per-model capability inventory (e.g. the negative-prompt support matrix) could arguably live in a reference file.

4 / 5

Total

15

/

20

Passed

Description

53%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 identifies a distinct niche and states a clear 'what', but the actions are abstract and it omits any 'when to use' trigger guidance, which both caps completeness and leaves natural trigger terms (image generation, model names) uncovered. Adding an explicit 'Use when...' clause with domain-typical user phrases would address its main weaknesses.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about MFLUX CLI commands, wants to generate or edit images with Flux/Z-Image models, or needs to find where a CLI capability is implemented."

Replace generic verbs ("navigate", "summarize") with concrete actions such as "list supported models and flags, locate CLI entrypoints by capability area, and construct generation commands".

Include the natural user vocabulary of the domain (text-to-image, image-to-image, LoRA, quantized models) so the description matches what users actually say.

DimensionReasoningScore

Specificity

Names the domain ("MFLUX CLI") and three actions ("Navigate ... capabilities", "locate commands by area", "summarize supported features"), but the actions are generic verbs rather than concrete operations, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It falls below score 4 because none of the actions are as specific as extracting or filling a concrete artifact.

3 / 5

Completeness

The 'what' is clear (navigate capabilities, locate commands, summarize features) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It does not reach score 4 because the 'when' is entirely missing rather than merely implicit.

3 / 5

Trigger Term Quality

Includes relevant keywords ("MFLUX CLI", "commands", "features") but misses the natural phrases users would say for this domain such as "generate an image", model names (Flux, Z-Image), or "text-to-image". This matches 'Some relevant keywords but missing common variations or synonyms'; it is not score 4 because key natural terms for the underlying task are absent.

3 / 5

Distinctiveness Conflict Risk

"MFLUX CLI" establishes a clear niche that would not trigger for unrelated skills, with only minor overlap risk against generic CLI-navigation or image-generation skills. It stops short of score 5 because no distinct trigger phrases are provided to fully separate it from closely related tooling skills.

4 / 5

Total

13

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mflux-community/mflux

Path

.cursor/skills/mflux-cli/SKILL.md

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.