stream-builder

The framework-agnostic Stream builder (Steps 0-7 scaffold + enhance + Video audit), being extended to support app kinds beyond web. Use ONLY when the user explicitly names 'stream-builder' or '/stream-builder'. Web React / Next.js work - 'build me a chat app', 'scaffold', 'create a new ...', 'add Chat/Video/Feeds to this app', 'integrate Video', livestreaming, video conferencing, team messaging, direct messaging, social feed - defaults to the stream-react skill, not this one. Not auto-selected for generic web build requests.

1.60x

Quality

88%

Does it follow best practices?

Impact

66%

1.60x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

81%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 highly actionable, well-sequenced scaffold workflow with strong validation feedback loops and clear progressive disclosure to product reference files. Its main weaknesses are mild verbosity (the trust/integrity section and conceptual UX framing) and two referenced root-level files not verifiable in the provided bundle.

Suggestions

Trim or collapse the 'Install trust & integrity' publisher table, since the verbatim Trust readout already covers the user-facing summary; keep only the reviewer checklist.

Verify enhance.md and builder-ui.md exist at the skill root (or ship them in the bundle), since the body instructs the agent to load them in Steps 3-4.

Move the per-use-case Page Flow diagrams and Cross-Product Integration patterns into a references file, leaving SKILL.md as a routing overview with the hub-first principle and key rules inline.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational detail, but the 'Install trust & integrity' table and some Track F restatement could be tightened, and Page Flow edges toward explaining UX concepts Claude already knows.	3 / 5
Actionability	Copy-paste-ready commands throughout (npx shadcn@latest init, getstream env, npx tsc --noEmit, npx next build) with a product-to-package mapping table covering the common cases.	5 / 5
Workflow Clarity	Steps 0-7 are explicitly sequenced with a scaffold-order checklist, a Step 5 type-check-then-build validate->fix->retry feedback loop, and a Task B .gitignore safety check before writing secrets.	5 / 5
Progressive Disclosure	SKILL.md acts as an overview with well-signaled one-level-deep references (references/VIDEO.md, CROSS-PRODUCT.md, use-cases/_use-cases.yaml all present), but enhance.md and builder-ui.md are referenced yet absent from the bundle and some inline content could live in references.	4 / 5
	Total	17 / 20 Passed

Description

95%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 explicitly covers what the skill does and when to use it, with comprehensive natural trigger terms and explicit disambiguation against the related stream-react skill. It is somewhat verbose and the routing logic (listing triggers that default away from this skill) is mildly convoluted, but all required information is present and concrete.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('Steps 0-7 scaffold + enhance + Video audit') in the Stream domain, with minor gaps in coverage of what each phase entails.	4 / 5
Completeness	Explicitly answers both what ('framework-agnostic Stream builder (Steps 0-7 scaffold + enhance + Video audit)') and when ('Use ONLY when the user explicitly names stream-builder or /stream-builder') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users actually say — 'build me a chat app', 'scaffold', 'livestreaming', 'video conferencing', 'team messaging', 'direct messaging', 'social feed' — including synonyms.	5 / 5
Distinctiveness Conflict Risk	Carves a clear niche requiring explicit naming and actively manages overlap with the sibling skill ('defaults to the stream-react skill, not this one. Not auto-selected for generic web build requests').	5 / 5
	Total	19 / 20 Passed

Validation

75%

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 — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 2 missing, 1 deeper-than-1-level, 3 suspicious	Warning
referenced_paths_exist	Referenced path issues: 2 deeper-than-1-level	Warning

	Total	12 / 16 Passed

Repository: GetStream/agent-skills
Path: skills/stream-builder/SKILL.md
Commit: 1c67ee3

Reviewed: 3 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.