rust-check

Run cargo check on the current Rust project to find compile errors

Quality

66%

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 ./crates/tui/assets/plugins/rust-toolkit/skills/rust-check/SKILL.md

Quality

Content

80%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 concise and well-structured with executable examples, but the workflow lacks an explicit fix-and-reverify feedback loop, which is the weakest dimension.

Suggestions

Add a re-verification step to the workflow, e.g. '4. Re-run `cargo check` to confirm no errors remain' to close the fix-and-recheck feedback loop.

Make step 3 more actionable by pointing to how to read cargo error output (e.g. file:line:col format) rather than just 'fix any issues found'.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: it states the trigger, three short steps, and one copy-paste example without explaining concepts Claude already knows about Rust or cargo.	5 / 5
Actionability	Provides executable commands ('cargo check' in the project root, 'cargo check --all-targets') but stops short of guidance for acting on the errors beyond 'fix any issues found'.	4 / 5
Workflow Clarity	Lists a clear run-analyze-fix sequence but omits an explicit re-verification step (re-run cargo check to confirm the fix), leaving a validation checkpoint gap.	3 / 5
Progressive Disclosure	Under 50 lines with no need for external references, organized into clear 'How to use' and 'Example' sections; per the simple-skill guideline this scores 5.	5 / 5
	Total	17 / 20 Passed

Description

53%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 specific and distinct but lacks an explicit 'Use when...' trigger clause, capping completeness. Trigger terms are relevant but not comprehensive across synonyms.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases, e.g. 'Use when the user wants to verify Rust code compiles, check for compile/build errors, or before committing Rust changes.'

Broaden trigger terms with synonyms and file extensions like 'build errors', 'lint', '.rs', or 'does not compile'.

Dimension	Reasoning	Score
Specificity	Names the Rust domain and one concrete action ('Run cargo check') plus purpose ('find compile errors'), but covers only a single action rather than comprehensive coverage.	3 / 5
Completeness	Has a clear 'what' but no 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant natural terms ('cargo check', 'compile errors', 'Rust project') but misses common variations like 'build errors', 'lint', or the .rs extension.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (cargo check for compile errors) with minimal conflict risk, though it could overlap slightly with cargo build or cargo clippy skills.	4 / 5
	Total	13 / 20 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: Hmbown/CodeWhale
Path: crates/tui/assets/plugins/rust-toolkit/skills/rust-check/SKILL.md
Commit: 1117692

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