patchright-browser

Drive Patchright and Chrome for web reading, transcription, and browser state diagnostics.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/42atom/msgcode --skill patchright-browser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patchright-browser
Source: https://github.com/42atom/msgcode/tree/main/src/skills/runtime/patchright-browser
Command: npx skills add https://github.com/42atom/msgcode --skill patchright-browser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables real web access, long-form page transcription, and diagnosis of browser state by driving the Patchright browser CLI and inspecting Chrome root data within msgcode. It coordinates browser tasks, state verification, and CLI contracts to ensure reliable browser-driven automation in local agent workflows.

Core Features & Use Cases

  • Patchright browser as the primary web automation backbone for reading, scrolling, and interacting with web pages.
  • Long-form transcription and link preservation with controlled CLI visibility for debugging and reconciliation.
  • Diagnostics of root/instances/tabs, with clear guidance for status checks and recovery paths in case of failures.

Quick Start

Initiate the Patchright browser capability by launching the browser session and then use the provided CLI commands to inspect and manage Chrome roots, instances, and tabs.

Frequently Asked Questions about patchright-browser

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

FAQPage Schema
How do I read and transcribe long web pages using a real browser environment?

Web page reading and long-form transcription are handled by driving a Patchright browser CLI to control Chrome, enabling scrolling, link preservation, and structured content extraction from real web pages.

What is the best way to diagnose Chrome browser state across instances and tabs?

Browser state diagnostics are performed by inspecting Chrome root data and managing instances and tabs through the Patchright CLI, providing clear guidance for status checks and recovery paths in case of failures.

How do I inspect Chrome root data for web automation debugging?

You inspect Chrome root data by launching a Patchright browser session and using the provided CLI commands to enforce usage contracts and verify browser state across root, instances, and tabs.

Do I need real browser infrastructure to run Patchright CLI workflows?

Yes, real browser infrastructure is required; the skill enforces usage contracts and requires explicit guidance for root inspection and safe handling of IDs within a local agent workflow environment.

Why does my web automation workflow fail when checking browser state across tabs?

Failures during browser state checks often require recovery paths; this skill coordinates state verification and CLI contracts to diagnose root, instances, and tabs for reliable browser-driven automation.

Can I use Patchright for local agent web automation and page reading?

Patchright coordinates browser tasks and CLI contracts to ensure reliable browser-driven automation in local agent workflows, applying structured access for web reading and diagnostic workflows.