writing-dev-server-tests

Guides writing HMR/Dev Server tests in test/bake/. Use when creating or modifying dev server, hot reloading, or bundling tests.

Quality

86%

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

Quality

Content

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

A concise, highly actionable reference with complete executable examples and clear section structure. Workflow sequencing is shown through code with embedded assertions rather than explicit checkpoint narration.

Dimension	Reasoning	Score
Conciseness	The body is lean and reference-like: a one-line opener, terse file/category lists, and code examples, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Two complete, copy-paste-ready devTest examples plus a concrete Key APIs list and executable error-testing snippets cover the common cases with real code rather than pseudocode.	5 / 5
Workflow Clarity	The test-writing flow (setup files, fetch/patch, client assertions, expectReload) is sequenced clearly through examples with embedded validation (expect.toInclude, expectMessage), but explicit checkpoints or recovery guidance are implicit rather than stated.	4 / 5
Progressive Disclosure	The content is well-organized into clearly headed sections and is self-contained with no bundle files, though at ~90 lines some API detail could arguably live in a separate reference file.	4 / 5
	Total	18 / 20 Passed

Description

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

A strong, third-person description that clearly answers both 'what' and 'when' with concrete, natural trigger terms and a distinct niche. The only weakness is a somewhat narrow action set, which limits the specificity score.

Dimension	Reasoning	Score
Specificity	The description names the domain ('HMR/Dev Server tests') and a concrete action ('Guides writing ... tests') plus the target location ('test/bake/'), but the action set is limited to writing tests rather than a comprehensive list of capabilities.	3 / 5
Completeness	It explicitly states what it does ('Guides writing HMR/Dev Server tests in test/bake/.') and when to use it ('Use when creating or modifying dev server, hot reloading, or bundling tests.') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger terms 'dev server', 'hot reloading', and 'bundling tests' (plus 'HMR') are present and would be said by users, but a few common synonyms or variations are missing.	4 / 5
Distinctiveness Conflict Risk	The niche (HMR/Dev Server tests in a specific bake test directory) is narrow with distinct triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: oven-sh/bun
Path: .claude/skills/writing-dev-server-tests/SKILL.md
Commit: abe2ad4

Reviewed: 1 day 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.