playwright-cli
Automate Browser Flows with Playwright CLI
Manual browser inspection makes reliable automation scripts difficult to author. This skill uses Playwright CLI to navigate pages, capture snapshots, and verify selectors.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "playwright-cli" from https://skillstore.io/skills/screenci-playwright-cli.md and its manifest at https://skillstore.io/api/skills/screenci-playwright-cli/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.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.
Test it
Using "playwright-cli". Inspect the Playwright documentation home page and identify the search control.
Expected outcome:
The page loaded successfully. The search control is available by role and accessible name, making it preferable to a generated element reference.
Using "playwright-cli". Compare the page before and after selecting the submit button.
Expected outcome:
The second snapshot shows a confirmation message and a disabled submit button. No navigation occurred.
Using "playwright-cli". Find the consent step needed before recording a ScreenCI flow.
Expected outcome:
A cookie banner appears after navigation. Use the clearly labeled accept button during hidden setup, then capture a new snapshot.
Security Audit
Medium RiskAll 37 static findings are false positives caused by Markdown code formatting, expected browser commands, benign example URLs, and a comment. One medium semantic risk remains: the fallback installation uses a mutable package version globally, increasing supply-chain and host impact.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (29)
🌐 Network access (7)
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.
Copy report link
https://skillstore.io/skills/screenci-playwright-cli/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/screenci-playwright-cli?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/screenci-playwright-cli?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/screenci-playwright-cli/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/screenci-playwright-cli.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
screenci. (2026). playwright-cli security audit report (audit version 3) [Author version unspecified]. Skillstore. https://skillstore.io/skills/screenci-playwright-cli/audits/3BibTeX citation
@techreport{screenci-screenci-playwright-cli-2026,
author = {screenci},
title = {playwright-cli security audit report (audit version 3)},
institution = {Skillstore},
year = {2026},
number = {3},
url = {https://skillstore.io/skills/screenci-playwright-cli/audits/3},
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-cli security audit report (audit version 3)"
version: "unspecified"
type: report
authors:
- name: "screenci"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/screenci-playwright-cli/audits/3"
identifiers:
- type: other
value: "skillstore:screenci-playwright-cli:audit:3"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
screenci-playwright-cli
2026-08-21
microsoft-playwright-cli
2026-08-21
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Verify a User Journey
Navigate a live flow, interact with controls, and capture page states before adding an automated test.
Discover Stable Selectors
Inspect roles, test identifiers, and attributes to select reliable targets for browser automation.
Prepare a ScreenCI Recording
Find consent actions and hidden setup steps before creating a repeatable ScreenCI visual script.
Try These Prompts
Open [URL], capture a snapshot, and summarize the page title, main controls, and visible consent banners. Do not submit forms.
Open [URL], find [control], activate it, and compare snapshots before and after. Report the resulting page change.
Inspect the flow from [start URL] to [goal]. Record each action, stable locator, page state, and required consent step.
Analyze [URL] for a ScreenCI script. Identify hidden setup actions, resilient selectors, dynamic content risks, and checkpoints for each visible step.
Best Practices
- Capture a new snapshot after navigation or any action that changes the page.
- Prefer roles, accessible names, and test identifiers over fragile CSS paths.
- Confirm the target domain and expected side effects before submitting forms.
Avoid
- Do not reuse stale element references after the page changes.
- Do not enter real credentials or sensitive data into demonstration flows.
- Do not install mutable global packages without explicit user approval.