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

Install with Tessl CLI

npx tessl i github:actionbook/rust-skills --skill domain-web

What are skills?

Review — 72%

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

Validation for skill structure

SKILL.md

Review

Evals

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, concepts, and multilingual terms, making it highly discoverable. However, it reads more like a keyword dump than a proper skill description - it lacks concrete action verbs explaining what the skill actually does (e.g., 'creates REST endpoints', 'implements authentication flows'). The 'Use when' clause is present but minimal.

Suggestions

Add concrete action descriptions before the keywords, e.g., 'Creates REST APIs and web servers, implements authentication/authorization, configures middleware and routing for Rust web applications.'

Expand the 'Use when' clause to be more specific, e.g., 'Use when building HTTP servers, REST APIs, or WebSocket services in Rust, or when configuring web middleware, authentication, or CORS.'

Dimension	Reasoning	Score
Specificity	Names the domain (web services) and lists frameworks/concepts (axum, actix, JWT, CORS, etc.), but doesn't describe concrete actions like 'create endpoints', 'implement authentication', or 'configure middleware'. It's more of a keyword list than action descriptions.	2 / 3
Completeness	Has a 'Use when' clause ('Use when building web services') but the 'what' is weak - it only lists keywords rather than explaining what the skill actually does. The trigger guidance exists but the capability description is essentially absent.	2 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'web server', 'HTTP', 'REST API', 'GraphQL', 'WebSocket', plus specific framework names (axum, actix, rocket) and common concepts (JWT, CORS, rate limiting). Also includes Chinese translations for international users.	3 / 3
Distinctiveness Conflict Risk	Clearly focused on Rust web development with specific framework names (axum, actix, warp, rocket, tower, hyper). The Rust-specific frameworks make it highly distinguishable from generic web development 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 is a well-structured domain reference skill that excels at conciseness and organization, using tables effectively to convey dense information. However, it functions more as a reference card than an actionable guide—it tells Claude what patterns exist but provides limited executable examples beyond the single Axum handler. The skill would benefit from more concrete code snippets for common workflows.

Suggestions

Add executable code examples for at least one more common task (e.g., middleware setup, shared state initialization, or basic server bootstrap)

Include a 'Quick Start' section with a minimal working web server example that can be copy-pasted

Add explicit step-by-step workflow for a common task like 'Adding authentication middleware' with validation checkpoints

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 frameworks 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 a domain overview skill.	3 / 3
	Total	10 / 12 Passed

Validation

75%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow	Warning

	Total	12 / 16 Passed

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