CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/puppeteer-testing

Authors browser automation scripts using Puppeteer - Chrome / Chromium-only headless / headed automation, Page object via `page.*` API, network interception, PDF generation, screenshot capture, scraping. Distinct from Playwright (Puppeteer's older sibling, Chrome-only) - use Puppeteer for Chrome-only browser automation tasks (scraping, generating PDFs from HTML, screenshot pipelines) where Playwright's multi-browser support is unneeded overhead. Use when a project already depends on `puppeteer` / `puppeteer-core`, or when a Chrome-only script must emit PDFs, screenshots, or scraped data rather than assert on a page.

79

Quality

99%

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

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean and code-forward, with executable examples across the install-to-run spine, explicit verification checkpoints with error recovery, and a well-signaled one-level-deep reference holding the use-case recipes. Every token earns its place and navigation is clear.

DimensionReasoningScore

Conciseness

The body is code-forward and assumes Claude's competence, with no padding about what a browser/Puppeteer is; 'Verify:' blocks and short connector prose each earn their place.

3 / 3

Actionability

Provides fully executable, copy-paste-ready code (screenshot.js, Jest E2E, migration) plus concrete npm commands and page.pdf/page.screenshot/$$eval recipes in the reference file.

3 / 3

Workflow Clarity

A clear linear sequence (Install -> Basic automation -> E2E -> recipes -> Run -> Migration) with explicit 'Verify:' checkpoints and error-recovery guidance (e.g., 'Could not find Chromium' -> reinstall or set executablePath -> re-run).

3 / 3

Progressive Disclosure

SKILL.md is an overview with one clearly signaled, one-level-deep reference ([references/use-cases.md]); the reference file exists, is non-nested, and is organized by use case.

3 / 3

Total

12

/

12

Passed

Description

100%

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 is specific, trigger-rich, complete, and clearly distinct from the nearest competing skill (Playwright). It names concrete actions, gives explicit 'Use when' guidance, and scopes itself to Chrome-only automation to avoid mis-triggering.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('network interception, PDF generation, screenshot capture, scraping'), matching the score-3 anchor rather than the 'some actions' of score 2.

3 / 3

Completeness

Explicitly answers 'what' (browser automation via page.* API, PDF/screenshot/scraping) and 'when' via an explicit 'Use when...' clause naming dependency and output-trigger conditions.

3 / 3

Trigger Term Quality

Covers natural user phrasings ('scraping', 'generating PDFs from HTML', 'screenshot pipelines', 'scraped data'), giving good keyword coverage a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Explicitly disambiguates from Playwright ('Distinct from Playwright... use Puppeteer for Chrome-only... where Playwright's multi-browser support is unneeded overhead'), carving a clear non-conflicting niche.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents