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

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 concise and well-structured, with concrete API references and a clear pointer to a single reference file for code examples. The main weakness is the absence of any inline executable code and a missing explicit validate-retry feedback loop in the Check/Fix workflow.

Suggestions

Add one small inline code snippet (e.g. a renderToPipeableStream onShellReady skeleton or a Suspense boundary) so the body is actionable without requiring the reference file.

Add an explicit verification step after 'Fix' (e.g. 'Re-run Lighthouse and confirm TTFB < 600ms and HTML chunks arrive before the response completes') to close the Check -> Fix -> Verify loop.

Tighten the Quick Reference so it does not restate the opening paragraph's points, removing minor redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean (~30 lines), assumes Claude's competence, explains no basic concepts, and every section (Quick Reference, Check, Fix, Explain, Code Review) earns its place with minimal redundancy.	5 / 5
Actionability	Names specific, actionable APIs and a measurable threshold (renderToPipeableStream, Suspense, ReadableStream, renderToString, TTFB > 600ms), but the body itself contains no executable code — all examples are offloaded to the reference file.	4 / 5
Workflow Clarity	The Check -> Fix sequence is clear with a measurable checkpoint (Lighthouse TTFB), but there is no explicit validate-and-retry feedback loop tying measurement back to the fix step.	4 / 5
Progressive Disclosure	A clean, well-sectioned overview that signals a single one-level-deep reference (references/rule.md, verified to exist) for full implementation details, making navigation easy.	5 / 5
	Total	18 / 20 Passed

Description

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

The description is well-crafted with an explicit 'Use when' trigger, concrete framework-specific targets, and a clear statement of what it verifies. It is concise and distinct, with only minor gaps in synonym/metric-term coverage.

Dimension	Reasoning	Score
Specificity	Names several concrete targets (SSR setup, Next.js App Router pages, Node.js HTTP handlers) and a concrete verification action, but the action set is largely a single review/verify verb family rather than multiple distinct actions.	4 / 5
Completeness	Explicitly answers both what (verify HTML is streamed incrementally rather than buffered) and when via a concrete 'Use when...' clause with multiple trigger scenarios.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('server-side rendering', 'Next.js App Router', 'Node.js HTTP handlers', 'buffered') that users would say, though common synonyms like SSR, streaming, TTFB, and FCP are missing.	4 / 5
Distinctiveness Conflict Risk	A clear, narrow niche (HTML streaming in SSR/Next.js/Node handlers) with distinctive triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/streaming-html/SKILL.md
Commit: 30756a7

Reviewed: 22 days ago

Table of Contents

Discovery Implementation Validation

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.