systems-programming-rust-project

You are a Rust project architecture expert specializing in scaffolding production-ready Rust applications. Generate complete project structures with cargo tooling, proper module organization, testing

Quality

50%

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 ./skills/systems-programming-rust-project/SKILL.md

Quality

Content

46%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 delivers genuinely executable scaffolding guidance with a clear numbered flow and concrete code for the main project types, but it is token-heavy boilerplate Claude could largely produce unaided, has no verification step for the generated project, and crams five full templates into one file instead of splitting them into references. Restructuring toward an overview plus per-type reference files with a build/test validation step would raise most dimensions.

Suggestions

Split the per-project-type templates (binary, library, workspace, web API) into references/ files (e.g. references/web-api.md) and keep SKILL.md as a concise overview that links to them one level deep.

Trim boilerplate Claude already knows (standard clap derive structs, Display/Error impls, Makefile targets) down to project-specific decisions, and move pinned version numbers into a clearly dated or deprecation-aware section.

Add an explicit validation checkpoint to the workflow, e.g. "After scaffolding, run `cargo build && cargo test && cargo clippy -- -D warnings` and fix any errors before delivering the project."

Dimension	Reasoning	Score
Conciseness	The ~440-line body inlines complete boilerplate templates (clap derive CLI, a Display/Error enum, an Axum router, a Makefile, rustfmt/clippy configs) that Claude already knows how to generate, and pins time-sensitive versions (clap 4.5, tokio 1.36, axum 0.7, rust-version 1.75) with no deprecation context. This is noticeably verbose rather than severely padded prose, matching anchor 2.	2 / 5
Actionability	Instructions provide real, executable code and commands (cargo new, full Cargo.toml, main.rs, cli.rs, workspace manifests), but with minor gaps: the referenced commands/, config.rs, and handler modules have no bodies, and error.rs lacks From<std::io::Error> impls so `?` on IO calls would not compile. Mostly executable with minor gaps fits anchor 4 rather than the fully copy-paste-ready coverage of anchor 5.	4 / 5
Workflow Clarity	Steps 1-7 form a clear sequence (analyze project type, cargo init, generate structure per type, configure dev tools), but there are no validation checkpoints at all — the skill never instructs running `cargo build`/`cargo test`/`cargo clippy` to verify the generated scaffold. Sequence present with checkpoints missing matches anchor 3, not anchor 4's "most checkpoints present".	3 / 5
Progressive Disclosure	The skill is a monolith: all five project-type templates (binary, library, workspace, web API, dev tooling) are fully inlined in SKILL.md with no references/ bundle, no navigation to detail files, and no offloading of content that clearly belongs in separate per-type files. Inlining this much template content matches anchor 2; it avoids anchor 1 only because section headers keep it navigable.	2 / 5
	Total	11 / 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 names a concrete, well-scoped capability (Rust project scaffolding with cargo tooling and module organization), but it is written in second person, cuts off mid-sentence, and lacks any "Use when..." trigger guidance. It is distinguishable from other skills yet under-specified for triggering and completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to create, scaffold, or set up a new Rust project, crate, workspace, or Axum web service."

Complete the truncated sentence and use third-person voice ("Generates complete project structures with cargo tooling, proper module organization, testing setup, and configuration") instead of "You are a Rust project architecture expert...".

Include natural trigger variations such as "new Rust project", "cargo new", "crate", "workspace", and "CLI app" so the skill fires on the phrases users actually say.

Dimension	Reasoning	Score
Specificity	"Generate complete project structures with cargo tooling, proper module organization, testing" lists several concrete actions (base 4), but the second-person opening "You are a Rust project architecture expert" triggers the mandated 1-point specificity penalty, lowering it to 3. The actions themselves are concrete, so it does not fall to 2.	3 / 5
Completeness	The "what" is clear (generate Rust project structures with cargo tooling, module organization, testing), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. The truncated final phrase ("...testing") further weakens the what.	3 / 5
Trigger Term Quality	"Rust", "cargo", and "scaffolding" are natural terms users would say, but common variations like "create/set up a new Rust project", "crate", "workspace", "CLI", or "Axum" are missing. Coverage is relevant but narrow, matching anchor 3 rather than anchor 4's fuller keyword set.	3 / 5
Distinctiveness Conflict Risk	"Rust project architecture", "scaffolding", and "cargo" carve out a clear niche with minimal conflict risk against non-Rust skills. It is not 5 because it could still overlap with generic project-init or other-language scaffolding skills, and no explicit triggers reinforce the boundary.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/systems-programming-rust-project/SKILL.md
Commit: 7b534bc

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