write-flow

MUST use when creating flows.

Quality

56%

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

Fix and improve this skill with Tessl

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

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.

The content is highly actionable with concrete commands, YAML shapes, and a clear creation workflow backed by validation checklists. Its main weakness is token efficiency and structure: a large raw schema dump and some duplicated sections are inlined rather than externalized into reference files.

Suggestions

Move the inline OpenFlow JSON schema into a separate reference file (e.g. references/openflow-schema.json) and link to it, removing the duplication with the earlier 'OpenFlow Schema' section.

Deduplicate the resource-reference material currently split across 'Resource References', 'S3 Object Operations', and 'Using Resources in Flows'.

Make external references clickable/signal-clear (e.g. 'See [OPENFLOW_SCHEMA.md](references/openflow-schema.md)' with a real path) so navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	The prose is mostly lean, high-signal Windmill-specific guidance Claude would not already know, but the file inlines a massive raw OpenFlow JSON schema dump (and repeats the 'OpenFlow Schema' / resource-reference sections), which is bulk reference material that could be trimmed or externalized — 'mostly efficient but includes some unnecessary content that could be tightened'.	3 / 5
Actionability	The body is packed with copy-paste-ready commands (wmill flow new, flow preview, generate-metadata --dry-run) and concrete correct/incorrect YAML shapes for modules, loops, approvals, and branches, covering the common cases comprehensively.	5 / 5
Workflow Clarity	The 'Creating a Flow' section gives an explicit Step 1→2→3 sequence, and the 'Final Structural Self-Check' checklist plus preview/dry-run validation with feedback loops provide the explicit validation checkpoints the rubric's anchor 5 calls for.	5 / 5
Progressive Disclosure	There are many well-organized section headers, but the full OpenFlow schema is inlined directly in the body (content that clearly belongs in a separate reference file) and references like 'Refer to OPENFLOW_SCHEMA' are not clearly signaled with a path or link, matching 'some structure but content that should be separate is inline'.	3 / 5
	Total	16 / 20 Passed

Description

36%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 essentially a bare trigger clause — it tells Claude when to fire but not what the skill does or how. It names the right domain but lacks any concrete capability statement, leaving completeness and specificity weak.

Suggestions

Add a 'what' clause stating concrete actions, e.g. 'Scaffolds Windmill flows by running wmill flow new, fills in flow.yaml, and guides preview/deploy. MUST use when creating flows.'

Include richer natural trigger terms and synonyms such as 'windmill flow', 'new flow', 'scaffold a flow', and 'flow.yaml'.

Tie the trigger to Windmill explicitly to reduce overlap with generic flow-related skills.

Dimension	Reasoning	Score
Specificity	The phrase "MUST use when creating flows" names the domain (flows) but states no concrete actions the skill performs — it never mentions scaffolding, the wmill CLI, or flow.yaml generation, so it sits at 'names the domain but actions are minimal or generic' rather than the entirely-vague anchor 1.	2 / 5
Completeness	It supplies an explicit 'when' ("MUST use when creating flows") but entirely omits any 'what' — there is no statement of what the skill does, which is the anchor-2 case of 'only when is present without what'.	2 / 5
Trigger Term Quality	"creating flows" is a natural phrase a user would say, but it is the only trigger term and lacks common variations/synonyms (e.g. 'windmill flow', 'new flow', 'scaffold flow'), matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	"creating flows" is somewhat specific to a flow-building niche but is generic enough to overlap with related flow skills (e.g. preview, resources) referenced in the body, fitting 'somewhat specific but could still overlap with similar skills'.	3 / 5
	Total	10 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: windmill-labs/windmill
Path: system_prompts/auto-generated/skills/write-flow/SKILL.md
Commit: 7915540

Reviewed: 3 days 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.