Skills browser-automation
📦

browser-automation

Content revision r1 Medium Risk ⚙️ External commands

Automate Browser Testing and Scraping

Browser scripts often fail because selectors, waits, and browser state are fragile. This skill guides reliable Playwright and Puppeteer automation for tests, scraping, and agent workflows.

Supports: Claude Codex Code(CC)
📊 70 Adequate

Install with my Agent

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

Agent request
Review the Skillstore skill "browser-automation" from https://skillstore.io/skills/sickn33-browser-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-browser-automation/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.

Markdown detail GET /skills/sickn33-browser-automation.md Signed manifest GET /api/skills/sickn33-browser-automation/manifest Signed lockfile GET /api/skills/sickn33-browser-automation/lockfile

Test it

Using "browser-automation". A QA engineer asks why a login test fails only in continuous integration.

Expected outcome:

  • The response checks viewport differences, missing auto-waits, shared browser state, and selectors that depend on layout.
  • It recommends user-facing locators, fresh contexts, and trace capture for failed runs.

Using "browser-automation". A developer asks whether to use Puppeteer or Playwright for a new automation project.

Expected outcome:

  • The response compares browser support, locator reliability, waiting behavior, ecosystem needs, and Chrome-only constraints.
  • It recommends Playwright unless the project depends on Puppeteer-specific stealth tooling.

Using "browser-automation". A data team asks for a scraping workflow review before launch.

Expected outcome:

  • The response reviews rate limits, monitoring, retries, content stability, and authorization boundaries.
  • It warns that anti-detection techniques should only support approved testing or compliant data access.

Security Audit

Medium Risk
v4 • 7/5/2026 Open versioned report

The static shell execution finding is a false positive caused by Markdown inline code on the related skills line. The skill has no executable files, but its prose includes dual-use anti-detection and stealth guidance for scraping.

1
Files scanned
71
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
SKILL.md:3SKILL.md:61SKILL.md:65
Dual-Use Anti-Detection Guidance
The skill references anti-detection patterns, stealth plugins, and delays between requests. This can help authorized testing, but it can also support bypassing website anti-bot controls.
The file explicitly mentions anti-detection patterns and stealth plugins. The risk is dual-use because the context is browser scraping, not credential theft or malware.

Risk Factors

⚙️ External commands (1)
SKILL.md:70
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
Security Assessment

Copy report link

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

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-browser-automation.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). browser-automation security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-browser-automation/audits/4

BibTeX citation

@techreport{sickn33-sickn33-browser-automation-2026, author = {sickn33}, title = {browser-automation security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/sickn33-browser-automation/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: "browser-automation security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-05" url: "https://skillstore.io/skills/sickn33-browser-automation/audits/4" identifiers: - type: other value: "skillstore:sickn33-browser-automation: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

Highest Skillstore Score
sickn33 Recommended Current

sickn33-browser-automation

Skillstore Score 70
Evidence Confidence High
Skillstore usage 11
Updated

2026-08-21

EmilLindfors

emillindfors-browser-automation

Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 10
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Stabilize End-to-End Tests

Improve flaky Playwright or Puppeteer tests by using better locators, waits, and isolated browser state.

Plan Responsible Web Scraping

Review scraping workflows for reliability, rate limits, monitoring, and compliance boundaries before implementation.

Guide Browser-Based Agents

Design agent browser actions that use visible page behavior, predictable waits, and recoverable workflow steps.

Try These Prompts

Choose a Browser Framework 
I need browser automation for [testing or scraping]. Compare Playwright and Puppeteer for my use case, constraints, and team skills.
Fix a Flaky Browser Test 
Review this failing browser test behavior: [describe failure]. Identify likely selector, wait, state, and viewport problems.
Design Isolated Test Runs 
Design a Playwright test structure for [application]. Include browser context isolation, trace capture, locator strategy, and popup handling.
Review Automation Risk 
Review this browser automation plan for reliability and compliance risk: [describe plan]. Flag detection, rate limit, consent, and monitoring concerns.

Best Practices

  • Prefer user-facing locators that match what users can see.
  • Let Playwright auto-wait for readiness instead of adding fixed sleeps.
  • Run each test with isolated browser state and collect traces for failures.

Avoid

  • Do not rely on CSS or XPath selectors before accessible locators.
  • Do not share one browser context across unrelated tests.
  • Do not use stealth or delay tactics to bypass access controls.

Frequently Asked Questions

Does this skill install Playwright or Puppeteer?
No. It provides guidance only and does not install packages or run commands.
Can I use it with Claude, Codex, and Claude Code?
Yes. The report lists support for Claude, Codex, and Claude Code.
Is Playwright always better than Puppeteer?
No. The skill favors Playwright for most cases, but Puppeteer can fit Chrome-only projects.
Does it cover web scraping?
Yes. It covers scraping reliability, but users must follow site terms and applicable law.
Does it include test design patterns?
Yes. It covers test isolation, user-facing locators, and Playwright auto-wait behavior.
What is the main security concern?
The main concern is dual-use anti-detection guidance that could be misused outside authorized work.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/browser-automation

Ref

6425ec35f4ac137735cff58cd7877843bba23e3b

Maintenance freshness

7/18/2026

Usage

7 downloads · 117 views

File structure

📄 SKILL.md