write-script-rust

MUST use when writing Rust scripts.

Quality

61%

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/write-script-rust/SKILL.md

Quality

Content

63%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 highly actionable with executable Rust examples and a well-sequenced wmill workflow including real validation checkpoints. Its weaknesses are redundancy (repeated deploy/not-a-deploy caveats) and inlined generic multi-language Windmill material that belongs in a shared reference, which hurt conciseness and progressive disclosure.

Suggestions

State the 'generate-metadata is not a deploy' and 'deploy only when explicitly asked' caveats once each instead of repeating them four times across the CLI commands, metadata, and after-writing sections.

Move the general Windmill guide (general principles, return values, preprocessor scripts, per-language placeholder syntax) into a shared reference file, keeping only Rust-relevant guidance inline.

Add a Rust example showing a resource-typed parameter (credentials as parameters) and a sample `wmill script preview` invocation with concrete -d args for a Rust script.

Dimension	Reasoning	Score
Conciseness	The Rust-specific sections are lean and example-driven, but the 'not a deploy' caveat is repeated roughly four times (lines 14, 31, 33, 45), the deploy-only-when-asked rule is stated four times (15, 19, 26, 45), and a general Windmill guide covering 10+ languages (SQL/Bash/PowerShell placeholder syntax, preprocessors) is inlined in a Rust-specific skill. Mostly efficient but could be tightened — anchor 3, not anchor 2 since there is no basic-concept padding and the bulk is operational guidance.	3 / 5
Actionability	Fully executable Rust examples (serializable struct return, cargo block in doc comments, tokio runtime pattern) plus concrete commands (wmill script preview, generate-metadata --dry-run, generate-metadata rehash) with specific decision rules. Anchor 4 rather than 5 because of minor gaps: no Rust example of a resource-typed parameter despite the principle being stated, and wmill resource-type list --schema is mentioned without a usage example.	4 / 5
Workflow Clarity	Clear sequenced workflow (write, preview vs run by intent, generate-metadata after edits, deploy only when explicitly asked) with validation checkpoints: --dry-run lists stale items before changes, diff regenerated locks and report version bumps, and preview validates before any deploy. Anchor 4 rather than 5: no explicit error-recovery loop after a failed preview, and 'Place scripts in a folder' does not say which folder.	4 / 5
Progressive Disclosure	No bundle files exist and headers are clear, but the multi-language general Windmill guide (preprocessor scripts, per-language placeholder syntax, general principles referencing TypeScript/Python/Go/SQL/etc.) is inlined in a Rust-specific skill where it plausibly belongs in a shared reference file. Anchor 3 ('content that should be separate is inline') — not 2, since structure is present and no references are buried or nested.	3 / 5
	Total	14 / 20 Passed

Description

40%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 a bare trigger statement: it says when to use the skill but not what the skill does. The trigger phrase itself is natural and distinct, but the missing capability list and absence of Windmill context leave it weak on completeness and specificity.

Suggestions

Add a 'what' clause listing concrete capabilities, e.g. 'Write Windmill Rust scripts: main function with serializable return type, cargo dependency block, async runtime handling, preview and metadata generation workflow. MUST use when writing Rust scripts.'

Mention Windmill in the description to distinguish this skill from general Rust-development skills and reduce conflict risk.

Add natural trigger variations users might say, such as 'Windmill Rust script', 'Rust script dependencies', or 'cargo for scripts'.

Dimension	Reasoning	Score
Specificity	"MUST use when writing Rust scripts." names the domain but lists no concrete capabilities — nothing about script structure, cargo dependencies, async handling, or the wmill preview/metadata workflow. This matches anchor 2 ('Names the domain but actions are minimal or generic', e.g. 'Processes PDF files') and not anchor 3, which requires 1-2 concrete actions to be listed.	2 / 5
Completeness	Only the 'when' is present ('MUST use when writing Rust scripts'); the 'what' — what the skill actually does — is entirely absent, exactly matching anchor 2 ('only when is present without what', e.g. 'Use when working with documents'). Anchor 3 requires a clear 'what', which the description lacks.	2 / 5
Trigger Term Quality	"writing Rust scripts" is a natural phrase a user would say, but there are no synonyms, related tooling terms (Windmill, cargo, script preview), or extensions. Matches anchor 3 ('Some relevant keywords but missing common variations or synonyms', e.g. 'Works with PDF files') rather than anchor 4's 'good keyword coverage'.	3 / 5
Distinctiveness Conflict Risk	'Writing Rust scripts' is a fairly distinct niche trigger with minor overlap risk against general Rust-development skills, matching anchor 4 ('Mostly distinct; minor overlap risk with closely related skills'). Not anchor 5: without 'Windmill' in the description, other Rust skills could trigger; not anchor 3: it is far more specific than 'Works with document files'.	4 / 5
	Total	11 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: windmill-labs/windmill
Path: system_prompts/auto-generated/skills/write-script-rust/SKILL.md
Commit: af42c47

Reviewed: 2 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.