bun-http-server

Use when building HTTP servers with Bun.serve, handling requests/responses, implementing routing, creating REST APIs, or configuring fetch handlers.

Quality

68%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/bun/skills/bun-http-server/SKILL.md

Quality

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.

The description effectively targets the right audience with strong trigger terms specific to Bun's HTTP server API, and it's clearly distinguishable from other skills. However, it reads entirely as a 'Use when' clause without first stating what the skill actually does (the 'what'), and the capabilities listed are more like topic areas than specific concrete actions.

Suggestions

Add an explicit 'what it does' statement before the 'Use when' clause, e.g., 'Guides building HTTP servers using Bun.serve, including route setup, middleware patterns, request parsing, and response construction.'

Make capabilities more concrete by listing specific actions like 'configure TLS, handle WebSocket upgrades, set CORS headers, parse request bodies, stream responses' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (HTTP servers with Bun.serve) and some actions (handling requests/responses, implementing routing, creating REST APIs, configuring fetch handlers), but these are somewhat general categories rather than deeply specific concrete actions like 'parse query parameters, set response headers, handle CORS'.	2 / 3
Completeness	The description is structured as a 'Use when...' clause, which addresses the 'when' clearly, but the 'what does this do' part is only implied through the trigger conditions rather than explicitly stated as capabilities. There's no separate statement of what the skill actually does or produces.	2 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'HTTP servers', 'Bun.serve', 'requests/responses', 'routing', 'REST APIs', 'fetch handlers'. These cover the main terms a user working with Bun's server API would naturally use.	3 / 3
Distinctiveness Conflict Risk	The description is clearly scoped to Bun.serve specifically, which distinguishes it from generic HTTP server skills (e.g., Node.js/Express) and from other Bun-related skills (e.g., file I/O, bundling). The mention of 'Bun.serve' and 'fetch handlers' creates a distinct niche.	3 / 3
	Total	10 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable reference skill with excellent executable code examples covering the breadth of Bun.serve functionality. Its main weaknesses are moderate verbosity (some sections could be condensed or moved to reference files) and the lack of workflow/validation guidance for setting up and testing a server. The referenced files for TLS and streaming are a good progressive disclosure pattern but aren't backed by actual bundle files.

Suggestions

Trim inline comments that explain things Claude already knows (e.g., '// GET, POST, etc.', '// ?id=123') to improve conciseness.

Move detailed sections like body parsing methods and server options into reference files, keeping only the most common patterns inline.

Add a brief workflow section showing how to verify the server is running correctly (e.g., a curl test or expected console output) to improve workflow clarity.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with executable code examples, but some sections are slightly verbose—e.g., showing all five body parsing methods inline, and the request handling section comments things Claude already knows (like 'GET, POST, etc.'). Could be tightened.	2 / 3
Actionability	Every section provides fully executable, copy-paste ready TypeScript code. The examples cover request handling, body parsing, response types, routing, error handling, CORS, static files, and server configuration with concrete, working code.	3 / 3
Workflow Clarity	The skill is primarily a reference/API guide rather than a multi-step workflow, so sequencing is less critical. However, there's no guidance on a recommended setup workflow, no validation steps (e.g., testing the server is running), and the common errors table is helpful but lacks a feedback loop for debugging.	2 / 3
Progressive Disclosure	The skill references `references/tls-config.md` and `references/streaming.md` with clear trigger conditions, which is good. However, no bundle files are provided, so these references are unverifiable. The main content is quite long (~200 lines of inline code) and some sections like body parsing or server options could be split into reference files.	2 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Commit: 5e92b71

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