CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

systems-programming-rust-project

Scaffold Rust projects with Cargo, module organization, testing, and development tooling. Use when starting Rust applications or libraries and establishing their project structure.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/systems-programming-rust-project/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body delivers genuinely executable scaffolding material — pinned Cargo.toml templates, idiomatic directory trees, and dev-tool configs — but buries it in circular filler and standard Rust boilerplate Claude already knows. The workflow is clearly sequenced yet lacks any build/test validation step, and the monolithic 435-line file ignores progressive disclosure entirely.

Suggestions

Split each project-type template (binary, library, workspace, web API) into its own reference file (e.g., references/binary-template.md, references/web-api-template.md) and keep SKILL.md as a concise dispatch overview that points to them, cutting the main file by ~70%.

Delete the circular meta-sections ("Use this skill when", "Do not use this skill when", "Context", "Requirements") and the boilerplate code Claude already knows (clap derive structs, Display/Error impls), keeping only the non-obvious choices: directory conventions, dependency/version pins, and profile settings.

Add an explicit validation step to the workflow, e.g., "After scaffolding, run `cargo build && cargo test` and fix any errors before delivering the project," and either provide the missing module templates (commands/init.rs, config.rs, library error.rs) or remove them from the trees so the scaffold actually compiles.

DimensionReasoningScore

Conciseness

The ~435-line body includes padded circular filler ("Do not use this skill when: The task is unrelated to rust project scaffolding", "Requirements: Take the requirements, target, and scope from the user's request") and roughly 150 lines of boilerplate Claude already knows — standard clap derive structs, a Display/std::error::Error impl, and a canonical axum hello-world main.rs. This matches anchor 2 ("noticeably verbose; several unnecessary explanations or padded sections"); it avoids anchor 1 because there is no prose explaining basic concepts and the directory trees and pinned dependency versions carry real value.

2 / 5

Actionability

Guidance is concrete and executable throughout: `cargo new project-name`, complete Cargo.toml templates with pinned versions, full directory trees, and Makefile/rustfmt.toml/clippy.toml configs. It falls short of anchor 5 because the templates don't assemble into a compiling project — referenced modules (commands/init.rs, commands/run.rs, config.rs, library core.rs and error.rs) are shown in trees but never defined, and WebAssembly is listed as a project type with no template at all.

4 / 5

Workflow Clarity

The numbered sequence (analyze project type → initialize with cargo → generate the matching structure → configure dev tools) is clear and well-dispatched by project type, matching "steps listed". However, validation checkpoints are entirely absent — the workflow never verifies the scaffold with `cargo build` or `cargo test` — which matches anchor 3 rather than 4, where most checkpoints would be present.

3 / 5

Progressive Disclosure

Section headers and numbered subsections give the body reasonable structure, but ~400 lines of per-project-type templates (binary, library, workspace, web API) are inlined in a single SKILL.md with no bundle files at all. This matches anchor 3 ("some structure… content that should be separate is inline"); it is better than anchor 2 because the content is well-sectioned rather than a header-less wall, but far from anchor 4 since none of the template bulk is split into reference files.

3 / 5

Total

12

/

20

Passed

Description

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

A strong description: concrete actions, natural trigger terms, explicit what-and-when structure, and a clearly distinct Rust/Cargo niche. Its main weaknesses are minor — the when-clause restates the what rather than adding user-mention triggers, and a few natural synonyms (crate, workspace) plus the web-API/workspace capabilities the body actually delivers are left out.

DimensionReasoningScore

Specificity

"Scaffold Rust projects with Cargo, module organization, testing, and development tooling" lists several concrete actions (scaffolding, module organization, testing, tooling setup). It falls short of anchor 5 because coverage has minor gaps — workspace, web-API, and WebAssembly scaffolding (all delivered by the body) are unmentioned — and "development tooling" is generic.

4 / 5

Completeness

Both what and when are explicit: "Scaffold Rust projects with Cargo, module organization, testing, and development tooling" plus "Use when starting Rust applications or libraries and establishing their project structure". The when-clause could be more specific — it largely restates the what and omits user-side trigger phrasing (e.g., "when the user asks to set up a new Rust project"), matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Natural terms are present: "Rust projects", "Cargo", "Rust applications", "libraries", "project structure" — phrases users would genuinely say. Not anchor 5 because common variations like "crate", "workspace", or "Cargo.toml" are missing; not anchor 3 because keyword coverage is good and natural rather than merely "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

"Scaffold Rust projects with Cargo" carves out a clear niche (Rust project scaffolding) with domain-distinct triggers (Rust, Cargo, starting applications/libraries), so it is unlikely to fire for the wrong skill — matching the anchor-5 "clear niche with distinct triggers; minimal conflict risk".

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/systems-programming-rust-project/SKILL.md

Reviewed

Table of Contents

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.