skills.rest
mikker
mikkerCOMMUNITY
Explore all skills by this author →
Website𝕏@mikkerGitHub

playwriter

Automate the user's existing Chrome session with Playwright code snippets.

102|4|Updated Apr 15, 2009
Search Tags:#javascript#playwright#chrome#web-testing#browser-automation#playwriter
One-click install
npx skills add https://github.com/mikker/dotfiles --skill playwriter-mikker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwriter
Source: https://github.com/mikker/dotfiles/tree/main/agents.symlink/skills/playwriter
Command: npx skills add https://github.com/mikker/dotfiles --skill playwriter-mikker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables automated control of the user's own Chrome browser via the Playwriter extension, using Playwright code snippets executed in a stateful local JavaScript sandbox. It is designed to automate JS-heavy websites by connecting to an existing Chrome session instead of launching a fresh browser instance.

Core Features & Use Cases

  • Connects to the user's existing Chrome browser instance to run Playwright scripts.
  • Provides a stateful local JavaScript sandbox for deterministic Playwright code.
  • Uses the Playwriter CLI to orchestrate browser automation tasks.
  • Ideal for JS-heavy sites (Instagram, Twitter, cookie/login walls, lazy-loaded UIs) where traditional fetch/curl-based approaches fall short.

Quick Start

Run the playwriter skill command to read the complete up to date skill and instructions.

Frequently Asked Questions about playwriter

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

FAQPage Schema
How do I automate Chrome browser tasks on websites with login walls?▼

Browser automation for login-walled sites is achieved by connecting Playwright scripts to your existing Chrome session, bypassing authentication blocks by operating within your active browser context.

Can I run Playwright scripts against my existing Chrome session instead of a fresh instance?▼

Yes, running Playwright scripts against an existing Chrome session is supported by using the Playwriter extension and CLI to execute code directly in your active browser environment.

How do I automate JavaScript-heavy websites like Instagram or Twitter with Playwright?▼

Automating JS-heavy sites with Playwright is handled through a stateful local JavaScript sandbox that interacts with lazy-loaded UIs and dynamic content via your connected Chrome browser.

Does this approach to browser automation work with traditional fetch or curl requests?▼

No, traditional fetch or curl-based approaches fall short for these JS-heavy targets, requiring a connected Chrome browser instance and Playwright code snippets for proper rendering and interaction.

Do I need a specific extension to control Chrome with Playwright code snippets?▼

Yes, you need the Playwriter extension and Playwright-capable tooling installed to orchestrate the browser automation tasks and maintain the local JavaScript sandbox.

What are the limitations of automating JS-heavy sites with an existing Chrome session?▼

This approach is limited to deterministic tasks within the local JavaScript sandbox, meaning non-deterministic browser actions or complex stateful flows outside the sandbox scope are not supported.

Related Skills

Explore More Software Engineering Skills→
mikeyobrienmikeyobrien
3.1k

playwriter

Run Playwright scripts against a persistent Chrome session for UI testing.

Community
Advanced
imehrimehr
1

Amplifier Learner Tools

Log AI executions and learn from feedback using JSONL logs and JSON recommendations.

Community
Intermediate
ShahfarzaneShahfarzane

browser-automation

Automate Chrome browser interactions via natural-language commands and Playwright.

Community
Advanced
MuduiClawMuduiClaw
11

webapp-testing

Automate local web app testing via Playwright and Chrome CDP instances.

Community
Intermediate