rust

Use this guide when working on Rust changes in the FAST monorepo.

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 ./.github/skills/rust/SKILL.md

Quality

Content

72%

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

The content is appropriately lean and well-structured for a short skill, but its guidance is largely abstract. Adding concrete commands and a sequenced, validated workflow for breaking changes would materially improve it.

Suggestions

Provide concrete commands for the breaking-change flow, e.g. how to inspect crate/package versions (cargo pkgid / package.json) and how to wrap a crate with wasm-bindgen.

Turn the breaking-changes guidance into a numbered sequence with a validation checkpoint — verify the version state, then update APIs, then confirm the PR description records the breaking change.

Replace the abstract 'as much as possible any logic... should not be duplicated' with a concrete rule or check Claude can apply when wiring Rust into the NodeJS CLI.

Dimension	Reasoning	Score
Conciseness	The body is lean (~130 words across two short sections), assumes Claude knows what crates and wasm-bindgen are, and contains no padding, matching the score-3 anchor; the only minor lapse is the slightly lecturing 'Understand [semver]'.	3 / 3
Actionability	It gives directional instructions ('should exist within a crate', 'should not be duplicated', 'check the crate and package version', 'update the APIs') but no executable commands, code, or concrete procedures, so it is above the vague score-1 anchor but short of the copy-paste-ready score-3 anchor.	2 / 3
Workflow Clarity	The breaking-changes section implies a loose sequence (check version -> if prerelease update APIs -> capture in PR descriptions) but has no numbered steps or validation checkpoints, and a destructive API change without verification caps it at 2.	2 / 3
Progressive Disclosure	At under 50 lines with no bundle files or external references needed, the two clearly headed sections (crate/CLI overview and Breaking changes) are well organized, satisfying the simple-skill score-3 allowance.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 provides a clear, third-person trigger for when to use the skill but is thin on what it actually does. It names the domain well yet lacks concrete actions and broader trigger-term coverage.

Suggestions

Add concrete actions to the description, e.g. building, testing, wrapping crates with wasm-bindgen, and managing semver/breaking changes.

Expand trigger terms beyond "Rust changes" to natural variations users might say: cargo, crate, wasm-bindgen, or NodeJS/Rust interop.

State what the skill does, not just when to use it — e.g. 'Guides Rust crate development and NodeJS CLI wrapping; use when...' to satisfy both the what and the when.

Dimension	Reasoning	Score
Specificity	It names a concrete domain ("Rust changes in the FAST monorepo") but lists no concrete actions — "working on" is vague, so it sits between the abstract score-1 anchor and the multi-action score-3 anchor.	2 / 3
Completeness	An explicit "Use this guide when..." trigger answers the "when", but the "what" is only weakly implied ("this guide") with no stated capabilities, so it does not reach the both-answered score-3 anchor.	2 / 3
Trigger Term Quality	"Rust changes" and "FAST monorepo" are reasonably natural phrases a user might say, but coverage is thin and omits common variations such as cargo, crate, wasm, or bindgen, matching the score-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The FAST monorepo plus Rust qualifier carves a fairly clear niche, but the single broad trigger ("Rust changes") could still overlap with other Rust-related skills, matching the score-2 anchor.	2 / 3
	Total	8 / 12 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: microsoft/fast
Path: .github/skills/rust/SKILL.md
Commit: 27a4304

Reviewed: 1 day 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.