cli-commands

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

Quality

63%

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/cli-commands/SKILL.md

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.

The body is a comprehensive, executable CLI command catalog with clear per-command structure and a useful object-storage orientation section. Its weaknesses are the large inlined token volume, missing validation guidance for destructive sync/delete/push operations, and total absence of progressive disclosure via separate reference files.

Suggestions

Split the per-command reference (app, flow, sync, instance, etc.) into separate reference files under references/ and keep SKILL.md as a concise overview with one-level-deep links, improving both conciseness and progressive_disclosure.

Add explicit validation/dry-run workflows for destructive and batch operations (e.g. run `--dry-run` then verify the diff before `wmill sync push` / `instance push`) to lift workflow_clarity above the destructive-ops cap of 3.

Include a few worked end-to-end examples with realistic values (e.g. `wmill flow run f/my/flow -d '{"x":1}' -s`) to move actionability from concrete signatures to fully copy-paste-ready examples.

Dimension	Reasoning	Score
Conciseness	Per-line listings are terse with little concept padding, but ~830 lines of every command and option inlined in SKILL.md is a large token footprint that could be tightened or split; it is above 2 (no heavy prose padding) but below 4 (the volume itself is inefficient for the main file).	3 / 5
Actionability	Concrete, copy-paste-ready command signatures with argument types and flags throughout (e.g. `wmill flow run <path>` with documented `-d` data format), plus a 'Choosing a subcommand' guide; it is not a 5 because there are no fully worked end-to-end examples with real values.	4 / 5
Workflow Clarity	This is a reference catalog rather than a sequenced workflow, and destructive/batch operations (`sync push`, `instance push` overwriting remote, `object-storage delete`) lack validation/verification checkpoints, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Section headers organize the commands, but no bundle/reference files exist and the entire CLI reference is inlined in SKILL.md — content that could be split stays inline with no one-level-deep references, so it does not reach a 4.	3 / 5
	Total	13 / 20 Passed

Description

70%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 concise, explicit about when to trigger it, and scoped to a recognizable Windmill CLI niche. Its main weakness is that the 'what' is generic and only the job-related subset of capabilities is enumerated.

Dimension	Reasoning	Score
Specificity	It names the domain ('the CLI') plus two concrete actions ('debugging job failures', 'inspecting run history via `wmill job`'), matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor; it is not a 4 because only the job subset is enumerated rather than several specific actions.	3 / 5
Completeness	Both 'what' (use the CLI for these tasks) and 'when' ('MUST use when using the CLI, including...') are explicit with concrete triggers, but the 'what' is somewhat generic, keeping it below a 5.	4 / 5
Trigger Term Quality	Natural trigger terms like 'CLI', 'debugging job failures', 'run history', and 'wmill job' map well to what a user would say; a few common variations/synonyms (e.g. 'commands', 'scripts', 'sync') are missing, so it sits just below a 5.	4 / 5
Distinctiveness Conflict Risk	The Windmill CLI niche plus the `wmill job` token make it mostly distinct with minor overlap risk against other generic CLI skills, rather than a fully clear niche with minimal conflict (5).	4 / 5
	Total	15 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (834 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
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.