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

Install with Tessl CLI

npx tessl i github:sickn33/antigravity-awesome-skills --skill systems-programming-rust-project

What are skills?

Review — 48%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 13 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

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 identifies its domain (Rust project scaffolding) and mentions relevant tooling but suffers from missing explicit trigger guidance ('Use when...') which is critical for skill selection. It also uses second person voice ('You are') which violates the third-person requirement, and reads more like a system prompt than a skill description.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'new Rust project', 'Rust boilerplate', 'cargo init', 'Rust workspace setup'

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

Include more natural user keywords: 'Rust template', 'cargo new', 'Rust crate', '.rs files', 'Cargo.toml'

Dimension	Reasoning	Score
Specificity	Names the domain (Rust project architecture) and some actions (scaffolding, generate project structures, cargo tooling, module organization, testing), but lacks comprehensive specific actions like 'create Cargo.toml', 'set up workspace', or 'configure CI pipelines'.	2 / 3
Completeness	Describes what it does (scaffolding Rust projects) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The rubric caps completeness at 2 maximum without explicit triggers, and this has none.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Rust', 'cargo', 'project structures', 'module organization', but missing common user variations like 'new Rust project', 'Rust boilerplate', 'Rust template', 'cargo new', or file extensions like '.rs'.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to Rust ecosystem which helps distinguish it, but 'project architecture' and 'scaffolding' could overlap with general code generation or other language-specific project setup skills.	2 / 3
	Total	7 / 12 Passed

Implementation

64%

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

This skill provides excellent actionable content with complete, executable Rust code examples covering multiple project types. However, it's overly verbose for a skill file, lacking validation checkpoints in the workflow, and would benefit from splitting detailed project templates into separate reference files while keeping the main skill as a concise overview.

Suggestions

Add explicit validation steps after each major action (e.g., 'Run `cargo check` to verify project compiles' after initialization)

Split detailed project templates (Binary, Library, Workspace, Web API) into separate reference files and link from the main skill

Remove the 'Use this skill when' and 'Do not use this skill when' sections as they add little value and Claude can infer applicability

Add a troubleshooting section or feedback loop for common scaffolding errors (e.g., dependency resolution failures)

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some unnecessary verbosity, such as the 'Use this skill when' and 'Do not use this skill when' sections that add little value. The code examples are well-structured but the overall document could be tightened.	2 / 3
Actionability	Provides fully executable code examples with complete Cargo.toml configurations, main.rs implementations, and CLI structures. All code is copy-paste ready with proper imports and realistic dependency versions.	3 / 3
Workflow Clarity	Steps are numbered and sequenced (1-7), but lacks explicit validation checkpoints. No verification steps after project creation (e.g., 'cargo check', 'cargo test' to verify setup). Missing feedback loops for error recovery.	2 / 3
Progressive Disclosure	Content is organized into clear sections by project type, but everything is inline in one monolithic document. The extensive code examples for 5 different project types could be split into separate reference files with the main skill providing an overview.	2 / 3
	Total	9 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning

	Total	13 / 16 Passed

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