CtrlK
BlogDocsLog inGet started
Tessl Logo

rust-check

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

61

Quality

72%

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

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 body is concise and well-organized for a simple single-command skill, but its post-check steps are vague and it lacks an explicit verify-re-run feedback loop. Tightening the workflow would raise the two lowest dimensions.

Suggestions

Make the feedback loop explicit, e.g. step 4: 'Re-run `cargo check` to confirm all errors are resolved before proceeding.'

Tighten steps 2–3 with concrete guidance, such as reading the `error[E...]` lines and fixing the first error before re-running, since later errors often cascade from earlier ones.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it gives a command, a short numbered list, and one example without explaining concepts Claude already knows, so every core token earns its place.

3 / 3

Actionability

It provides a concrete executable command ("cargo check") and a copy-paste example ("cargo check --all-targets"), but steps 2–3 ("Analyze the output for errors and warnings", "Fix any issues found") are vague and lack specifics on how to interpret or address errors.

2 / 3

Workflow Clarity

The steps are clearly numbered and sequenced, but the natural feedback loop — re-run `cargo check` after fixing to confirm errors are resolved — is missing or only implicit.

2 / 3

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and is organized into clear 'How to use' and 'Example' sections, satisfying the simple-skill allowance for a top score.

3 / 3

Total

10

/

12

Passed

Description

72%

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, natural-sounding, and clearly niched, but it omits an explicit 'Use when...' trigger clause, capping its completeness. Adding trigger guidance would lift the highest-weighted dimension.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to check a Rust project for compile/build errors or before running other cargo commands.'

Optionally broaden trigger-term coverage with common variations like 'build errors', 'won't compile', or 'compilation errors'.

DimensionReasoningScore

Specificity

Names a concrete action ("Run cargo check") and outcome ("find compile errors") but lists only a single action rather than multiple specific actions, matching the 'names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

It clearly states what the skill does but lacks a "Use when..." trigger clause; per the guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

"cargo check", "Rust project", and "compile errors" are exactly the natural terms a user would say when they need this skill, giving good coverage for this narrow domain.

3 / 3

Distinctiveness Conflict Risk

Scoped specifically to running cargo check for Rust compile errors, a clear niche with distinct triggers that is 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
Hmbown/CodeWhale
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.