bun-react-ssr
Use when building server-rendered React with Bun, including streaming SSR, hydration, renderToString, or custom SSR without a framework.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted description that clearly defines its niche at the intersection of Bun, React, and server-side rendering without a framework. It includes excellent trigger terms covering the main variations a developer would use and has an explicit 'Use when' clause. The only minor note is that the 'what' is somewhat embedded within the 'when' clause rather than stated separately, but the meaning is still very clear.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'streaming SSR', 'hydration', 'renderToString', 'custom SSR without a framework'. These are concrete, well-defined technical capabilities. | 3 / 3 |
Completeness | Starts with an explicit 'Use when' clause that clearly answers both what (building server-rendered React with Bun, streaming SSR, hydration, renderToString, custom SSR) and when (when building server-rendered React with Bun or doing any of the listed activities). | 3 / 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 asking about this topic. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Bun' runtime + 'SSR' + 'React' + 'without a framework' creates a very specific niche. It explicitly excludes framework-based SSR (like Next.js), reducing conflict risk with other skills. | 3 / 3 |
Total | 12 / 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 skill with complete executable examples covering the full spectrum of Bun React SSR patterns. Its main weaknesses are length (several sections cover patterns Claude already knows well, like basic routing and CSS handling) and lack of explicit validation checkpoints in the build/deploy workflow. The referenced files don't exist in the bundle, undermining the progressive disclosure structure.
Suggestions
Move the Router, CSS Handling, and Development Setup sections into separate reference files to reduce the main SKILL.md length and improve progressive disclosure.
Add explicit validation steps after the build step (e.g., 'Verify ./public/static/client.js exists before starting server') and after server startup (e.g., 'Test with: curl http://localhost:3000').
Trim sections that cover standard patterns Claude already knows (e.g., the full Router component implementation, basic CSS linking) to brief mentions with pointers to reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes sections that are somewhat verbose for Claude (e.g., the simple router implementation, CSS handling patterns, and dev setup are standard patterns Claude already knows). The common errors table and performance tips are efficient, but overall the file could be tightened significantly. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code throughout — from project initialization commands to complete server/client entry files, build scripts, streaming SSR setup, and data fetching with hydration. All code is concrete TypeScript/TSX, not pseudocode. | 3 / 3 |
Workflow Clarity | The steps for setting up a project are implicitly sequenced (init → install → create files → build → run), but there are no explicit validation checkpoints. For example, after building the client bundle, there's no verification step to confirm the build succeeded before starting the server. The common errors table partially compensates but doesn't constitute a feedback loop. | 2 / 3 |
Progressive Disclosure | The skill references `references/streaming-patterns.md` and `references/caching.md` at the bottom with clear loading conditions, which is good. However, no bundle files exist to back these references, and the main file itself is quite long (~300 lines) with sections like the full router implementation and CSS handling that could be split into separate reference files. | 2 / 3 |
Total | 9 / 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
5e92b71
- 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.