Scaffold a production-ready Actix-web 4.x API with Rust 2024 edition, async handlers, extractors, middleware, SQLx for database access, and structured error handling.
85
80%
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/actix-project-starter/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at specificity and distinctiveness by naming exact technologies and versions (Actix-web 4.x, Rust 2024 edition, SQLx). However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select this skill, and could benefit from more natural user-facing keywords beyond technical jargon.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user wants to create a Rust web API, build an Actix backend, or scaffold a new Rust web service'
Include more natural language variations users might say: 'Rust web server', 'REST API in Rust', 'Actix project', 'backend API'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'Scaffold a production-ready Actix-web 4.x API' with 'async handlers, extractors, middleware, SQLx for database access, and structured error handling' - these are all concrete, specific capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (scaffold Actix-web API with specific features), but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Contains good technical keywords like 'Actix-web', 'Rust', 'SQLx', 'async handlers', 'middleware' that users familiar with the stack would use, but missing common variations like 'web server', 'REST API', 'backend', or file extensions like '.rs'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (Actix-web 4.x, Rust 2024 edition, SQLx) that creates a clear niche unlikely to conflict with other web framework or language skills. | 3 / 3 |
Total | 10 / 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 an Actix-web API. The code examples are complete and immediately usable, with clear conventions and patterns. The main weakness is the monolithic structure - at this length, splitting detailed implementations (middleware, full CRUD handlers) into separate reference files would improve navigation.
Suggestions
Consider splitting detailed code examples (middleware implementation, full CRUD handlers) into separate reference files like MIDDLEWARE.md and HANDLERS.md, keeping SKILL.md as a concise overview with links
Add a brief 'See Also' section at the end pointing to potential companion files for advanced topics like testing setup, Docker configuration, or WebSocket implementation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is dense with executable code and avoids explaining basic concepts Claude already knows. Every section provides actionable content without padding or unnecessary explanations about what Actix-web or Rust are. | 3 / 3 |
Actionability | Fully executable code throughout with complete, copy-paste ready examples for main.rs, routes, models, error handling, middleware, and migrations. Commands are specific and immediately usable. | 3 / 3 |
Workflow Clarity | Clear sequenced steps in 'First Steps After Scaffold' section with numbered workflow. The scaffold command section provides ordered dependency installation, and common commands are well-organized for different development phases. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but it's a monolithic document with no references to external files. For a skill of this length (~350 lines), some content like the full middleware implementation or integration notes could be split into separate reference files. | 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 | |
181fcbc
Table of Contents
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.