CtrlK
BlogDocsLog inGet started
Tessl Logo

preview

MUST use when opening the Windmill dev page / visual preview of a flow, script, or app. Triggers on words like preview, open, navigate to, visualize, see the flow/app/script, and after writing a flow/script/app for visual verification.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, highly actionable guide with executable commands, a decision table, and an anti-patterns checklist that gates risky paths correctly. Minor room to tighten redundancy between the overview table and the dedicated sections.

Suggestions

Collapse the overlap between the "Two independent decisions" table and the dedicated "Starting the server yourself" / "Letting launch.json start the server" sections so each mode/path is explained once.

Add a short validate→retry note for the launch.json path (e.g., what to do if the chosen port is already in use or the MCP tool fails to launch) to push workflow_clarity from 4 to 5.

Consider splitting the per-target launch.json entry shapes and the stdout line-shape reference into a separate reference file to bring progressive_disclosure to 5.

DimensionReasoningScore

Conciseness

Lean and targeted, assuming Windmill competence; the only slack is light redundancy where the decision table and the dedicated "Starting the server yourself" / "Letting launch.json start" sections restate the same two decisions, keeping it just below the fully lean 5 anchor.

4 / 5

Actionability

Provides copy-paste-ready commands ("wmill dev --path <wmill_path> --no-open", "wmill app dev --no-open --port 4000"), concrete launch.json entries, and MCP invocation guidance covering direct, proxy, app, and launch.json cases — fully executable.

5 / 5

Workflow Clarity

Clear sequencing with explicit gating checkpoints (only take the launch.json path if an mcp__Claude_Preview__* tool exists, bump ports to avoid conflicts) and an anti-patterns checklist, but no explicit validate→fix→retry feedback loop, so it fits the 4 anchor rather than 5.

4 / 5

Progressive Disclosure

Well-organized into clear sections with no nested references and no bundle files to navigate, but at ~127 lines it exceeds the under-50-line simple-skill exemption that would let well-organized structure alone reach 5.

4 / 5

Total

17

/

20

Passed

Description

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

A strong, trigger-rich description that clearly answers both what it does and when to use it, with natural synonyms users would actually say. The only minor gap is breadth of distinct concrete actions, which keeps specificity at 4 rather than 5.

DimensionReasoningScore

Specificity

Names the concrete domain and actions — "opening the Windmill dev page / visual preview of a flow, script, or app" — but the action set is narrow (open/preview) rather than a comprehensive list of distinct capabilities, so it sits at 4 rather than 5.

4 / 5

Completeness

Explicitly states what (open/visualize the Windmill dev preview) and when ("MUST use when…" plus concrete trigger phrases and an after-writing case), satisfying the 5 anchor for both what and when.

5 / 5

Trigger Term Quality

"Triggers on words like preview, open, navigate to, visualize, see the flow/app/script" gives comprehensive coverage of natural synonyms a user would actually say, matching the 5 anchor.

5 / 5

Distinctiveness Conflict Risk

Scoped to the Windmill dev-page preview with distinct triggers, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
windmill-labs/windmill
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.