CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-script-rust

MUST use when writing Rust scripts.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 Rust-specific guidance is exemplary — complete executable examples and a carefully gated workflow with validation and feedback loops. Weaknesses are the repeated 'not a deploy' caveats and the inlined all-language Windmill material (resource types, preprocessors) that should live in a shared reference and inflates the token budget of a Rust skill.

Suggestions

Move the 'General Principles' and 'Preprocessor Scripts' sections (all-language Windmill material) into a shared reference file and keep only Rust-relevant guidance inline.

State the 'not a deploy' distinction once in the CLI list and reference it elsewhere instead of repeating it in the preview, metadata, and after-writing sections.

Split the long metadata paragraph into short directives to cut hedged compound sentences.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious operational knowledge (preview-vs-run intent rules, lock/hash sync semantics, importer propagation), but 'not a deploy' is restated in the CLI list, the preview section, the metadata section, and the after-writing section, and the metadata guidance uses long hedged compound sentences. Not a 5 because that repetition and hedging could be trimmed.

4 / 5

Actionability

Copy-paste-ready Rust examples (owned-args main returning anyhow::Result<Serialize> struct, cargo deps in a //! doc comment, sync main wrapping a tokio runtime) plus exact commands with flags: 'wmill script preview <path> -d', 'wmill generate-metadata --dry-run', 'rehash', 'f/foo' scoping, and 'wmill resource-type list --schema'. These cover the common cases end to end.

5 / 5

Workflow Clarity

The edit → preview → generate-metadata → deploy flow is sequenced with explicit checkpoints: preview validates before any deploy, --dry-run lists stale items when regeneration touches more than expected (a feedback loop), the regenerated .lock must be diffed to surface version bumps, and deploy is gated on explicit user request. Not a 4 because validation and error-recovery loops are present at each risky step.

5 / 5

Progressive Disclosure

There are no bundle files (references/, scripts/, assets/ are absent) and everything is inlined, including 'General Principles' and 'Preprocessor Scripts' sections that cover non-Rust languages (TypeScript, Python, SQL, Bash, PowerShell, Ansible). That cross-language material belongs in a shared reference file rather than this Rust-specific skill. Not a 4 because inlining it is a real organizational gap, not a minor one.

3 / 5

Total

17

/

20

Passed

Description

36%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 has a clear, forceful trigger ('MUST use when writing Rust scripts') but completely omits what the skill does and never mentions Windmill, the platform it targets. This weakens discovery for users who name the tool, and risks mis-triggering for ordinary Rust work.

Suggestions

State the 'what': e.g. 'Write Windmill scripts in Rust: main structure, owned arguments, anyhow::Result return types, cargo dependency declaration, and async runtime handling.'

Include 'Windmill' as a trigger term so users naming the platform surface the skill.

Add natural variations such as 'Rust script', 'script in Rust', or '.rs' to broaden trigger coverage.

DimensionReasoningScore

Specificity

'MUST use when writing Rust scripts' names the domain but states no concrete actions — nothing about script structure, dependencies, or the CLI workflow the body actually covers. It is not a 3 because no 'what' action is listed at all.

2 / 5

Completeness

Only the 'when' is present ('MUST use when writing Rust scripts') with no 'what' — the skill's capabilities are entirely unstated. This matches the anchor 'only when is present without what'; not a 3 because the 'what' is absent, not merely weak.

2 / 5

Trigger Term Quality

'writing Rust scripts' is a natural phrase, but coverage is sparse: no synonyms ('script in Rust', '.rs'), and 'Windmill' — the platform this skill is for — is absent, so users naming the tool would not trigger it. Not a 4 because of these missing variations.

3 / 5

Distinctiveness Conflict Risk

'Rust scripts' is a niche but without 'Windmill' the description would also trigger for non-Windmill Rust scripting tasks, creating real overlap with general Rust assistance. Not a 4 because the missing platform qualifier leaves genuine mis-trigger risk.

3 / 5

Total

10

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.