bun-react-ssr
Use when building server-rendered React with Bun, including streaming SSR, hydration, renderToString, or custom SSR without a framework.
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/bun/skills/bun-react-ssr/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 excels at trigger term coverage and distinctiveness, clearly carving out a niche for Bun-based React SSR without a framework. However, it lacks explicit 'what does this do' content — it only states when to use it, not what concrete actions or outputs the skill provides. Adding specific capability statements would strengthen it significantly.
Suggestions
Add explicit capability statements before the 'Use when' clause, e.g., 'Sets up server-rendered React applications using Bun, configures streaming SSR pipelines, implements client hydration, and generates HTML with renderToString.'
Separate the 'what' from the 'when' more clearly — currently the description reads as only a trigger clause without describing concrete deliverables or actions the skill performs.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (server-rendered React with Bun) and some actions (streaming SSR, hydration, renderToString), but doesn't list comprehensive concrete actions like 'configure hydration entry points' or 'set up Bun SSR pipelines'. The terms listed are more techniques/concepts than specific actions the skill performs. | 2 / 3 |
Completeness | Has a 'Use when...' clause which addresses the 'when' question well, but the 'what does this do' part is weak — it describes when to use it but not what concrete outputs or actions the skill performs. The what and when are conflated into a single 'Use when' statement. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'server-rendered React', 'Bun', 'streaming SSR', 'hydration', 'renderToString', 'custom SSR without a framework'. These cover the main variations a developer would use when seeking help with this topic. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Bun' + 'SSR' + 'React' + 'without a framework' creates a very specific niche that is unlikely to conflict with general React skills, Next.js skills, or other runtime-specific skills. The scope is clearly delineated. | 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, actionable skill with excellent executable code examples covering the full spectrum of Bun React SSR patterns. Its main weakness is length—some sections (routing, CSS, dev setup) could be split into reference files to keep the main skill leaner. The workflow could benefit from explicit validation steps between build and serve phases.
Suggestions
Add explicit validation checkpoints between build and serve steps (e.g., verify the client bundle exists before starting the server, check for build errors)
Move secondary concerns like routing, CSS handling, and dev setup into separate reference files to reduce the main skill's token footprint
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some sections that could be trimmed or consolidated. The routing, CSS handling, and dev setup sections add bulk that may not be core to the SSR skill. Some code examples are longer than necessary, though they avoid explaining concepts Claude already knows. | 2 / 3 |
Actionability | Excellent actionability throughout - every section provides fully executable, copy-paste ready TypeScript/TSX code with complete file paths, specific Bun APIs, and concrete commands. The quick start, server entry, client entry, build scripts, and streaming examples are all immediately usable. | 3 / 3 |
Workflow Clarity | The basic workflow (init → install → create files → build → run) is implicitly clear but lacks explicit validation checkpoints. There's no verification step after building the client bundle, no check that hydration succeeded, and no error recovery flow for build failures. The build-then-serve sequence is present but could use explicit validation. | 2 / 3 |
Progressive Disclosure | Well-structured with a clear progression from Quick Start → Basic SSR → Streaming → Data Fetching → Advanced topics. References to external files (streaming-patterns.md, caching.md) are clearly signaled with specific trigger conditions at the end. Content is appropriately organized with headers for easy navigation. | 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.