Content
63%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body delivers concrete, executable Windmill-specific guidance with a well-gated run/preview/deploy workflow and meaningful validation checkpoints. Its weaknesses are redundancy (repeated deploy-gating and shebang rules) and a monolithic structure that mixes language-agnostic Windmill content into a Bash-specific skill.
Suggestions
State the deploy-only-when-explicitly-asked rule once and cross-reference it, instead of repeating it across the CLI commands, preview-vs-run, sync-push, and after-writing sections.
Move the cross-language general Windmill guidance (preprocessors, resource types, return values) into a shared reference file (e.g. references/windmill-general.md) and keep SKILL.md focused on Bash specifics plus a pointer.
Remove the duplicate shebang prohibition — it is stated in prose ("Do not include #!/bin/bash") and again in the Important list.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Most content is genuinely non-obvious platform detail (lock hash invalidation, `generate-metadata rehash`, hub resource types), but the deploy-only-when-asked rule is restated four times, the shebang prohibition appears twice (line 82 and the "Important" list), and long parenthetical run-ons could be tightened. Matches anchor 3 ('Mostly efficient but includes some unnecessary explanation or could be tightened'); not 4 because the redundancy exceeds minor instances. | 3 / 5 |
Actionability | Concrete commands with exact flags (`wmill script preview <script_path>`, `generate-metadata --dry-run`, `rehash`, `--strict-folder-boundaries`, `resource-type list --schema`) plus executable bash snippets with correct positional-arg and heredoc-JSON syntax. Matches anchor 4 ('Mostly executable guidance; concrete code or commands with minor gaps') — the gap being "Place scripts in a folder" naming no folder; not 5 because a few specifics like that are missing. | 4 / 5 |
Workflow Clarity | A clear decision tree for preview vs run vs sync push with real checkpoints: dry-run before regenerating metadata, diffing regenerated locks to report version bumps, and "the preview has already validated the change" as a deploy precondition. Matches anchor 4 ('Clear sequence with most checkpoints present; minor validation gaps'); not 5 because there is no explicit error-recovery loop when a preview or validation fails. | 4 / 5 |
Progressive Disclosure | No bundle files exist, so everything is one inline file; headers are present, but general cross-language Windmill material (preprocessor scripts, resource types, return values, TypeScript/Python typing) sits inline in a Bash-named skill where a shared reference belongs. Matches anchor 3 ('Some structure but could be better organized; content that should be separate is inline'); not 4 because the language-general and Bash-specific material are not split, and pointers like AGENTS.wmill.md and the preview skill resolve outside the skill. | 3 / 5 |
Total | 14 / 20 Passed |