browser_automation_playwright

Render JavaScript-driven web pages with Playwright/Chromium and return URL, title, and content.

9|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/flaz78/9Lives --skill browser-automation-playwright
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser_automation_playwright
Source: https://github.com/flaz78/9Lives/tree/main/workspace/skills/browser_automation_playwright
Command: npx skills add https://github.com/flaz78/9Lives --skill browser-automation-playwright

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves unreliable web automation caused by pages that depend on real JavaScript rendering, dynamic client-side content, and SPA-style navigation that can’t be captured by simple HTTP fetching.

Core Features & Use Cases

  • Real browser rendering: Navigate using a real Playwright/Chromium browser (with wait_until: networkidle and a DOM fallback).
  • Visual debugging support: Capture screenshots of the current page when requested.
  • ARM64 Docker readiness: Optimized for Linux ARM64 environments like Raspberry Pi, with explicit Chromium path and enablement variables.
  • Guardrails + fallback guidance: Detect Playwright ARM64 runtime failures and recommend switching to the fallback skill when Playwright is unavailable.

Quick Start

Use the browser_automation_playwright skill to open a JavaScript-heavy page and return the final URL, page title, and extracted content.

Frequently Asked Questions about browser_automation_playwright

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I render JavaScript with Playwright for web scraping dynamic SPAs?▼

You can render JavaScript by driving a real Playwright/Chromium browser that waits for `networkidle` and falls back to `domcontentloaded` on timeouts, returning the final URL, title, and extracted content.

Does Playwright browser automation work in ARM64 Docker environments?▼

Yes, this browser automation is optimized for Linux ARM64 Docker environments like Raspberry Pi, requiring `PLAYWRIGHT_ENABLED=true` and `PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH=/usr/bin/chromium` to run.

How do I capture screenshots during Chromium web scraping for debugging?▼

You can capture screenshots for debugging during Chromium web scraping by requesting visual debugging support, which takes a snapshot of the current page alongside returning the extracted content.

Why does my web scraper fail to extract content from client-side rendered pages?▼

Web scrapers fail on client-side rendered pages because simple HTTP fetching cannot execute JavaScript; this skill solves this by using a real Playwright browser to render and verify SPA-style navigation and content.

What should I do when Playwright fails to launch on ARM64?▼

When Playwright fails to launch on ARM64, the skill includes guardrails that detect the runtime failure and recommend switching to a fallback skill to continue your web automation tasks.