write-script-rust

MUST use when writing Rust scripts.

Quality

64%

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

75%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 content is highly actionable with complete executable code and commands, and is well structured for a single-file skill. Its main weakness is repetition of the deploy-vs-preview intent guidance across sections and prose-driven rather than explicitly numbered workflow sequencing.

Suggestions

Consolidate the repeated preview-vs-run and deploy-only-when-asked guidance into one section to remove redundancy across "Preview vs run", "After writing", and "Keep metadata in sync".

Consider a short numbered checklist for the post-edit flow (edit -> generate-metadata [--dry-run] -> preview -> optional deploy) to make the sequence and checkpoints explicit.

If deploy guidance is load-bearing, either inline a brief summary of the AGENTS.wmill.md Deploying steps or bundle a short reference so the skill is self-contained.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude knows Rust/cargo, but the preview-vs-run and deploy intent rules are repeated across multiple sections and some policy prose could be tightened, fitting mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides fully executable commands (wmill script preview, generate-metadata, rehash, --dry-run) and complete copy-paste Rust examples covering both sync and async main with cargo manifests, matching fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The edit -> generate-metadata -> preview -> optional deploy flow has explicit intent gates and a dry-run checkpoint plus a diff-and-report feedback step, but it is prose-driven rather than a numbered sequence with an explicit validate-fix-retry loop, fitting clear sequence with most checkpoints and minor gaps.	4 / 5
Progressive Disclosure	No bundle files are present and the single-file body is well-organized with clear headers; the load-bearing reference to the non-bundled AGENTS.wmill.md Deploying section keeps it from a 5, fitting good structure with mostly clear references.	4 / 5
	Total	16 / 20 Passed

Description

53%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 short and has an explicit trigger, but it names the domain without concrete actions and gives almost no statement of what the skill actually does. It is distinct enough (Rust-specific) but underspecified on capability.

Suggestions

Add 2-3 concrete actions the skill performs, e.g. "Scaffold Rust wmill scripts with a cargo manifest, run them locally with wmill script preview, and regenerate .script.yaml metadata."

Expand trigger coverage with natural synonyms users might say, such as "Rust code", "Cargo", or ".rs files".

Make the "what" explicit rather than implied by the trigger alone, so it answers both what it does and when to use it.

Dimension	Reasoning	Score
Specificity	The description names the domain ("writing Rust scripts") but lists no concrete actions, matching the anchor for naming the domain with minimal or generic actions.	2 / 5
Completeness	It has an explicit "use when" trigger ("MUST use when writing Rust scripts") but the "what" (what the skill does with the scripts) is barely stated, matching the anchor for a clear what with missing or weak when; here the what is the weak side.	3 / 5
Trigger Term Quality	"writing Rust scripts" is a relevant natural phrase but coverage is thin, missing synonyms like "Rust code", "Cargo", or ".rs", fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"writing Rust scripts" is Rust-scoped and unlikely to trigger for unrelated skills, matching mostly distinct with minor overlap risk; it lacks the richer trigger set needed for a 5.	4 / 5
	Total	12 / 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: 74af4ed

Reviewed: about 18 hours 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.