CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

streaming-html

Use when reviewing server-side rendering setup, Next.js App Router pages, or Node.js HTTP handlers to verify that HTML is streamed incrementally rather than buffered until completion.

Quality

81%

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

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.

The body is a well-structured overview with actionable, API-specific review and fix guidance and excellent progressive disclosure to a single reference file. Its main weakness is redundancy: a conceptual intro paragraph that re-explains known SSR behavior and duplicates content in the reference file.

Suggestions

Remove or drastically shorten the introductory paragraph explaining how traditional SSR blocks on data fetches — Claude already knows this, and the same text appears in references/rule.md's 'Why It Matters' section.

Drop the first Quick Reference bullet ('Streaming sends HTML in chunks...') since it restates the intro; keep the bullets that add concrete facts (default streaming with Suspense, boundary placement, the 600ms TTFB threshold).

Move the 'Monitor TTFB in Lighthouse — values above 600ms' threshold into the Check section so the detection criterion sits with the review steps, and add a one-line post-fix validation cue (e.g., re-check TTFB after refactoring) to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The opening paragraph explains how traditional SSR works ('waits for all data fetches to complete before sending a single byte of HTML... cannot parse, discover subresources, or render') — a concept Claude already knows — and is duplicated nearly verbatim in references/rule.md's 'Why It Matters' section, with the first Quick Reference bullet restating it a third time. The Check/Fix/Explain/Code Review sections themselves are tight, so this is 'some unnecessary explanation or could be tightened' rather than noticeably verbose.

3 / 5

Actionability

The guidance names exact APIs and signals to act on: 'renderToString calls, missing Suspense boundaries around data-fetching components, and use of await on slow queries', the fix ('renderToPipeableStream with Suspense boundaries', 'ReadableStream in a Node.js handler'), and a measurable threshold ('Monitor TTFB in Lighthouse — values above 600ms'). Anchor 4 fits because executable code lives only in the reference file and the body's own verification steps are thin.

4 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review structure gives the sequence, and the 600ms TTFB threshold provides a detection checkpoint. Not anchor 5 because an explicit validate-after-fix loop is absent from the body (the Verification section lives in the reference); not anchor 3 because a concrete measurable checkpoint is present.

4 / 5

Progressive Disclosure

The body is a concise, well-sectioned overview that delegates all implementation details, code examples, and verification to a single, clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), which exists and contains exactly that content. This matches anchor 5's clear overview with well-signaled references and appropriate content split.

5 / 5

Total

16

/

20

Passed

Description

83%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 trigger-style description that explicitly states both what the skill does (verify incremental HTML streaming vs buffering) and when to use it, across three concrete framework contexts. It is specific and distinct; only minor improvements (adding synonyms like 'SSR' or 'streaming') would push it to the top level.

DimensionReasoningScore

Specificity

The description names three concrete review targets ('server-side rendering setup, Next.js App Router pages, or Node.js HTTP handlers') and a precise verification criterion ('streamed incrementally rather than buffered until completion'). It is more concrete than anchor 3's domain-plus-1-2-actions example, but centers on one action type (verify/review) rather than the multiple distinct actions anchor 5 requires.

4 / 5

Completeness

Both parts are explicitly answered: what ('verify that HTML is streamed incrementally rather than buffered until completion') and when ('Use when reviewing server-side rendering setup, Next.js App Router pages, or Node.js HTTP handlers') with concrete trigger phrases. Not anchor 4, since the 'when' clause is already fully explicit and specific.

5 / 5

Trigger Term Quality

Natural phrases a developer would actually say are present: 'server-side rendering', 'Next.js App Router', 'Node.js HTTP handlers', 'streamed', 'buffered'. Common synonyms and abbreviations a user might use ('SSR', 'streaming', 'React', 'TTFB') are missing, which keeps it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche (verifying HTML streaming vs buffering in SSR contexts) is clear with framework-specific triggers. Minor overlap risk remains with generic SSR or Next.js performance skills, so anchor 5's 'minimal conflict risk' is not fully met.

4 / 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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/streaming-html/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.