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

Discovery

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 is truncated mid-sentence, which immediately undermines its effectiveness. While it identifies the domain (Rust project scaffolding) and mentions some relevant capabilities, it lacks a 'Use when...' clause and uses second-person voice ('You are'), both of which are penalized by the rubric. The description needs to be completed, rewritten in third person, and augmented with explicit trigger conditions.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'new Rust project', 'Rust boilerplate', 'Cargo.toml setup', 'crate structure', or 'Rust workspace'.

Rewrite in third person voice (e.g., 'Scaffolds production-ready Rust applications with cargo tooling...') instead of the current 'You are...' framing.

Complete the truncated sentence and list specific concrete actions such as 'generates Cargo.toml configurations, sets up workspace layouts, creates module hierarchies, configures CI pipelines, and adds test scaffolding'.

Dimension	Reasoning	Score
Specificity	Names the domain (Rust project architecture) and some actions (scaffolding, generate 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. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the description is also truncated mid-sentence, further reducing quality.	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 reduces naturalness.	2 / 3
Distinctiveness Conflict Risk	The focus on Rust project scaffolding is somewhat specific, but 'project structures', 'testing', and 'module organization' could overlap with general code generation or other language-specific scaffolding skills. The Rust + cargo combination provides some distinctiveness but not enough to be clearly niche.	2 / 3
	Total	7 / 12 Passed

Implementation

42%

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

The skill provides highly actionable, executable Rust scaffolding templates but is severely bloated — it inlines complete boilerplate for five different project types that Claude could largely generate from minimal prompts. It lacks validation checkpoints (e.g., 'cargo check' after scaffolding) and has no progressive disclosure, dumping everything into a single monolithic file. The generic 'Use this skill when' / 'Do not use this skill when' sections and context preamble add no value.

Suggestions

Split each project type (binary, library, workspace, web API, WASM) into separate referenced files and keep SKILL.md as a concise overview with a decision tree pointing to the right template.

Remove explanations Claude already knows (e.g., what binary vs library projects are, that cargo new initializes git) and trim boilerplate to only non-obvious, opinionated choices.

Add explicit validation checkpoints after scaffolding: 'Run `cargo check` to verify compilation' and 'Run `cargo test` to confirm test setup works.'

Remove the generic 'Use this skill when / Do not use this skill when' and 'Limitations' sections, which add no actionable information beyond what the skill title already conveys.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Covers five different project types (binary, library, workspace, web API, WASM) with full boilerplate code for each, much of which Claude already knows how to generate. The 'Use this skill when / Do not use this skill when' sections are generic filler. Repeating full Cargo.toml files, complete module structures, and standard Rust patterns wastes significant token budget.	1 / 3
Actionability	Provides fully executable, copy-paste ready code examples including complete Cargo.toml files, main.rs, cli.rs, error.rs, Makefile, and configuration files. Commands are specific (cargo new, cargo clippy) and code is real, not pseudocode.	3 / 3
Workflow Clarity	Steps are numbered (1-7) and sequenced logically from analysis through initialization to tool configuration. However, there are no validation checkpoints — no step says 'run cargo check to verify the project compiles' or 'run cargo test to confirm the scaffold works.' For a scaffolding task that generates multiple files, a verification step is important but missing.	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 SKILL.md serving as an overview that points to them.	1 / 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: 76aea27

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