Conciseness

Every line is an executable command or a repo-specific fact Claude cannot know (ports, iframe.html URL format, install script name, the CI caveat "bun install in CI does not download Chrome"). No concept explanations or padding; matches the lean 5 anchor.

Actionability

Copy-paste ready commands throughout: "bunx agent-browser open <url>", "curl -s localhost:6006/index.json lists the ids", "bunx agent-browser diff screenshot --baseline baseline.png", plus concrete setup commands. Covers the common cases; matches the 5 anchor.

Workflow Clarity

A clear numbered sequence from setup through visual diff with some checkpoints ("An unnamed control is a bug; fix the name rather than clicking by CSS", "Browser-console warnings in a page or story are bugs"). Between 4 and 5: validation rules are stated but there is no explicit step or command for reading browser-console output, leaving a minor validation gap.

Progressive Disclosure

Under 50 lines with well-organized sections (Set up, Steps) and no inlined content that belongs in a separate file; the full command guide is deferred one level deep via a clearly signaled link ("Load the agent-browser skill for the full command guide"). Fits the simple-skill 5 anchor.

Specificity

"check a web page or Storybook story in a real browser", "taking screenshots, comparing against a baseline, testing a viewport or dark mode", and "serving a production build over HTTPS" are multiple concrete, comprehensive actions in neutral how-to voice. Not 4: coverage of the domain's actions is comprehensive with no material gaps.

Completeness

Explicitly answers both: what ("How to check a web page or Storybook story in a real browser... using only agent-browser") and when ("Use when verifying UI changes, looking at a page or component, taking screenshots, comparing against a baseline, testing a viewport or dark mode, or serving a production build over HTTPS"). Matches the 5 anchor with a concrete 'Use when' trigger list; not 4 since the when-clause is fully explicit rather than vague.

Trigger Term Quality

Natural phrases like "verifying UI changes", "taking screenshots", "page or component", "dark mode", "viewport", and "baseline" are present, but a few natural terms users would say (e.g. "visual regression", "test in a browser", "inspect the UI") are missing. Fits the 4 anchor (good coverage, a few natural terms missing) rather than 5's comprehensive synonym coverage.

Distinctiveness Conflict Risk

Clear niche (repo browser verification with agent-browser, Storybook stories, HTTPS prd builds) with "using only agent-browser" explicitly disambiguating from Playwright/Puppeteer-style skills. Minimal conflict risk; fits the 5 anchor rather than 4's minor overlap risk.