write-flow

MUST use when creating flows.

Quality

48%

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 body is highly actionable with a clear, validated workflow for scaffolding, editing, previewing, and deploying Windmill flows. Its main weakness is the inlined full OpenFlow schema JSON, which inflates token cost and should live in a separate reference file.

Suggestions

Move the embedded OpenFlow schema JSON into a separate reference file (e.g. references/openflow_schema.json) and keep only a one-line pointer plus the few field examples actually needed inline.

Replace the inlined schema with the specific subset the workflow relies on (modules, preprocessor/failure modules, suspend, transforms) so the overview stays lean.

Verify the referenced paths (OPENFLOW_SCHEMA, AGENTS.wmill.md) resolve to real bundle files so the one-level-deep references are navigable.

Dimension	Reasoning	Score
Conciseness	The instructional prose is lean and assumes Claude's competence (e.g. tight Step 1-3 scaffolding, anti-patterns), but the body embeds the entire OpenFlow schema as a giant inline JSON blob (~hundreds of lines of type definitions) that is reference material Claude does not need inline, matching the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor; it cannot reach 4 because of that bulk.	3 / 5
Actionability	It gives fully executable, copy-paste-ready commands ("wmill flow new f/folder/my_flow --summary \"Short description\"") plus concrete YAML/JSON examples and exact rules covering the common cases (scaffold, fill flow.yaml, preview, deploy), matching the top anchor.	5 / 5
Workflow Clarity	The creation flow is sequenced as Step 1-3 with an explicit anti-patterns list and a 'Final Structural Self-Check', and the preview/deploy section has clear validation checkpoints (preview before deploy, 'Only when valid', dry-run to inspect stale deps), matching the anchor for clear sequence with explicit validation and feedback loops.	5 / 5
Progressive Disclosure	Sections are reasonably organized and a few references are signaled (OPENFLOW_SCHEMA, AGENTS.wmill.md, the preview skill), but the full OpenFlow schema is inlined as a monolithic JSON blob that clearly belongs in a separate reference file, matching the 'some structure but content that should be separate is inline' anchor; it is not a 4 because the schema dump is a major piece of misplaced inline content rather than a minor gap.	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 essentially a bare trigger clause with no statement of what the skill does or that it targets Windmill flows. It is too generic to distinguish the skill or convey its capabilities. Add concrete actions and the Windmill domain to make it complete and distinctive.

Suggestions

State what the skill does, e.g. 'Scaffolds, edits, previews, and deploys Windmill flows via the wmill CLI', so the 'what' is explicit.

Add Windmill-specific trigger terms and synonyms (e.g. 'Use when creating or editing Windmill flows, flow.yaml, wmill flow new, or when the user mentions Windmill flows').

Keep third-person voice and combine what + when in one sentence, e.g. 'Scaffolds and deploys Windmill flows with the wmill CLI. Use when creating or editing Windmill flows (flow.yaml, wmill flow new).'

Dimension	Reasoning	Score
Specificity	The description is "MUST use when creating flows" — it names no concrete actions or capabilities whatsoever, only a trigger condition, matching the 'entirely vague; no concrete actions' anchor.	1 / 5
Completeness	It states only a 'when' ("MUST use when creating flows") with no 'what' describing what the skill does, matching the anchor for 'only when is present without what'; it cannot reach 3 because the 'what' is entirely absent.	2 / 5
Trigger Term Quality	"creating flows" is a generic phrase users might say, but it omits the domain keyword 'Windmill' and any synonyms or file extensions, falling between the one-or-two-generic-keywords anchor (2) and the some-relevant-keywords anchor (3); it sits noticeably below the midpoint because it lacks the natural term 'windmill'.	2 / 5
Distinctiveness Conflict Risk	"creating flows" is very broad and does not mention Windmill, so it would overlap with virtually any flow-creation skill, matching the 'very broad; high overlap risk' anchor; it is not a 1 only because it does narrow to 'flows' rather than 'documents and code'.	2 / 5
	Total	7 / 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: 74af4ed

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