Skills playwright-skill

📦

playwright-skill

Name: playwright-skill
Author: sickn33

Content revision r1 Critical ⚙️ External commands🌐 Network access📁 Filesystem access🔑 Env variables⚡ Contains scripts

Automate Browser Testing with Playwright

Manual browser checks are slow and easy to miss. This skill creates focused Playwright automation for pages, forms, screenshots, and responsive checks.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Do not auto-install this skill.

The canonical policy requires operator review before any installation action.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "playwright-skill" from https://skillstore.io/skills/sickn33-playwright-skill.md and its manifest at https://skillstore.io/api/skills/sickn33-playwright-skill/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-playwright-skill.md Signed manifest GET /api/skills/sickn33-playwright-skill/manifest Signed lockfile GET /api/skills/sickn33-playwright-skill/lockfile

Test it

Using "playwright-skill". Check my localhost app visually.

Expected outcome:

Found one local server on port 3001.
Loaded the home page in a visible Chromium window.
Saved desktop and mobile screenshots and noted two layout issues.

Using "playwright-skill". Test whether login redirects to the dashboard.

Expected outcome:

The login form submitted successfully and redirected to the dashboard. The script reported no visible error messages.

Using "playwright-skill". Look for broken external links.

Expected outcome:

Collected external links from the page.
Reported working and failing links with their status codes.
Flagged links that timed out during the check.

Security Audit

Critical

v4 • 7/7/2026 Open versioned report

Most documentation backtick and example URL detections are false positives. Material risks remain in run.js, which executes generated JavaScript with Node privileges and can install dependencies automatically. Header injection and sandbox-disabled browser launch also need remediation before marketplace auto-install.

Files scanned

1,806

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (7)

Critical

SKILL.md:17-24 SKILL.md:41-42 run.js:52-71 run.js:121-147 run.js:205-209

Arbitrary Node.js Execution by Design

The skill tells the agent to write custom Playwright code and run it with run.js. run.js accepts file, inline, or stdin input, writes it to JavaScript, and loads it with require().

The documentation instructs generated script execution, and run.js implements file, inline, and stdin execution through require(). This directly grants generated code local Node.js privileges.

High

lib/helpers.js:16

Environment file access

const headerValue = process.env.PW_HEADER_VALUE;

This line reads PW_HEADER_VALUE, which can hold credentials or tokens. The value is later propagated into HTTP headers, so the sensitive-data risk is real.

High

lib/helpers.js:22

Environment file access

const headersJson = process.env.PW_EXTRA_HEADERS;

This line reads PW_EXTRA_HEADERS, which can include credential-bearing headers. The helper later applies those headers to browser contexts.

High

lib/helpers.js:366

Certificate/key files

...(Object.keys(mergedHeaders).length > 0 && { extraHTTPHeaders: mergedHeaders })

The spread merges environment-derived values into extraHTTPHeaders. This can propagate tokens to visited pages even though no certificate file is accessed.

High

lib/helpers.js:47

UID/GID manipulation

args: ['--no-sandbox', '--disable-setuid-sandbox']

Chromium is launched with --no-sandbox and --disable-setuid-sandbox by default. Disabling the browser sandbox increases impact from malicious or compromised pages.

High

SKILL.md:331-350 lib/helpers.js:14-27 lib/helpers.js:350-366

Unscoped Environment Header Propagation

The skill documents authentication tokens in custom headers and helper code applies environment-derived headers to browser contexts. A token for one target could be sent to another site.

The prose explicitly suggests authentication tokens, and the helper merges those environment values into extraHTTPHeaders. The code does not scope headers to a single origin.

Low

lib/helpers.js:392

System reconnaissance

hostname: 'localhost',

The helper probes localhost ports to discover running services. The behavior is limited to common dev ports, but it is still local service reconnaissance.

Capability review items (20)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Critical

run.js:209

Dynamic require with variable

require(tempFile);

run.js writes user or model supplied JavaScript to a temp file and loads it with require(). That executes arbitrary local Node.js code.

High

run.js:15

Node.js child_process module

const { execSync } = require('child_process');

run.js imports child_process and uses execSync during dependency setup. This is real process execution from the skill runtime.

High

run.js:38

Synchronous process execution

execSync('npm install', { stdio: 'inherit', cwd: __dirname });

run.js automatically runs npm install when Playwright is missing. That executes an external package-manager command from the skill runtime.

High

run.js:39

Synchronous process execution

execSync('npx playwright install chromium', { stdio: 'inherit', cwd: __dirname });

run.js automatically runs npx playwright install chromium when Playwright is missing. That executes an external command and can fetch browser dependencies.

Medium

lib/helpers.js:15

Environment variable access (dot notation)

const headerName = process.env.PW_HEADER_NAME;

The helper reads environment variables for custom HTTP header configuration. Those headers can influence requests made by browser contexts.

Medium

lib/helpers.js:16

Environment variable access (dot notation)

const headerValue = process.env.PW_HEADER_VALUE;

PW_HEADER_VALUE can contain authentication material and is later used as an HTTP header value. That makes this real secret-bearing environment access.

Medium

lib/helpers.js:22

Environment variable access (dot notation)

const headersJson = process.env.PW_EXTRA_HEADERS;

PW_EXTRA_HEADERS can contain multiple header values and is parsed from the environment. Those values are later applied to browser requests.

Medium

lib/helpers.js:15

Environment variable object

const headerName = process.env.PW_HEADER_NAME;

The helper reads environment variables for custom HTTP header configuration. Those headers can influence requests made by browser contexts.

Medium

lib/helpers.js:16

Environment variable object

const headerValue = process.env.PW_HEADER_VALUE;

PW_HEADER_VALUE can contain authentication material and is later used as an HTTP header value. That makes this real secret-bearing environment access.

Medium

lib/helpers.js:22

Environment variable object

const headersJson = process.env.PW_EXTRA_HEADERS;

PW_EXTRA_HEADERS can contain multiple header values and is parsed from the environment. Those values are later applied to browser requests.

Medium

run.js:59

Node.js fs operations

return fs.readFileSync(filePath, 'utf8');

run.js reads a caller-provided file path as JavaScript for later execution. That is real filesystem access tied to the arbitrary-code executor.

Medium

run.js:71

Node.js fs operations

return fs.readFileSync(0, 'utf8');

run.js reads JavaScript from standard input for later execution. That is real filesystem-style input access tied to the arbitrary-code executor.

Medium

run.js:205

Node.js fs operations

fs.writeFileSync(tempFile, code, 'utf8');

run.js writes generated JavaScript to a temp file inside the skill directory before executing it. This is real local file creation of executable code.

Medium

run.js:59

Synchronous file operations

return fs.readFileSync(filePath, 'utf8');

run.js synchronously reads a caller-provided script before execution. The synchronous API is secondary, but the filesystem access is real.

Medium

run.js:71

Synchronous file operations

return fs.readFileSync(0, 'utf8');

run.js synchronously reads code from standard input before execution. The read feeds the arbitrary-code execution path.

Medium

run.js:205

Synchronous file operations

fs.writeFileSync(tempFile, code, 'utf8');

run.js synchronously writes generated code to a JavaScript file that it then executes. This confirms filesystem write risk.

Low

lib/helpers.js:391

HTTP/HTTPS request

const req = http.request({

detectDevServers sends HEAD requests to localhost on common development ports. This is intentional local probing, but it is real network behavior.

Low

lib/helpers.js:391

HTTP client library

const req = http.request({

detectDevServers uses Node http.request to probe local ports. The target is localhost only, so the confirmed risk is limited.

Low

lib/helpers.js:399

Hardcoded URL

detectedServers.push(`http://localhost:${port}`);

The helper constructs localhost URLs for detected services. This is not external exfiltration, but it is real local network discovery output.

Low

run.js:56

Node.js fs stat operations

if (args.length > 0 && fs.existsSync(args[0])) {

run.js accepts a caller-provided file path and checks whether it exists before execution. This is a real filesystem touch, though the risk is limited.

Risk Factors

⚙️ External commands (90)

API_REFERENCE.md:502-503 API_REFERENCE.md:530-538 API_REFERENCE.md:602-603 lib/helpers.js:54 lib/helpers.js:134 lib/helpers.js:137 lib/helpers.js:187 lib/helpers.js:195 lib/helpers.js:271 lib/helpers.js:334 lib/helpers.js:399 lib/helpers.js:400 run.js:15 run.js:38 run.js:39 run.js:58 run.js:121-156 run.js:161-173 run.js:201 SKILL.md:7 SKILL.md:11 SKILL.md:12 SKILL.md:13 SKILL.md:23-25 SKILL.md:25-31 SKILL.md:31-33 SKILL.md:33-41 SKILL.md:41-42 SKILL.md:42-48 SKILL.md:48-51 SKILL.md:51-59 SKILL.md:59-61 SKILL.md:61-65 SKILL.md:65-84 SKILL.md:84-88 SKILL.md:88-90 SKILL.md:90-96 SKILL.md:96-118 SKILL.md:118-122 SKILL.md:122-132 SKILL.md:132-144 SKILL.md:144-148 SKILL.md:148-158 SKILL.md:158-171 SKILL.md:171-175 SKILL.md:175-201 SKILL.md:201-202 SKILL.md:202-206 SKILL.md:206-210 SKILL.md:210-235 SKILL.md:235-239 SKILL.md:239-257 SKILL.md:257-269 SKILL.md:269-277 SKILL.md:277-283 SKILL.md:283-293 SKILL.md:293-302 SKILL.md:302-304 SKILL.md:304-325 SKILL.md:325-327 SKILL.md:327-341 SKILL.md:341-344 SKILL.md:344-348 SKILL.md:348-351 SKILL.md:351-355 SKILL.md:355-357 SKILL.md:357-361 SKILL.md:361-363 SKILL.md:363-365 SKILL.md:365-369 SKILL.md:369-386 SKILL.md:386-387 SKILL.md:387 SKILL.md:388-389 SKILL.md:389-390 SKILL.md:390-391 SKILL.md:391-392 SKILL.md:392-393 SKILL.md:393 SKILL.md:395-401 SKILL.md:401-403 SKILL.md:403-406 SKILL.md:406-409 SKILL.md:409-412 SKILL.md:412-416 SKILL.md:416-427 SKILL.md:427-429 SKILL.md:429-444 SKILL.md:444-451 SKILL.md:451-452

🌐 Network access (21)

📁 Filesystem access (43)

🔑 Env variables (18)

API_REFERENCE.md:53 API_REFERENCE.md:54 API_REFERENCE.md:55 API_REFERENCE.md:72 API_REFERENCE.md:53 API_REFERENCE.md:54 API_REFERENCE.md:55 API_REFERENCE.md:72 lib/helpers.js:15 lib/helpers.js:16 lib/helpers.js:22 lib/helpers.js:45 lib/helpers.js:46 lib/helpers.js:15 lib/helpers.js:16 lib/helpers.js:22 lib/helpers.js:45 lib/helpers.js:46

⚡ Contains scripts (3)

lib/helpers.js:174 run.js:110 run.js:209

Detected Patterns

UID/GID manipulationSystem reconnaissance

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-playwright-skill/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-playwright-skill/security.svg)](https://skillstore.io/skills/sickn33-playwright-skill?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-playwright-skill?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-playwright-skill/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-playwright-skill.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). playwright-skill security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-playwright-skill/audits/4

BibTeX citation

@techreport{sickn33-sickn33-playwright-skill-2026,
  author = {sickn33},
  title = {playwright-skill security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/sickn33-playwright-skill/audits/4},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "playwright-skill security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-playwright-skill/audits/4"
identifiers:
  - type: other
    value: "skillstore:sickn33-playwright-skill:audit:4"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

sickn33 Recommended Current

sickn33-playwright-skill

Skillstore Score 38

Evidence Confidence Medium

Skillstore usage 26

Updated

2026-08-21

lackeyjb

lackeyjb-playwright-skill

Skillstore Score 38

Evidence Confidence Medium

Skillstore usage 17

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Check a Local Web App

Detect a running dev server, open the app, capture screenshots, and report visible layout issues.

Validate User Workflows

Exercise login, form submission, navigation, and redirect flows with focused Playwright automation.

Inspect Responsive Behavior

Compare desktop, tablet, and mobile views and summarize visible regressions from saved screenshots.

Try These Prompts

Test a Local Page

Find my running dev server and test the home page in a visible browser. Capture a screenshot and report visible layout issues.

Validate a Form Flow

Use Playwright to fill the contact form, submit it, and report validation messages and success states. Ask before using real credentials.

Compare Responsive Views

Run a responsive check across desktop, tablet, and mobile widths. Save screenshots and summarize layout regressions with file paths.

Build a Focused Script

Create a Playwright script for [workflow] against [URL]. Keep the URL configurable and explain external requests before running it.

Best Practices

Review generated scripts before execution when credentials, uploads, or external domains are involved.
Use localhost or staging targets unless the user explicitly approves production testing.
Keep URLs and secrets configurable and scoped to the tested origin.

Avoid

Do not run generated automation against unknown external sites without user approval.
Do not place long-lived credentials in broad PW_EXTRA_HEADERS values.
Do not treat visual screenshots as proof that business logic is correct.