check

Run Rust fmt, clippy, and unit tests. Use after making Rust code changes.

Quality

96%

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

Quality

Content

100%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 exemplary for a simple skill: exact, executable commands in a clear order with built-in failure-and-fix loops, no padding, and appropriate scope. Nothing material is missing.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: three exact commands with inline fix instructions and a one-line reporting instruction, with no padding or explanation of concepts Claude already knows; matches the 'every token earns its place' anchor.	5 / 5
Actionability	All three commands are fully executable and copy-paste ready with exact flags (e.g. 'cargo clippy --locked --all-targets --all-features -- -D warnings'), and each includes remediation guidance, matching the anchor for fully executable commands covering the common cases.	5 / 5
Workflow Clarity	Steps are clearly sequenced and each is itself a validation checkpoint with an explicit error-recovery loop ('if formatting fails, run cargo fmt --all to fix it', 'fix any warnings'); the operations are non-destructive, so the destructive-operation cap does not apply.	5 / 5
Progressive Disclosure	This is a simple single-purpose skill under 50 lines with no need for external references, and no bundle files exist; the well-organized numbered list satisfies the simple-skill exception for a top score.	5 / 5
	Total	20 / 20 Passed

Description

92%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.

A strong description: concise, third-person, lists concrete actions, and includes an explicit 'Use when' trigger clause. The only weakness is mild — it omits synonyms like 'lint' and 'formatting' that some users would use instead of 'clippy' and 'fmt'.

Suggestions

Add natural synonyms to the trigger clause, e.g. 'Use after making Rust code changes, when the user asks to lint, format, or run tests.'

Mention 'cargo' explicitly (e.g. 'Run cargo fmt, clippy, and tests') since users often phrase the request in terms of the toolchain command.

Dimension	Reasoning	Score
Specificity	"Run Rust fmt, clippy, and unit tests" names the domain plus three concrete actions that fully cover the skill's scope, matching the anchor for multiple specific concrete actions with comprehensive coverage; there are no meaningful gaps, so it does not fall to 4.	5 / 5
Completeness	It explicitly answers both what ("Run Rust fmt, clippy, and unit tests") and when ("Use after making Rust code changes") with a concrete trigger phrase, matching the top anchor; the 'when' clause is more concrete than the anchor-4 example's generic 'when working with PDF files'.	5 / 5
Trigger Term Quality	Terms like "Rust", "fmt", "clippy", "unit tests", and "Rust code changes" are ones users would naturally say, but common synonyms and variations ("lint", "linting", "formatting", "cargo") are missing, fitting the anchor for good coverage with a few natural terms absent rather than comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The description carves out a clear niche (Rust tooling checks) with distinct trigger words like clippy and fmt, so it is unlikely to fire for unrelated skills; no overlap concerns.	5 / 5
	Total	19 / 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: katanemo/plano
Path: .claude/skills/check/SKILL.md
Commit: 72002a6

Reviewed: 18 hours 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.