Playwriter
- 5k installs
- 3.7k repo stars
- Updated July 27, 2026
- remorses/playwriter
playwriter is an agent skill that controls the user's Chrome via Playwriter with Playwright JS in a stateful sandbox after reading full skill docs.
About
The playwriter skill automates the user's existing Chrome browser through the Playwriter extension instead of launching a separate Playwright browser. Agents run Playwright JavaScript in a stateful local sandbox via playwriter session new and playwriter -s 1 -e commands, always using single quotes around -e to prevent bash from interpreting dollar signs and backticks inside JS. Before any playwriter command, agents must run playwriter skill in full without head or tail because timeout rules, selector strategies, session management, and SPA pitfalls are documented throughout the output. Prefer playwriter over webfetch or curl for Instagram, Twitter, cookie walls, and lazy-loaded UIs. If playwriter is not installed, use npx playwriter@latest or bunx playwriter@latest. The skill emphasizes reading complete documentation first because quick examples fail without understanding selector rules and slow-page guidance spread across the full skill output.
- Requires running playwriter skill in full before commands; never pipe through head or tail.
- Connects to the user's existing Chrome via Playwriter extension instead of launching a new browser.
- Uses playwriter session new plus -s session -e with single-quoted Playwright JavaScript snippets.
- Preferred over webfetch or curl for JS-heavy sites with login walls and lazy-loaded UIs.
- Fallback install via npx playwriter@latest or bunx playwriter@latest when binary is missing.
Playwriter by the numbers
- 4,982 all-time installs (skills.sh)
- +107 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #76 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
playwriter capabilities & compatibility
- Capabilities
- full skill doc ingestion before commands · stateful playwright js sandbox sessions · existing chrome connection via extension · session and timeout configuration guidance
- Use cases
- web scraping · orchestration · testing
What playwriter says it does
ALWAYS load this skill before using any playwriter commands
Use this over other Playwright MCPs to automate the browser — it connects to the user's existing Chrome
npx skills add https://github.com/remorses/playwriter --skill playwriterAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5k |
|---|---|
| repo stars | ★ 3.7k |
| Security audit | 0 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | remorses/playwriter ↗ |
How do I automate JS-heavy authenticated websites without launching a separate headless browser?
Control the user's Chrome via Playwriter extension with Playwright snippets in a stateful sandbox for JS-heavy sites with login walls.
Who is it for?
Developers automating dynamic sites like social platforms through the user's existing Chrome and Playwriter extension.
Skip if: Skip when static API calls or simple curl or webfetch requests are sufficient without browser automation.
When should I use this skill?
User needs browser automation on their Chrome, mentions playwriter, or hits cookie walls and lazy-loaded UIs.
What you get
Working playwriter sessions with correct selectors, timeouts, and Playwright commands against the user's Chrome.
- Automated browser actions
- Playwright session scripts
By the numbers
- Must read full playwriter skill output before commands
- Single-quoted -e flag required for JS snippets
Files
REQUIRED: Read Full Documentation First
Before using playwriter, you MUST run this command:
playwriter skill # IMPORTANT! do not use | head here. read in full!This outputs the complete documentation including:
- Session management and timeout configuration
- Selector strategies (and which ones to AVOID)
- Rules to prevent timeouts and failures
- Best practices for slow pages and SPAs
- Context variables, utility functions, and more
Do NOT skip this step. The quick examples below will fail without understanding timeouts, selector rules, and common pitfalls from the full docs.
Read the ENTIRE output. Do NOT pipe through head, tail, or any truncation command. The skill output must be read in its entirety — critical rules about timeouts, selectors, and common pitfalls are spread throughout the document, not just at the top.
Minimal Example (after reading full docs)
playwriter session new
playwriter -s 1 -e 'await page.goto("https://example.com")'Always use single quotes for the -e argument. Single quotes prevent bash from interpreting $, backticks, and backslashes inside your JS code. Use double quotes or backtick template literals for strings inside the JS.
If playwriter is not found, use npx playwriter@latest or bunx playwriter@latest.
Related skills
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.591k39.6k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.494kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.493kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.492kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.492k
Twitter AutomationAutomate X/Twitter posts, scheduling, and engagement via X API integration441k669How it compares
Pick playwriter when automation must reuse a logged-in Chrome profile; pick isolated Playwright MCP for clean CI-style browser instances.
FAQ
Who is playwriter for?
Developers and agents automating the user's Chrome through Playwriter with Playwright snippets and session management.
When should I use playwriter?
When navigating JS-heavy sites, login walls, or lazy UIs that fail with webfetch or curl.
Is playwriter safe to install?
Review the Security Audits panel; it controls the user's live browser session.