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 设计, 中间件, 路由

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/domain-web/SKILL.md

Quality

Content

77%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 content is a tightly organized, token-efficient reference with executable Rust examples and strong cross-skill navigation, but it is structured as a design-constraint reference rather than a sequenced workflow with validation checkpoints, and it has no bundle files for deeper reference.

Suggestions

Add a short sequenced workflow for the most common web-service build task (e.g., define handler → add extractor → wire middleware → return IntoResponse) with an explicit validation/check step, to lift workflow clarity above 3.

Optionally move the Framework Comparison and Key Crates tables into a bundled reference file (e.g. references/frameworks.md) referenced one level deep, to strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense and lean: constraint tables, RULE/WHY/RUST blocks, and a single executable Rust example with no padding or explanation of concepts Claude already knows, matching the 5 anchor where every token earns its place.	5 / 5
Actionability	The Axum handler code block is concrete and executable, and tables map problems to specific fixes (spawn_blocking, Arc, IntoResponse), but most guidance is pattern-level rather than fully copy-paste-ready across common cases, sitting just below the 5 anchor.	4 / 5
Workflow Clarity	The skill frames design as constraint-to-implementation traces rather than a sequenced operational workflow, and it has no validation checkpoints; though it is a reference/design skill rather than a destructive batch operation, the absence of any explicit sequence caps it at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Critical Constraints, Framework Comparison, Key Crates, Design Patterns, Common Mistakes) with no nested references and appropriate use of a 'Related Skills' table for navigation, but it relies entirely on inline structure with no bundle files, leaving a minor gap versus the 5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

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

The description is trigger-rich and well-targeted with comprehensive keyword coverage and a clear Rust web-services niche, but its 'what' is conveyed as a keyword list rather than explicit concrete actions, leaving a minor gap versus the top completeness/specificity anchors.

Suggestions

Lead with a concise verb-phrase of concrete actions (e.g., 'Build and structure Rust web services: design handlers, extractors, middleware, and state') before the keyword list so the 'what' is explicit rather than implied.

Add a trailing clause mapping keywords to intent (e.g., 'Use when ... or when the user mentions any of these crates/concepts') to convert the keyword pile into clear trigger guidance.

Dimension	Reasoning	Score
Specificity	It names the domain ('building web services') and concrete action areas (state management, authentication, middleware, routing, extractors) but stops at the level of naming rather than enumerating distinct concrete actions, sitting between anchors 2 and 4.	3 / 5
Completeness	It explicitly provides 'when' ('Use when building web services') plus a 'what' via the keyword list, but the 'what' is an enumeration of keywords rather than a clearly stated set of concrete actions, so it falls just below the 5 anchor.	4 / 5
Trigger Term Quality	Comprehensive keyword coverage spanning natural English terms ('web server', 'HTTP', 'REST API', 'middleware'), specific crate names (axum, actix, warp, rocket, reqwest), and Chinese synonyms (web 开发, 中间件, 路由), matching the 5 anchor's coverage of natural terms and synonyms.	5 / 5
Distinctiveness Conflict Risk	The crate-specific triggers (axum, actix, warp, rocket, tower, hyper) carve out a distinct Rust web niche with minimal overlap risk against non-web or non-Rust skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: actionbook/rust-skills
Path: skills/domain-web/SKILL.md
Commit: 5c40d3a

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