CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-commands

MUST use when using the CLI, including debugging job failures and inspecting run history via `wmill job`.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./system_prompts/auto-generated/skills/cli-commands/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 dense, accurate, and highly actionable CLI reference that assumes Claude's competence and documents product-specific flags Claude cannot know. Its weaknesses are structural: a monolithic ~900-line single file with no reference files, duplicated option blocks, and no explicit validation guidance for the many destructive push/merge/delete operations it documents.

Suggestions

Split the per-command reference into per-domain reference files (e.g. references/jobs.md, references/sync.md, references/apps.md) and keep SKILL.md as a concise overview with one-level-deep pointers, per the progressive-disclosure model.

Deduplicate the `sync pull`/`sync push` and `instance pull`/`instance push` option blocks by stating shared options once, and factor the ~40 repeated "--json - Output as JSON (for piping to jq)" lines into a single global note.

Add validation guidance for destructive/batch operations — e.g. "run `wmill sync push --dry-run` (or `--lint`) and review the changes before pushing without `--yes`" — so workflow clarity isn't capped by missing checkpoints.

DimensionReasoningScore

Conciseness

Entries are terse one-line flag descriptions with no conceptual padding (e.g. "--show-diffs - Show diff informations when syncing"), and the "Key concepts (not obvious from per-command --help)" section adds genuinely non-obvious guidance. However, `sync pull`/`sync push` repeat ~28 identical options, `instance pull`/`instance push` repeat ~10, and "--json - Output as JSON (for piping to jq)" is repeated ~40 times — more than minor over-explanation, matching anchor 3 ("could be tightened") rather than 4.

3 / 5

Actionability

Exact command signatures with argument types, flags, and defaults throughout (e.g. "object-storage upload <local_path:string> <file_key:string>", "-d --data <data:string>" with explicit $res/$var semantics) let Claude construct commands directly. It falls short of anchor 5 only because there are few complete worked examples with real values or sample outputs.

4 / 5

Workflow Clarity

This is a lookup reference rather than a sequenced workflow; implicit sequencing exists (the object-storage "Choosing a subcommand" decision guide, digest's "Run from the root of a sync checkout" timing note). But destructive/batch operations — "sync push" ("This overrides any remote versions"), "workspace merge", "object-storage delete", "datatable migrate down" — lack explicit validation checkpoints even though the tools exist (--dry-run, --lint, --locks-required), so the rubric cap of 3 applies.

3 / 5

Progressive Disclosure

No bundle files exist; the entire ~840-line command-by-command API reference is inlined in SKILL.md. Internal structure is good (## Global Options, ### per command group, a separate # Object Storage CLI section), making it navigable — matching anchor 3 ("some structure... content that should be separate is inline") rather than 2, which requires minimal structure or no headers.

3 / 5

Total

13

/

20

Passed

Description

41%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 has an explicit, strong trigger clause with a couple of concrete job-related use cases, but it never states what the skill contains and frames its trigger around the generic "the CLI" rather than naming wmill. It reads as a routing instruction rather than a capability description, leaving both completeness and distinctiveness weak.

Suggestions

Add a 'what' clause stating the skill's content, e.g. "Reference for the `wmill` CLI: commands for managing scripts, flows, apps, datatables, jobs, sync, and workspaces."

Name the tool in the trigger clause — "MUST use when running `wmill` / Windmill CLI commands" — instead of the generic "the CLI", to reduce overlap with other CLI-related skills.

Broaden trigger terms beyond job debugging to match the command families the reference actually covers (e.g. "syncing, pushing, or previewing scripts and flows; managing workspaces and datatables").

DimensionReasoningScore

Specificity

It names two concrete actions — "debugging job failures and inspecting run history via `wmill job`" — anchored to the CLI domain, matching anchor 3 ("names domain and 1-2 concrete actions, but not comprehensive"). It is not a 4 because the body covers ~30 command groups (sync, script, flow, app, datatable, workspace, ...) of which none are named.

3 / 5

Completeness

The description is a pure trigger statement — "MUST use when using the CLI, including..." — with no clause stating what the skill is or does (a full wmill CLI command reference). This matches anchor 2 ("only 'when' is present without 'what'", example "Use when working with documents"); it cannot be a 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

Natural terms are present ("the CLI", "job failures", "run history", "wmill job") but common variations are missing — the tool name "wmill"/"Windmill" never appears in the trigger clause, and there are no terms for the other command families the reference covers, matching anchor 3 rather than anchor 4's "good keyword coverage".

3 / 5

Distinctiveness Conflict Risk

The "via `wmill job`" mention anchors it to the Windmill CLI, but the operative trigger phrase "when using the CLI" never names the tool and would equally match any other CLI-oriented skill, matching anchor 3 ("somewhat specific but could still overlap with similar skills") rather than 4's "mostly distinct".

3 / 5

Total

11

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing, 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

windmill-labs/windmill

Path

system_prompts/auto-generated/skills/cli-commands/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.