CtrlK
BlogDocsLog inGet started
Tessl Logo

browser-smoke-review

Use browser automation to review docs pages, preview URLs, rendered output, or web-facing fallow surfaces. Use when the user wants a screenshot-based review, browser smoke test, docs site check, or preview deployment inspection.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 concise, well-structured simple skill body with a clear workflow and good organization. The main gap is actionability: it names the tool family but gives no concrete executable commands or examples.

Suggestions

Add one concrete example invocation (e.g. a Playwright snippet or command) for the common case to lift actionability.

Specify how to surface console/network failures (e.g. capture browser console logs) so the checking step is executable.

DimensionReasoningScore

Conciseness

Lean and efficient with no concept over-explanation; every line ('Use Playwright/browser tooling for web-facing checks', the Good fits list, the numbered workflow) earns its place and assumes Claude's competence.

5 / 5

Actionability

Steps are concrete and ordered (open URL, inspect structure, capture screenshots, check console errors, report issues with page/path context) but lack specific executable commands or tool invocations beyond the generic 'Playwright/browser tooling' mention.

3 / 5

Workflow Clarity

Clear five-step sequence with a checking step (console errors/network failures); minor validation gaps remain, though this non-destructive review skill does not trigger the destructive/batch feedback-loop cap.

4 / 5

Progressive Disclosure

Well under 50 lines with no need for external references and cleanly organized into 'Good fits' and 'Workflow' sections, satisfying the simple-skill exception for a top score.

5 / 5

Total

17

/

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 description that clearly states capabilities and explicit 'Use when...' triggers with natural keywords. Minor room to expand synonyms and sharpen distinctiveness from adjacent review skills.

Suggestions

Add natural synonyms/extensions (e.g. 'preview URLs', 'staging deploy') to broaden trigger coverage.

Sharpen distinctiveness by contrasting scope with panel-review (e.g. 'smoke/correctness only, not product judgment').

DimensionReasoningScore

Specificity

Names the domain ('browser automation') and several concrete review targets ('docs pages, preview URLs, rendered output, or web-facing fallow surfaces'), listing multiple specific actions with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (use browser automation to review web-facing surfaces) and 'when' (Use when the user wants...) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('screenshot-based review, browser smoke test, docs site check, or preview deployment inspection') with good coverage, though a few synonyms/extensions are absent.

4 / 5

Distinctiveness Conflict Risk

Clear browser-based review niche with distinct triggers, but minor overlap risk with related review skills (e.g. panel-review, docs-review).

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fallow-rs/fallow
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.