CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-flow

MUST use when creating flows.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./system_prompts/auto-generated/skills/write-flow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

An expert-level, highly actionable guide whose commands, examples, and validation loops are excellent. Its weaknesses are structural: a ~50KB schema blob inlined into the main file with no reference bundle, a dangling OPENFLOW_SCHEMA pointer, and some repeated guidance across sections.

Suggestions

Move the full OpenFlow JSON schema into a references/ file (e.g. references/openflow-schema.md) and keep only a summary of key types inline, replacing the inlined blob and making the OPENFLOW_SCHEMA pointer resolve to a real file.

De-duplicate the visual-preview and generate-metadata guidance — each is stated two to three times (Step 3 vs "Visual preview"; the CLI list, "After writing", and the preview section) — by stating each rule once and cross-referencing it.

Consider splitting the long AI agent / AI decision / chat-mode detail into a reference file so SKILL.md stays a navigable overview with well-signaled one-level-deep references.

DimensionReasoningScore

Conciseness

The prose is dense and Windmill-specific with almost no explanation of concepts Claude already knows, but the entire ~50KB OpenFlow JSON schema is inlined as a single blob at the end, and guidance is repeated across sections (the visual-preview offer appears in Step 3 and again in full under "Visual preview"; the generate-metadata caveats appear in three places). Mostly efficient, but the inlined schema and repetition could be trimmed — anchor 3, not 4, because the schema blob alone is a large token cost.

3 / 5

Actionability

Fully executable throughout: exact commands ("wmill flow new f/folder/my_flow --summary \"Short description\"", "wmill flow preview <flow_path> --step <step_id>", "wmill lint <flow folder>"), copy-paste-ready YAML/JSON module examples, and correct-vs-incorrect shape pairs covering the common cases (preprocessor/failure placement, whileloopflow state carrying, suspend approval, branch scope).

5 / 5

Workflow Clarity

Creation is a clearly numbered sequence (gather path+summary → run wmill flow new → fill flow.yaml), preview/run/deploy are disambiguated by explicit intent rules, and validation is built in: the "Final Structural Self-Check" checklist, `wmill lint` reporting errors before anything runs, `generate-metadata --dry-run` to inspect staleness, and gating `wmill sync push` (the destructive deploy) on explicit user consent. This is a clear sequence with explicit validation, feedback loops, and a checklist.

5 / 5

Progressive Disclosure

Section headers and internal cross-references are good, but there is no bundle at all (no references/, scripts/, or assets/ exist), the entire OpenFlow schema — reference material that clearly belongs in its own file — is inlined in SKILL.md, and the pointer "Refer to OPENFLOW_SCHEMA for the complete type definitions" targets no actual file in the bundle. Between anchor 2 (content that belongs in separate files is inlined) and anchor 3 (good structure, references not clearly signaled); 3 because the document's own organization is strong while the split-out is what fails.

3 / 5

Total

16

/

20

Passed

Description

20%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 a bare trigger clause with no statement of capability and a single generic keyword. It would cause both missed triggers (no 'what' for matching) and false triggers (any 'flow' creation task). Adding what the skill does and Windmill-specific trigger terms would move it up several anchors.

Suggestions

State the capability explicitly, e.g. "Scaffolds, writes, previews, and lints Windmill flows via the wmill CLI (flow.yaml modules, loops, branches, approvals, AI agent steps)."

Include platform-specific trigger terms users would actually say: "windmill", "flow.yaml", "build/edit/deploy a flow", "workflow automation", so it doesn't collide with CI-workflow or generic flow skills.

Keep the 'Use when...' clause but attach it to concrete conditions, e.g. "Use when creating or modifying Windmill flows or when the user mentions wmill or flow.yaml."

DimensionReasoningScore

Specificity

"MUST use when creating flows." states no capability whatsoever — it names no actions, no domain specifics, and no operations; it is a bare trigger clause, matching the 'no concrete actions; pure abstract language' anchor rather than anchor 2, which at least names a domain with minimal actions.

1 / 5

Completeness

Only the 'when' is present ("when creating flows") with no 'what' at all — the description never says what the skill does — which exactly matches anchor 2 ('only when is present without what', e.g. "Use when working with documents"). It is not 3 because there is no clear 'what' to weakly imply.

2 / 5

Trigger Term Quality

The only keyword phrase is "creating flows", one generic term; natural variations users would say — "windmill", "build a flow", "edit a flow", "workflow", "automation" — are all missing, matching 'one or two generic keywords; missing the natural phrases users say'.

2 / 5

Distinctiveness Conflict Risk

"flows" is very broad and unqualified by "windmill" or any platform term, so it would collide with CI/CD pipelines, GitHub Actions workflows, and generic workflow-creation skills — 'very broad; high overlap risk with many similar skills'.

2 / 5

Total

7

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (722 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

windmill-labs/windmill

Path

system_prompts/auto-generated/skills/write-flow/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.