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

37%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/systems-programming-rust-project/SKILL.md

Quality

Content

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a comprehensive but excessively verbose template dump that doesn't respect Claude's existing knowledge of Rust project structures. While the code examples are high-quality and executable, the skill would be far more effective as a concise decision tree pointing to separate files for each project type. The lack of validation checkpoints and the monolithic structure significantly reduce its practical value.

Suggestions

Split each project type (binary, library, workspace, web API) into separate referenced files (e.g., BINARY.md, LIBRARY.md, WORKSPACE.md) and keep SKILL.md as a concise routing overview under 50 lines.

Remove explanations of basic Rust concepts Claude already knows (cargo new, .gitignore patterns, what edition means) and focus only on opinionated architectural decisions.

Add explicit validation checkpoints after scaffolding: 'Run `cargo check` to verify the generated project compiles' and 'Run `cargo test` to confirm test infrastructure works'.

Remove the generic 'Use this skill when' / 'Do not use this skill when' / 'Limitations' boilerplate sections that add no actionable information.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Covers five different project types (binary, library, workspace, web API, WASM) with full boilerplate code that Claude already knows how to generate. Explains basic concepts like cargo new, .gitignore, and standard Rust project structures that Claude is deeply familiar with. The $ARGUMENTS placeholder and generic 'use this skill when' sections add no value.	1 / 3
Actionability	The code examples are fully executable and copy-paste ready — complete Cargo.toml files, main.rs, cli.rs, error.rs, and Axum web server setup. Commands are specific (cargo new, cargo clippy, etc.) and the examples compile as written.	3 / 3
Workflow Clarity	Steps are numbered (1-7) and sequenced logically from project type analysis through tool configuration. However, there are no validation checkpoints — no 'cargo check' or 'cargo test' verification steps between scaffolding stages, and no feedback loops for error recovery. For a scaffolding task that generates multiple files, a validation step is important.	2 / 3
Progressive Disclosure	Monolithic wall of content with no references to external files. All five project types are fully inlined, making the skill extremely long. The different project types (binary, library, workspace, web API) should be split into separate referenced files, with the main SKILL.md providing a concise overview and routing logic.	1 / 3
	Total	7 / 12 Passed

Description

32%

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 identifies the domain (Rust project scaffolding) and mentions some relevant capabilities but appears truncated and lacks a 'Use when...' clause, which is critical for skill selection. It also uses second-person voice ('You are') instead of the required third-person voice, and misses common trigger terms users would naturally use.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create a new Rust project, scaffold a Rust application, set up a Cargo workspace, or generate Rust boilerplate.'

Rewrite in third person voice (e.g., 'Scaffolds production-ready Rust applications with complete project structures...') instead of 'You are a Rust project architecture expert'.

Complete the truncated description and include additional trigger terms like 'new Rust project', 'Cargo.toml', 'workspace', 'crate setup', and 'Rust boilerplate'.

Dimension	Reasoning	Score
Specificity	Names the domain (Rust project architecture) and some actions (scaffolding, generating project structures, cargo tooling, module organization, testing), but the description is truncated and doesn't fully enumerate concrete actions like a score-3 would.	2 / 3
Completeness	The description addresses 'what' (scaffolding Rust projects) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The description also appears truncated, further reducing completeness.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Rust', 'cargo', 'project structures', 'module organization', and 'testing', but misses common user variations like 'new Rust project', 'Cargo.toml', 'workspace', 'crate', or 'boilerplate'. Also uses second-person framing ('You are') which is atypical.	2 / 3
Distinctiveness Conflict Risk	Specifying 'Rust' and 'cargo tooling' provides some distinctiveness from generic code scaffolding skills, but the broad mention of 'testing' and 'module organization' could overlap with general Rust development or testing skills.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 9431b67

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