Content
71%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 is highly actionable with exact commands, copy-paste-ready GraphQL examples, and a well-gated deploy/test/metadata workflow with real validation checkpoints. Its weaknesses are redundancy (the deploy-gating rule restated several times) and a monolithic single-file structure that inlines a general Windmill script-writing guide not specific to GraphQL. Trimming the repetition and splitting the general guide into a shared reference would lift both.
Suggestions
State the deploy-only-on-explicit-request rule once (in the CLI commands list) and reference it from other sections instead of restating it four times; likewise collapse the three "this is not a deploy" clarifications into one.
Move the general Windmill script-writing guide (resource-typed parameters, return values, preprocessor scripts — none of it GraphQL-specific) into a shared reference file, leaving SKILL.md focused on the GraphQL script workflow.
Reorder so the GraphQL-writing guidance and the post-writing workflow (preview → metadata → deploy) read as one continuous sequence instead of interleaving the CLI section, general principles, and GraphQL guide.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is Windmill-specific with no generic padding, but has real redundancy: the deploy-only-on-explicit-request rule is stated four times (CLI list, "Preview vs run", "Only use sync push when", and the preview section), "not a deploy" is repeated three times, and the AGENTS.wmill.md "Deploying" pointer appears twice. Mostly efficient but could be tightened by consolidating these — matching "includes some unnecessary explanation or could be tightened". | 3 / 5 |
Actionability | Fully executable throughout: exact CLI commands (`wmill script preview <script_path>`, `wmill generate-metadata --dry-run`, `wmill generate-metadata rehash`, `wmill resource-type list --schema`), copy-paste-ready GraphQL examples covering queries, variable binding, and mutations, and concrete per-language placeholder syntax. Specific examples cover the common cases, matching the top anchor. | 5 / 5 |
Workflow Clarity | A clear script lifecycle is sequenced (write → choose preview vs run by intent → generate-metadata → deploy only on explicit request) with explicit validation checkpoints: preview validates before any deploy, regenerated `.lock`/`.script.lock` diffs are surfaced to catch version bumps, and `--dry-run` lists stale items before narrowing. The destructive operation (deploy) does have validation, so no cap applies; it is 4 rather than 5 because the end-to-end workflow is interleaved across separated sections and must be assembled by the reader. | 4 / 5 |
Progressive Disclosure | The single 123-line file has well-organized headers and no nested references (the AGENTS.wmill.md pointer is one level and clearly signaled), but roughly half the content — the general Windmill script-writing guide on resource types, return values, and preprocessor scripts — is not GraphQL-specific and would naturally live in a separate shared reference file. This matches "Some structure but could be better organized; content that should be separate is inline"; the under-50-line simple-skill exception does not apply at this length. | 3 / 5 |
Total | 15 / 20 Passed |