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

61%

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

65%

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

The skill is highly actionable with concrete, executable scaffolding for multiple Rust project types, but it is a long monolithic document that duplicates boilerplate, embeds version pins inline, and lacks both validation checkpoints and any progressive disclosure into reference files.

Suggestions

Add a verification step to the workflow (e.g. 'Run `cargo check` then `cargo test` and only report success when both pass') so the scaffold is validated before delivery.

Move the per-project-type structure trees and manifests into reference files (e.g. references/binary.md, references/web-api.md) and keep SKILL.md as an overview with one-level-deep links.

Pull hard version pins (clap, axum, tokio, rust-version) out of the inline examples or into a clearly marked section, so they do not penalize conciseness as they age.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining basic Rust concepts and leans on code, but is padded with heavily duplicated boilerplate across project types and embeds time-sensitive version pins (clap 4.5, axum 0.7, rust-version 1.75) inline rather than in a deprecated/old-patterns section, matching the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It provides fully executable cargo commands, complete Cargo.toml manifests, and ready-to-use main.rs/cli.rs/error.rs examples across binary, library, workspace, and web-API variants — copy-paste ready and concrete.	3 / 3
Workflow Clarity	Steps are numbered and sequenced (analyze → init → generate structure → configure tools → output), but there are no validation checkpoints such as 'run cargo check/build to confirm the scaffold compiles', and the verify-the-output feedback loop is only implicit in the Limitations section.	2 / 3
Progressive Disclosure	Everything lives inline in one large SKILL.md with no reference files and no navigation; the per-project-type trees and manifests are content that could be split into separate reference files, matching the 'some structure but content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 conveys a clear Rust-specific niche and concrete actions, but uses second-person voice, omits an explicit 'Use when...' trigger clause, and truncates mid-sentence at 'testing', leaving completeness and trigger-term coverage below the top level.

Suggestions

Rewrite in third person and drop the second-person opener: e.g. 'Scaffolds production-ready Rust applications, generating complete project structures with cargo tooling, module organization, and testing setup.'

Add an explicit trigger clause such as 'Use when creating a new Rust project, scaffolding a cargo workspace, or setting up a Rust CLI/library/web API.'

Complete the truncated tail of the description ('...testing setup, and configuration following Rust best practices.').

Dimension	Reasoning	Score
Specificity	It lists multiple concrete actions ('Generate complete project structures with cargo tooling, proper module organization, testing'), which would score 3, but the second-person opening ('You are a Rust project architecture expert') triggers the voice penalty that reduces specificity by one point.	2 / 3
Completeness	It clearly states what the skill does but lacks any explicit 'Use when...' trigger guidance, and per the judging guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant keywords exist ('Rust', 'scaffolding', 'cargo', 'module organization') but natural user phrasings like 'set up a new Rust project' or 'create a Rust app' are missing, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	'Rust project scaffolding' with cargo-specific triggers carves out a clear, distinct niche that is unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 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/antigravity-awesome-skills
Path: skills/systems-programming-rust-project/SKILL.md
Commit: d5814bb

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.