CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bun-hot-reloading

Use when implementing hot reloading with Bun (--hot, --watch), HMR, or automatic code reloading during development. Covers watch mode, hot mode, and HTTP server reload.

63

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/bun/skills/bun-hot-reloading/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, highly actionable reference: the watch-vs-hot table, executable code for every pattern, and a Common Errors troubleshooting table give Claude everything needed for the common cases. The two significant weaknesses are broken references — the body points to two reference files that are absent from the bundle — and duplicated/overlapping code blocks that inflate the token cost without adding information.

Suggestions

Create the missing bundle files references/advanced-hmr.md and references/debugging.md, or remove the 'When to Load References' section — broken references are worse than none since Claude will attempt to read nonexistent paths.

Deduplicate the Hot Mode section (the repeated 'bun --hot run src/server.ts' block and the near-identical 'HTTP Server Hot Reload' vs 'Bun.serve with Hot Reload' examples), and consolidate watch-mode command examples that recur across three sections.

Promote the watch-vs-hot comparison table into a brief explicit decision rule (e.g., 'serving HTTP via Bun.serve with state to preserve → --hot; any other process or tests → --watch') so mode selection does not depend on inference from the table.

DimensionReasoningScore

Conciseness

The body is mostly executable code with minimal prose and no explanations of concepts Claude already knows — every section earns its place. It falls short of 5 due to duplication: 'bun --hot run src/server.ts' appears twice within the Hot Mode section, the watch commands recur across 'Watch Mode', 'package.json Scripts', and 'Testing with Watch', and 'HTTP Server Hot Reload' / 'Bun.serve with Hot Reload' substantially overlap.

4 / 5

Actionability

Nearly all guidance is copy-paste-ready: bash commands ('bun --watch run src/index.ts'), package.json scripts, complete TypeScript server examples, a full import.meta.hot API block, and a Common Errors table with concrete fixes ('await server.stop() before rebind'). Minor gaps keep it from 5 — the WebSocket live-reload example uses watch() and ServerWebSocket without imports, and the Express-like pattern's server.reload() usage is not validated against the surrounding example.

4 / 5

Workflow Clarity

The opening watch-vs-hot comparison table acts as a clear decision checkpoint (Behavior/State/Speed/Use case), followed by coherent sections for each mode, patterns, and a troubleshooting table mapping errors to causes and fixes — a reasonable error-recovery loop. Not a 5 because the mode-selection guidance is a table rather than an explicit decision procedure, and no validation steps exist for verifying a reload setup actually works.

4 / 5

Progressive Disclosure

The body is well-sectioned with clear headers and a 'When to Load References' section that clearly signals when to load advanced material — but both referenced files ('references/advanced-hmr.md', 'references/debugging.md') do not exist in the bundle, so the navigation promises are broken. This sits between anchor 3 (structure present, references problematic) and anchor 2; the strong in-body organization keeps it at 3 rather than dropping to 2.

3 / 5

Total

15

/

20

Passed

Description

78%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 description: explicit 'Use when' triggers, concrete Bun-specific flags, and good natural-keyword coverage including HMR and watch/hot mode terminology. The main gap is that the 'what' reads as a topic list ('Covers watch mode, hot mode, and HTTP server reload') rather than action-oriented capabilities, and a few natural synonyms (live reload, file watching) are absent.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — 'implementing hot reloading with Bun (--hot, --watch)', 'watch mode, hot mode, and HTTP server reload' — naming specific flags and modes rather than vague abstractions. It falls short of a 5 because the actions are topic labels ('Covers watch mode') rather than fully enumerated concrete actions, and it omits secondary capabilities present in the body (import.meta.hot API, WebSocket live reload).

4 / 5

Completeness

It has an explicit 'Use when' trigger clause plus a 'what' statement ('Covers watch mode, hot mode, and HTTP server reload'), so both what and when are present. Not a 5 because the 'what' is a topic coverage list rather than concrete action verbs, and the 'when' could be slightly more explicit about development-context triggers (it does say 'during development', which is good).

4 / 5

Trigger Term Quality

Natural trigger phrases include 'hot reloading', 'HMR', '--hot', '--watch', 'watch mode', 'hot mode', and 'automatic code reloading during development' — terms a developer would genuinely say. A few natural synonyms are missing (e.g., 'live reload', 'live reloading', 'restart on file change', 'file watching'), keeping it below a 5.

4 / 5

Distinctiveness Conflict Risk

'with Bun (--hot, --watch)' establishes a clear, well-scoped niche with tool-specific flags that no other skill would claim. The bare 'HMR' term carries minor overlap risk with frontend bundler HMR (Vite/webpack), but it is qualified by Bun throughout, so conflict risk is minimal — matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/bun/skills/bun-hot-reloading/SKILL.md

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.