CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rust

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

Quality

62%

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

Quality

Content

65%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 admirably lean and well-organized for its size, and its two architectural rules (crate-first logic, no Rust/JS duplication) are clearly stated as principles. However, it gives no concrete commands, file paths, or examples, leaving Claude to guess where the crate lives, how to check versions, and how breaking changes are actually made and shipped.

Suggestions

Add executable specifics to 'Breaking changes': the file paths where the crate and package versions are declared (e.g. Cargo.toml, package.json) and the commands to check or bump them.

Concretize the crate-first rule with a pointer to where the crate and its wasm-bindgen wrapper live in the FAST monorepo, so Claude can navigate there directly.

Turn the breaking-changes paragraph into an explicit numbered sequence with a verification checkpoint (e.g. confirm prerelease state, apply breaking API updates, verify the PR description captures the breaking change).

DimensionReasoningScore

Conciseness

Two short paragraphs under clear headings with zero padding: it assumes Claude knows what semver and wasm bindgen are (linking rather than explaining), so every token earns its place. Fits the anchor 'Lean and efficient; assumes Claude's competence'.

5 / 5

Actionability

The guidance is principle-level: 'check the crate and package version', 'update the APIs with breaking changes as necessary' — no commands, file paths, or code showing how or where to do any of it. Fits 'Minimal concrete guidance; high-level hints but missing the specific steps to execute'; not 3 because there is not even partially executable or pseudocode-level guidance.

2 / 5

Workflow Clarity

'Breaking changes' implies a conditional sequence (check version → if prerelease, update APIs → capture in PR descriptions) but the steps are vague and checkpoints are absent — no instruction on where the crate and package versions live or how to verify the prerelease state. Fits 'sequence present but checkpoints missing or implicit'; not 4 because no validation or verification step exists.

3 / 5

Progressive Disclosure

The skill is well under 50 lines with no need for external references: two clearly headed sections and one appropriately scoped external link (semver.org). Per the simple-skill guideline, this can score 5 with just well-organized sections, which it has.

5 / 5

Total

15

/

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 has an explicit and appropriately scoped trigger ('when working on Rust changes in the FAST monorepo') but completely omits what the skill does. Without any statement of capabilities or concrete actions, a user or Claude cannot distinguish it from a generic Rust helper, and it scores below the midpoint on both specificity and completeness.

Suggestions

Add a 'what' clause listing the skill's concrete capabilities, e.g. 'Maintains the Rust crate and its wasm-bindgen NodeJS CLI, prevents logic duplication between Rust and JS/TS, and manages semver-breaking-change releases.'

Include natural trigger synonyms users would actually say — Cargo, crate, wasm-bindgen, Rust CLI — not just 'Rust changes'.

Keep the existing 'Use this guide when working on Rust changes in the FAST monorepo' trigger but append it to the capability statement so both what and when are explicit.

DimensionReasoningScore

Specificity

"Use this guide when working on Rust changes in the FAST monorepo" names the domain but states no concrete actions or capabilities whatsoever. It matches the anchor 'Names the domain but actions are minimal or generic' — not 1 because the domain is concrete rather than abstract, and not 3 because no action verb or capability is ever listed.

2 / 5

Completeness

The 'when' is explicit ('Use this guide when working on Rust changes') but the 'what' is entirely absent — the description never says what the skill does. This matches the anchor 'only "when" is present without "what"'; it is not 3 because there is no 'what' statement, even a weak one.

2 / 5

Trigger Term Quality

"Rust" and "FAST monorepo" are natural terms a user might say, but common variations are missing — Cargo, crate, wasm-bindgen, or the Rust CLI. This fits the anchor 'Some relevant keywords but missing common variations or synonyms'; 4 would require fuller coverage of the natural phrasing users actually use.

3 / 5

Distinctiveness Conflict Risk

Scoping to Rust changes within the specific FAST monorepo gives a clear niche with mostly distinct triggers, though it could still overlap with generic Rust/Cargo skills. Fits 'Mostly distinct; minor overlap risk with closely related skills'; not 5 because no distinguishing capability language (crate, wasm bindgen, semver) appears to fully separate it.

4 / 5

Total

11

/

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

microsoft/fast

Path

.github/skills/rust/SKILL.md

Revision

9d0011e

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill