rust-coding-style

HASH Rust coding style. Use when writing or reviewing Rust code, choosing types, imports, function arguments, or naming.

Quality

75%

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 ./.agents/skills/rust-coding-style/SKILL.md

Quality

Content

72%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 a highly actionable, lean Rust style reference with concrete commands and code, but it is a flat catalog rather than a sequenced workflow and keeps all material inline with no progressive-disclosure structure.

Suggestions

Frame the clippy/rustfmt/doc commands as an explicit validation loop (run clippy -> fix -> re-run) to add workflow checkpoints.

Move the long Import Style Good/Bad example blocks into a reference file and signal it from SKILL.md to improve progressive disclosure.

Deduplicate the newtype guidance that appears in both the "Type System" and "Types" sections.

Dimension	Reasoning	Score
Conciseness	Mostly lean bullet rules that assume Rust competence with no concept over-explanation, but the Type System/Types newtype guidance is duplicated and the Import Style Good/Bad block is lengthy.	4 / 5
Actionability	Provides exact commands ("cargo clippy --all-features --all-targets --no-deps", "cargo doc --no-deps --all-features", "rustfmt") and copy-paste-ready code examples for newtypes, async signatures, imports, and assertions.	5 / 5
Workflow Clarity	Functions as a rules catalog rather than a sequenced workflow; clippy/rustfmt/doc commands exist but are not framed as an explicit validate->fix->retry loop with checkpoints.	3 / 5
Progressive Disclosure	No bundle files exist and ~218 lines are inlined in SKILL.md; section headers are clear, but long Good/Bad example blocks that could live in reference files are inlined with no external references signaled.	3 / 5
	Total	15 / 20 Passed

Description

78%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 a solid, mostly concrete trigger statement with an explicit Use-when clause and a clear Rust niche. Its main weaknesses are the unexplained "HASH" token at the start and a terse what-statement.

Suggestions

Remove or replace the leading "HASH" token, which reads as an unfilled template placeholder and weakens the what-statement.

Add common natural trigger terms (e.g., "rustfmt", "clippy", "format", "lint") so the description matches phrasings users actually say.

Tighten the what-statement to name the skill's concrete output (e.g., "Applies project Rust coding conventions...") instead of the generic "HASH Rust coding style".

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("writing or reviewing Rust code, choosing types, imports, function arguments, or naming"), but the templated "HASH" lead and lack of comprehensive coverage keep it below a 5.	4 / 5
Completeness	Both a what ("HASH Rust coding style") and an explicit when ("Use when writing or reviewing Rust code, choosing types, imports, function arguments, or naming") are present, though the what is terse and slightly generic.	4 / 5
Trigger Term Quality	Natural phrases like "writing or reviewing Rust code", "types", "imports", and "naming" appear, but common variations such as "rustfmt", "clippy", or "format" are absent from the description.	4 / 5
Distinctiveness Conflict Risk	Rust-specific niche with Rust-typed triggers (types, imports, function arguments, naming) gives it a clear, distinct trigger surface with minimal conflict risk against non-Rust skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: hashintel/hash
Path: .agents/skills/rust-coding-style/SKILL.md
Commit: a6f5727

Reviewed: 4 days 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.