CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bun-react-ssr

Use when building server-rendered React with Bun, including streaming SSR, hydration, renderToString, or custom SSR without a framework.

64

Quality

80%

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-react-ssr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable content with complete, executable examples and a logical progression from basic SSR to production builds. The main defects are the two dangling references to nonexistent files and the large amount of advanced content inlined in SKILL.md that should be split out.

Suggestions

Create references/streaming-patterns.md and references/caching.md (or remove the 'When to Load References' section) — the body currently points to files that do not exist.

Move the advanced sections (Streaming SSR with Suspense, Hot Reload Development, Production Build) into the reference files, keeping SKILL.md as a concise quick-start overview to cut the ~400-line body.

Add a lightweight verification step after the client build (e.g. check that public/static/client.js exists before starting the server) to give the workflow an explicit checkpoint.

DimensionReasoningScore

Conciseness

Nearly all executable code with no padding explaining React/Bun basics Claude already knows. Not 5 because the server entry is shown twice with overlap, and placeholder comments like '// This would be a data fetching component' could be trimmed.

4 / 5

Actionability

Complete copy-paste-ready code for server, client, app, build, dev, and production, plus run commands ('bun run build.ts', 'bun run src/server.tsx') covering the common cases end-to-end.

5 / 5

Workflow Clarity

Sections sequence logically (init → build client → start server → streaming → production build). Not 5 because no verification checkpoints exist (e.g. nothing confirms the client bundle was emitted before serving); no destructive/batch ops, so the 3-cap doesn't apply.

4 / 5

Progressive Disclosure

The 'When to Load References' section clearly signals references, but both referenced files ('references/streaming-patterns.md', 'references/caching.md') do not exist, and ~400 lines of advanced material (streaming/Suspense, dev hot-reload, prod build) are inlined that belong in those reference files. Not 2 because sections are well organized and references are explicitly signaled, not buried.

3 / 5

Total

16

/

20

Passed

Description

75%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 with an explicit 'Use when' trigger, a clearly bounded niche, and several concrete capability keywords. Its main weakness is that the 'what' is never stated separately from the 'when', and a few natural synonyms (e.g. 'server-side rendering') are absent.

DimensionReasoningScore

Specificity

Lists several concrete actions ('streaming SSR, hydration, renderToString, or custom SSR'), but coverage has minor gaps (routing, CSS, static file serving are unmentioned). Not 5 because it isn't comprehensive; not 3 because it names more than 1-2 actions.

4 / 5

Completeness

Explicit 'Use when building...' trigger with capabilities embedded ('streaming SSR, hydration, renderToString, or custom SSR'). Not 5 because the 'what' has no standalone capability statement — it lives entirely inside the when-clause.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'server-rendered', 'SSR', 'streaming', 'hydration', 'renderToString', 'React', 'Bun'. Not 5 because common synonyms like 'server-side rendering' or 'isomorphic' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche of Bun + React + 'custom SSR without a framework', but trigger terms like 'React SSR' would also plausibly fire for framework-specific skills (Next.js, Vite SSR), giving minor overlap risk.

4 / 5

Total

16

/

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-react-ssr/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.