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 strong, executable operational guidance — exact CLI commands, a well-reasoned preview/deploy decision workflow with real validation checkpoints, and complete C# code examples. Its weaknesses are structural: generic multi-language Windmill content is inlined in a language-specific skill, and the C# section itself misses how resource-typed parameters are declared in C#.
Suggestions
Move the language-agnostic "Windmill Script Writing Guide" (General Principles, Return Values, Preprocessor Scripts) into a shared reference file (e.g. references/windmill-script-guide.md) and keep only the C# section inline.
Add a C# example showing how a resource-typed parameter is declared in a `Main` signature, since only the TypeScript (`RT.C<Name>`) and Python (`c_<name>` TypedDict) forms are shown.
Trim the multi-language argument-shape list (SQL `$1`/`@P1`/`@name`, Bash positional, PowerShell `param(...)`) to a pointer to the shared guide — it is irrelevant to C# scripting.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The CLI-workflow material (preview vs run, generate-metadata, hash syncing) is dense and high-value with no padding about concepts Claude already knows. However, roughly a third of the body is other-language content inlined into a C# skill — TS/Python preprocessor typing, SQL `@P1`/BigQuery placeholder syntax, Bash/PowerShell argument shapes — which is more than a minor trim, keeping it below anchor 4. | 3 / 5 |
Actionability | Exact commands with flags (`wmill script preview <path> -d '<args>'`, `generate-metadata --dry-run`, `rehash`, `resource-type list --schema`) and two complete, copy-paste-ready C# examples cover the common cases. It falls short of anchor 5 because the C# section never shows how resource-typed parameters are declared in C# — only TypeScript `RT.C<Name>` and Python `c_<name>` TypedDict forms appear. | 4 / 5 |
Workflow Clarity | A clear intent-based decision workflow with explicit validation checkpoints: preview validates before any deploy, `--dry-run` lists stale items before narrowing with a path, and the regenerated `.lock` must be diffed with version bumps reported to the user. Deploy is explicitly gated on user request. Not anchor 5: steps are not laid out as an ordered sequence and there is no error-recovery guidance when preview fails. | 4 / 5 |
Progressive Disclosure | Headers are clear and in-file navigation is easy, but no bundle files exist while the language-agnostic "Windmill Script Writing Guide" (General Principles, Return Values, Preprocessor Scripts) is inlined — content that belongs in a shared reference since it is duplicated across the language family. References to `AGENTS.wmill.md` are external to the bundle. This matches anchor 3's 'content that should be separate is inline'. | 3 / 5 |
Total | 14 / 20 Passed |