bun-http-server
Use when building HTTP servers with Bun.serve, handling requests/responses, implementing routing, creating REST APIs, or configuring fetch handlers.
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/bun/skills/bun-http-server/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.
The description has strong trigger terms and clear distinctiveness due to the Bun.serve specificity, but it lacks a proper 'what this does' statement—it jumps straight into 'Use when' without first describing capabilities. Adding a leading sentence describing concrete actions would significantly improve it.
Suggestions
Add a leading capability statement before the 'Use when' clause, e.g., 'Creates and configures HTTP servers using Bun.serve, defines route handlers, sets up middleware, and manages request/response lifecycles.'
Expand the 'what' portion with more specific concrete actions like 'handle WebSocket upgrades, configure TLS, set response headers, parse request bodies' to better differentiate from a generic routing skill.
| 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 has a 'Use when' clause which addresses the 'when' aspect, but it lacks a clear 'what does this do' statement. It only specifies triggers without first describing the skill's capabilities. The 'what' and 'when' are conflated into a single 'Use when' clause rather than being distinct. | 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 developer would use when asking about building servers with Bun. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Bun.serve specifically for HTTP servers, which is a distinct niche. The mention of 'Bun.serve' and 'fetch handlers' distinguishes it from generic Node.js/Express server skills or other runtime-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 is a solid HTTP server reference skill with excellent actionability—every section has executable code examples covering the key use cases. The progressive disclosure is well done with clear section organization and appropriately signaled external references. The main weaknesses are minor verbosity (some examples could be tightened given Claude's knowledge of Web APIs) and the lack of explicit workflow/validation guidance for common development patterns.
Suggestions
Trim body parsing to show 2-3 key methods (json, formData, text) with a brief note that standard Request body methods are all supported, rather than listing all five.
Remove inline comments that explain things Claude already knows (e.g., '// GET, POST, etc.', '// ?id=123') to improve token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable examples, but some sections are slightly verbose—e.g., showing all five body parsing methods (json, formData, text, arrayBuffer, blob) when Claude already knows the Web API Request interface. The comments like '// GET, POST, etc.' and '// ?id=123' add minor clutter. | 2 / 3 |
Actionability | Every section provides fully executable, copy-paste ready TypeScript code. The examples cover the full range of HTTP server tasks—routing, body parsing, response types, CORS, error handling, static files, and server configuration—with concrete, runnable 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 development workflow (e.g., start server → test → iterate), and the common errors table, while useful, lacks explicit validation or verification steps. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers progressing from Quick Start to advanced topics. References to external files (tls-config.md, streaming.md) are clearly signaled with specific trigger conditions, and the main file stays at an appropriate overview level without deeply nesting references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%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
88da5ff
- 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.