storybook-startup-benchmark

Measure Storybook startup time from spawning `storybook dev` until the first story renders in the browser. Use when the user asks about Storybook boot time, server-ready timing, first story render timing, startup regressions, benchmarking with repeat runs, or comparing Storybook versions or feature flags.

Quality

81%

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

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

A well-structured, actionable benchmark skill with concrete flags and JSON shapes, but it provides structured-prose guidance rather than a complete executable script and lacks an explicit validation checkpoint inside the repeat-run batch loop.

Suggestions

Add an explicit per-run verification checkpoint in the `--repeat` workflow (e.g., "after each run, sanity-check `server.average`; if implausibly low, abort and check for a stale server") to lift the batch-operation workflow_clarity cap.

Provide a minimal complete Node benchmark script (or a reference file) so the harness steps are copy-paste executable rather than prose.

Trim the "Example Triggers" section since the same triggers are already covered by the frontmatter "Use when" clause, reducing token redundancy.

Dimension	Reasoning	Score
Conciseness	Lean and well-organized with no over-explanation of concepts Claude already knows (it does not explain what Storybook is); the "Example Triggers" section partially duplicates the frontmatter "Use when" clause and could be trimmed.	4 / 5
Actionability	Provides concrete flags (--no-open, --repeat), real API hooks (requestAnimationFrame, performance.mark), and exact JSON payload/summary shapes, but stops short of a complete copy-paste Node script, leaving the harness as structured prose steps.	4 / 5
Workflow Clarity	The harness sequence is clearly numbered and includes a pre-check ("Fail fast if the target Storybook port is already in use") and a stale-server diagnostic, but the batch `--repeat` loop has no explicit per-run validation/verification checkpoint, and the batch-operation cap therefore holds this at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is organized into clearly headed sections (Quick Start, Measurement Rules, Recommended Implementation, Pitfalls); at ~150 lines it is slightly beyond the simple-skill threshold and could not be trimmed further into separate files, so a couple of sections remain denser than ideal.	4 / 5
	Total	15 / 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.

A strong, third-person description that explicitly covers both what the skill does and when to use it, with concrete measurement boundaries and natural trigger phrases. Minor room to surface additional distinct actions, but well above the bar.

Dimension	Reasoning	Score
Specificity	Names a concrete measurement action with explicit boundaries ("from spawning `storybook dev` until the first story renders") and additional capabilities (repeat runs, version/flag comparison), but the core action is a single measurement operation rather than a broad set of distinct actions.	4 / 5
Completeness	Clearly states what it does (measure Storybook startup time from spawn to first story render) and explicitly answers when with concrete "Use when the user asks about..." trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases a user would actually say: "Storybook boot time", "server-ready timing", "first story render timing", "startup regressions", "benchmarking with repeat runs", "comparing Storybook versions or feature flags".	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Storybook startup benchmarking) with highly specific triggers; minimal risk of firing for unrelated skills.	5 / 5
	Total	19 / 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: storybookjs/storybook
Path: .agents/skills/storybook-startup-benchmark/SKILL.md
Commit: 8403f24

Reviewed: about 18 hours 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.