domain-web
Use when building web services. Keywords: web server, HTTP, REST API, GraphQL, WebSocket, axum, actix, warp, rocket, tower, hyper, reqwest, middleware, router, handler, extractor, state management, authentication, authorization, JWT, session, cookie, CORS, rate limiting, web 开发, HTTP 服务, API 设计, 中间件, 路由
77
72%
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 ./skills/domain-web/SKILL.mdQuality
Discovery
72%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 trigger term coverage with comprehensive keywords spanning frameworks, protocols, and concepts in both English and Chinese. However, it reads more like a keyword dump than a proper skill description - it lacks concrete action verbs describing what the skill actually does. The 'Use when' clause is minimal and the capabilities are only implied through the keyword list.
Suggestions
Add concrete action descriptions before the keywords, e.g., 'Build HTTP servers, implement REST/GraphQL APIs, configure middleware, handle authentication and authorization in Rust web applications.'
Expand the 'Use when' clause to be more explicit, e.g., 'Use when building web services, creating API endpoints, setting up server routing, or implementing auth flows in Rust.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (web services) and lists frameworks/concepts (axum, actix, JWT, middleware, etc.) but doesn't describe concrete actions like 'create endpoints', 'handle requests', or 'implement authentication flows'. | 2 / 3 |
Completeness | Has a 'Use when' clause ('Use when building web services') but the 'what' is essentially just a keyword list rather than describing actual capabilities. The when is present but minimal, and the what is implied through keywords rather than explicitly stated. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural keywords users would say: 'web server', 'HTTP', 'REST API', 'GraphQL', 'WebSocket', plus specific framework names and Chinese equivalents. Covers both high-level concepts and specific technologies. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Rust web development with distinct framework names (axum, actix, warp, rocket, tower, hyper) that clearly distinguish it from general web development or other language-specific skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a well-structured reference document that efficiently maps web domain constraints to Rust patterns. Its strength is concise, tabular organization that respects token budget. However, it functions more as a quick-reference card than an actionable guide—it would benefit from additional executable examples and explicit workflows for common web development tasks.
Suggestions
Add 2-3 more executable code examples covering common patterns: middleware setup, state initialization with Arc, and request validation with typed extractors
Include a step-by-step workflow for setting up a basic Axum web server from scratch with validation checkpoints
Add concrete examples for the 'Common Mistakes' section showing both the problematic code and the fix
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for dense information delivery, no unnecessary explanations of concepts Claude would know. Every section adds value without padding. | 3 / 3 |
Actionability | Provides one concrete code example for Axum handlers with error handling, but most guidance is in table/reference format rather than executable examples. Missing concrete examples for middleware, state setup, or other patterns mentioned. | 2 / 3 |
Workflow Clarity | The 'Trace Down' section shows conceptual flow but lacks explicit step-by-step workflows for common tasks like setting up a web server, adding middleware, or implementing authentication. No validation checkpoints for multi-step processes. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections and tables. References to related skills (m07-concurrency, m02-resource, etc.) are clearly signaled in a dedicated section. Content is appropriately structured for an overview/reference document. | 3 / 3 |
Total | 10 / 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
- actionbook/rust-skills
- Commit
1f4becd
- 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.