check

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

Quality

93%

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

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

An efficient, fully executable checks workflow with a clear sequence and one explicit feedback loop. The only gap is that retry loops for clippy and test failures are implicit rather than spelled out.

Suggestions

Make the feedback loops for clippy and tests explicit, e.g. "fix any warnings, then re-run clippy until clean" and "if tests fail, fix and re-run `cargo test --lib` until all pass".

Consider an explicit ordering note that each step must pass before proceeding to the next, to strengthen the validation checkpoint sequencing.

Dimension	Reasoning	Score
Conciseness	The body is lean — "Run all local checks in order:" followed by three commands with brief annotations and no explanation of what fmt/clippy/tests are; every token earns its place and Claude's competence is assumed.	5 / 5
Actionability	Three fully executable, copy-paste-ready commands (e.g. `cd crates && cargo clippy --locked --all-targets --all-features -- -D warnings`) cover the common cases with exact flags.	5 / 5
Workflow Clarity	A clear numbered sequence with an explicit fix loop on step 1 ("if formatting fails, run cargo fmt --all to fix it"), but steps 2 and 3 only imply retry ("fix any warnings", "ensure all unit tests pass") rather than spelling out a validate->fix->retry loop, leaving a minor validation gap.	4 / 5
Progressive Disclosure	This is a simple skill under 50 lines with no need for external references; the numbered list is well-organized, so per the simple-skill exception progressive disclosure scores 5 without separate files.	5 / 5
	Total	19 / 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 tight, third-person description that answers both what and when with concrete, domain-specific trigger terms. Only minor room for improvement in synonym coverage.

Dimension	Reasoning	Score
Specificity	"Run Rust fmt, clippy, and unit tests" names the Rust domain and lists three concrete, distinct actions (fmt, clippy, unit tests), which is comprehensive coverage for a checks skill; not 4 because there are no real coverage gaps.	5 / 5
Completeness	It explicitly states 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; not 4 because the 'when' is explicit and specific.	5 / 5
Trigger Term Quality	Natural Rust-dev terms appear ("fmt", "clippy", "unit tests", "code changes"), but common synonyms like "lint", "formatting", "cargo check", or "build" are missing, so it falls just short of comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	"Rust fmt, clippy, and unit tests" scoped to "after making Rust code changes" carves a clear Rust-specific niche with minimal overlap against other skills.	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: 003c36a

Reviewed: 3 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.