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

1.29x

Quality

37%

Does it follow best practices?

Impact

84%

1.29x

Average score across 3 eval scenarios

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

The canonical home for this skill is systems-programming-rust-project in sickn33/antigravity-awesome-skills

Quality

Content

42%Scale 1-3

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

This skill is highly actionable with complete, executable code examples for multiple Rust project types, but it is severely bloated. It inlines ~300 lines of boilerplate templates that Claude already knows how to produce, and fails to use progressive disclosure to split distinct project types into separate files. Adding validation steps (e.g., cargo check/build after scaffolding) and dramatically reducing inline content would significantly improve it.

Suggestions

Split each project type (binary, library, workspace, web API, WASM) into separate referenced files (e.g., BINARY.md, LIBRARY.md, WEB_API.md) and keep SKILL.md as a concise overview with navigation links.

Remove boilerplate code that Claude can generate from memory (standard Cargo.toml fields, basic main.rs patterns, .gitignore contents) and focus only on project-specific or non-obvious configurations.

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

Remove the 'Use this skill when / Do not use this skill when' sections which add no value and are generic filler.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Includes massive boilerplate code blocks for every project type (binary, library, workspace, web API) that Claude already knows how to generate. Explains basic concepts like cargo new, .gitignore, and standard Rust project structures that Claude is well-versed in. Most of this content is template code that doesn't add unique value.	1 / 3
Actionability	The code examples are fully executable and copy-paste ready. Cargo.toml files, Rust source files, Makefiles, and configuration files are all complete and concrete with specific version numbers and real dependency configurations.	3 / 3
Workflow Clarity	Steps are numbered and sequenced (analyze type → initialize → generate structure → configure tools), but there are no validation checkpoints. No step says 'verify cargo build succeeds' or 'run cargo check before proceeding.' For a scaffolding task that generates multiple files, a verification step would be important.	2 / 3
Progressive Disclosure	Monolithic wall of content with all five project types fully inlined. The binary, library, workspace, and web API structures with complete code should each be in separate referenced files. No external references are used despite the content being well over 200 lines and covering distinct project archetypes.	1 / 3
	Total	7 / 12 Passed

Description

32%Scale 1-3

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 appears truncated and uses second-person voice ('You are'), which violates the third-person requirement. While it identifies the Rust scaffolding domain and mentions some concrete capabilities, it lacks a 'Use when...' clause and doesn't provide sufficient trigger terms for reliable skill selection from a large pool.

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 initialize a Rust crate.'

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

Include more natural trigger terms users would say: 'new Rust project', 'Cargo.toml', 'Rust workspace', 'crate structure', 'rust boilerplate', '.rs files'

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, further weakening it to a 1.	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 'rust boilerplate'. Also uses second-person framing ('You are') which is atypical.	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 for a 3.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/systems-programming-rust-project/SKILL.md
Commit: 0159794

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