CtrlK
BlogDocsLog inGet started
Tessl Logo

rust-backend

Rust coding guidelines for the Windmill backend. MUST use when writing or modifying Rust code in the backend directory.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, highly actionable set of Windmill-specific Rust patterns with executable examples and clean section organization. It avoids conceptual padding and assumes Claude's competence throughout.

DimensionReasoningScore

Conciseness

Lean pattern-oriented guidance with executable snippets and no padding explaining concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Provides concrete, executable Rust examples (sqlx::query_as!, spawn_blocking, Box<RawValue>, serde derives, Axum extractor destructuring) with Correct/Wrong contrasts that are copy-paste ready.

3 / 3

Workflow Clarity

A well-organized patterns/reference skill rather than a multi-step process; sections are unambiguous and rule-based, satisfying the simple-skills allowance.

3 / 3

Progressive Disclosure

A single self-contained SKILL.md with clear section organization and no nested or broken references; no bundle files are needed or present.

3 / 3

Total

12

/

12

Passed

Description

75%

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 clearly pairs a scoped 'what' with an explicit 'MUST use when' trigger and is well-distinguished by its Windmill/backend niche. It could be improved by naming a few more concrete capabilities and trigger-term variations.

DimensionReasoningScore

Specificity

Names the domain ('Rust coding guidelines for the Windmill backend') and actions ('writing or modifying Rust code'), but does not list multiple concrete capabilities like error handling, SQLx, or async patterns.

2 / 3

Completeness

Explicitly states both what ('Rust coding guidelines for the Windmill backend') and when ('MUST use when writing or modifying Rust code in the backend directory').

3 / 3

Trigger Term Quality

Includes relevant natural terms ('Rust', 'Windmill backend', 'backend directory', 'writing or modifying Rust code') but offers few synonym variations a user might say.

2 / 3

Distinctiveness Conflict Risk

Scoped tightly to the Windmill backend directory, giving it a clear niche with triggers unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
windmill-labs/windmill
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.