rocket-project-starter
Scaffold a production-ready Rocket 0.5+ API with Rust 2024 edition, request guards, fairings, managed state, responders, database integration, and typed configuration.
79
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backend-rust/rocket-project-starter/SKILL.mdQuality
Discovery
50%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 excels at specificity and distinctiveness by naming the exact framework version, language edition, and Rocket-specific concepts. However, it critically lacks any 'Use when...' guidance, making it difficult for Claude to know when to select this skill. The trigger terms are somewhat technical and could benefit from more natural user language.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when building a Rust web API, creating a Rocket project, or when the user mentions Rocket framework, Rust backend, or web server in Rust.'
Include more natural user terms alongside technical ones, such as 'web server', 'REST API', 'backend service', or 'Rust web framework'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Scaffold a production-ready Rocket 0.5+ API' with detailed components including 'request guards, fairings, managed state, responders, database integration, and typed configuration.' | 3 / 3 |
Completeness | Describes WHAT the skill does well, but completely lacks a 'Use when...' clause or any explicit trigger guidance for WHEN Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and this has no implicit triggers either. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Rocket', 'Rust', 'API', 'database integration', but these are somewhat technical. Missing common user phrases like 'web server', 'REST API', 'backend', or file extensions like '.rs'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Rocket 0.5+ framework with Rust 2024 edition. The combination of framework version, language edition, and specific Rocket concepts (fairings, request guards) makes it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, production-ready skill that provides comprehensive, executable guidance for scaffolding Rocket APIs. The code examples are complete and follow Rust/Rocket idioms correctly. The main weakness is the monolithic structure - while well-organized internally, the extensive code examples could benefit from being split into referenced files for easier navigation and reduced cognitive load.
Suggestions
Consider splitting detailed code examples (full CRUD handlers, fairings) into separate referenced files like HANDLERS.md and FAIRINGS.md, keeping SKILL.md as a concise overview with quick-start patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining basic concepts Claude already knows. Every section serves a purpose with executable code examples and no padding. | 3 / 3 |
Actionability | Fully executable code throughout - complete cargo commands, working Rust code examples, proper project structure, and copy-paste ready patterns for all major components (routes, guards, fairings, error handling). | 3 / 3 |
Workflow Clarity | Clear sequential steps in 'First Steps After Scaffold' section with explicit ordering. The scaffold command sequence is logical, and common commands are well-organized for different development phases. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but this is a monolithic file with ~400 lines of code. Some content (like the full CRUD handlers or fairing implementations) could be split into referenced files for better navigation. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
90%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
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.