CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

playwright-cli

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

4.42x
Quality

91%

Does it follow best practices?

Impact

84%

4.42x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary skill body: lean, fully executable command documentation with worked examples and clean offloading of specialized tasks to real one-level-deep reference files. The only gap is that workflows rely on implicit snapshot checkpoints rather than explicit validation/error-recovery steps.

DimensionReasoningScore

Conciseness

The body is almost entirely executable command listings with terse, load-bearing comments (e.g., '# take a screenshot (rarely used, as snapshot is more common)'), with no explanation of concepts Claude already knows and no padding. Every section earns its place, matching the lean-and-efficient top anchor.

5 / 5

Actionability

Everything is copy-paste-ready: a quick start, a comprehensive categorized command reference with real arguments, and worked examples (form submission, multi-tab workflow, DevTools debugging) that cover the common cases. Fully executable, matching the top anchor.

5 / 5

Workflow Clarity

Sequences are clear (open -> goto -> interact -> snapshot -> close) and examples include implicit checkpoints via snapshots after actions, but verification is not explicitly labeled as validation and no error-recovery guidance is given. This fits anchor 4 (clear sequence, most checkpoints, minor validation gaps) rather than 5's explicit validation steps and feedback loops.

4 / 5

Progressive Disclosure

A clear overview (quick start, categorized commands) plus a 'Specific tasks' section linking seven well-signaled, one-level-deep reference files, all verified to exist with real content. No content that belongs in references is inlined; navigation is easy, matching the top anchor.

5 / 5

Total

19

/

20

Passed

Description

87%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: third-person voice, explicit what-and-when structure with concrete trigger phrases, and a clearly distinct browser-automation niche. The only room for improvement is adding a few natural synonyms (e.g., 'web scraping') and mentioning more of the tool's capabilities.

DimensionReasoningScore

Specificity

The description names the domain ('browser interactions') and several concrete actions ('web testing, form filling, screenshots, and data extraction'), matching the anchor for several specific actions with minor gaps. It falls short of a 5 because capabilities like request mocking, tracing, or storage-state handling are not reflected, keeping coverage from comprehensive.

4 / 5

Completeness

It explicitly answers both what ('Automates browser interactions for web testing, form filling, screenshots, and data extraction') and when ('Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages') with concrete trigger phrases, directly matching the top anchor. Not lower: the 'Use when' clause is present and enumerates specific triggers.

5 / 5

Trigger Term Quality

Natural user phrases are well covered: 'navigate websites', 'interact with web pages', 'fill forms', 'take screenshots', 'test web applications', 'extract information from web pages'. A few natural synonyms are missing (e.g., 'scrape'/'web scraping', 'browser automation'), placing it noticeably above the midpoint between anchor 3 and anchor 5.

4 / 5

Distinctiveness Conflict Risk

It has a clear niche (browser automation) with browser-centric triggers repeated in both the what and when clauses, so conflict risk with unrelated skills is minimal. 'Web testing' and 'data extraction' carry slight overlap with testing/scraping skills, but the browser framing dominates, matching the top anchor better than anchor 4.

5 / 5

Total

18

/

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

drufball/nightshift

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.