CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

playwright-cli

Automate browser interactions, test web pages and work with Playwright tests.

60

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/playwright-cli/SKILL.md

The canonical home for this skill is playwright-cli in microsoft/playwright-cli

SKILL.md
Quality
Evals
Security

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 content is a lean, command-first reference with excellent progressive disclosure into nine real one-level-deep bundle files and fully executable examples throughout. The only notable gaps are a minor duplication between the inline Storage section and its reference file, and the absence of explicit outcome-verification steps in the example workflows.

DimensionReasoningScore

Conciseness

The body is almost entirely executable commands with terse, purposeful comments — it assumes Claude's competence and wastes no tokens on background concepts. Not 5: the Storage section enumerates every cookie/localStorage/sessionStorage command inline while references/storage-state.md covers the same ground, a minor duplication that could be trimmed.

4 / 5

Actionability

Every section consists of copy-paste-ready commands ("playwright-cli fill e5 \"user@example.com\" --submit", "playwright-cli tab-new https://example.com/page") plus worked examples (form submission, multi-tab workflow, DevTools debugging) covering the common cases. Fully executable with no pseudocode.

5 / 5

Workflow Clarity

The Quick start and examples establish a clear sequence (open → snapshot → interact → snapshot → close), with snapshots serving as implicit checkpoints before and after actions. Not 5: there is no explicit verification of outcomes (e.g., confirming a form actually submitted or a navigation succeeded) before closing the session.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview: core CLI usage stays inline, and a well-labeled "Specific tasks" section points to nine one-level-deep reference files (all verified to exist on disk: playwright-tests.md, request-mocking.md, running-code.md, session-management.md, storage-state.md, test-generation.md, tracing.md, video-recording.md, element-attributes.md). Navigation is easy and the split is appropriate.

5 / 5

Total

18

/

20

Passed

Description

53%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 states a clear, niche-specific 'what' in third person with a concrete tool name, but it omits any 'when to use' trigger guidance, which both caps completeness and weakens trigger-term coverage. Common natural phrasings users would say (browser automation, scraping, e2e tests, screenshots) are absent.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to automate a browser, drive/click through a web page, scrape or verify web content, or run, debug, and fix Playwright tests."

Broaden natural trigger terms to include likely user phrasings such as "browser automation", "e2e/end-to-end tests", "scrape a page", "fill out a form", and "take a screenshot".

Mention 1-2 more concrete capabilities (snapshots, network mocking, multi-tab/session management) to lift specificity beyond two generic actions.

DimensionReasoningScore

Specificity

"Automate browser interactions, test web pages" names the domain with 1-2 concrete actions, but coverage is not comprehensive (no snapshots, screenshots, network mocking, or storage capabilities). Fits anchor 3 ("names domain and 1-2 concrete actions") rather than 4, which requires several specific actions with only minor gaps.

3 / 5

Completeness

The 'what' is clear (automate, test web pages, work with Playwright tests), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. This is exactly anchor 3 (clear 'what', 'when' missing), not 4, since the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant keywords are present ("browser", "Playwright", "tests", "web pages"), but the natural phrases users would actually say — "browser automation", "scraping", "end-to-end/e2e tests", "take a screenshot" — are missing. Matches anchor 3 (some relevant keywords, missing common variations) rather than 4, since the most likely user phrasings are absent.

3 / 5

Distinctiveness Conflict Risk

Mentioning "Playwright tests" carves out a clear niche that is unlikely to trigger for unrelated skills. Slightly below anchor 5 because the bare phrase "Automate browser interactions" could overlap with other browser-automation or scraping skills, leaving minor overlap risk.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

coleam00/Archon

Path

.claude/skills/playwright-cli/SKILL.md

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.