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

59%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/systems-programming-rust-project/SKILL.md

Quality

Content

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

Highly actionable scaffolding guidance with complete, executable Cargo.toml and source templates for several project types, but it is a long monolithic file with no progressive disclosure and lacks validation checkpoints to verify generated projects build.

Suggestions

Add an explicit verification step after scaffolding (e.g. run `cargo build` and `cargo test`, fix issues, then report) to introduce a validate->fix->retry loop.

Move the per-project-type templates (library, workspace, web API) into separate reference files under references/ and link to them from SKILL.md for one-level-deep progressive disclosure.

Remove the verbatim repeat of the frontmatter description and filler lines like 'Focus on Rust idioms and scalable architecture.' to tighten the opening.

Dimension	Reasoning	Score
Conciseness	The bulk is concrete, useful code and directory trees, but the opening paragraph repeats the frontmatter description verbatim and filler lines like 'Focus on Rust idioms and scalable architecture.' add little; it is mostly efficient but could be tightened.	3 / 5
Actionability	Provides fully executable, copy-paste-ready artifacts across variants: `cargo new` commands, complete Cargo.toml files, main.rs/cli.rs/error.rs source, Makefile, and rustfmt/clippy configs covering the common scaffolding cases.	5 / 5
Workflow Clarity	A clear numbered sequence exists (analyze type -> cargo init -> generate structure -> configure tools), but there are no validation/verification checkpoints such as running `cargo build`/`cargo test`/`cargo check` to confirm the scaffold compiles.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but no references/scripts/assets bundle exists and all four full project-type templates are inlined in one ~430-line file rather than split into one-level-deep reference files.	3 / 5
	Total	14 / 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 states a clear niche and a few concrete actions but is truncated mid-sentence and omits any explicit 'Use when' trigger guidance, capping completeness at 3. Trigger terms are relevant but lack common synonyms.

Suggestions

Complete the truncated sentence (e.g. '...proper module organization, testing setup, and configuration following Rust best practices').

Add an explicit 'Use when...' clause naming natural triggers like 'scaffold a new Rust project', 'set up a Cargo workspace', or 'create a Rust crate'.

Include synonym/extension terms (crate, workspace, Cargo.toml, axum/actix) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Rust project architecture', 'scaffolding production-ready Rust applications') and lists a few concrete actions ('Generate complete project structures with cargo tooling, proper module organization, testing'), but the sentence is truncated mid-list so coverage is not comprehensive.	3 / 5
Completeness	The 'what' is clear (generate Rust project structures with cargo tooling, modules, testing) but there is no 'Use when...' or equivalent trigger clause, so per the rubric cap completeness stays at 3; the truncation further weakens the 'what'.	3 / 5
Trigger Term Quality	'Rust project' and 'cargo' are natural terms a user might say, but common synonyms/variations like 'crate', 'workspace', 'Cargo.toml', or 'new Rust project' are missing.	3 / 5
Distinctiveness Conflict Risk	'Rust project scaffolding' is a clear niche with distinct triggers and only minor overlap risk with general Rust/cargo skills; it would not trigger for unrelated skills.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/systems-programming-rust-project/SKILL.md
Commit: 57c135b

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.