clarify skill docs should be read once per session, not before every command

The body wording previously said "REQUIRED" and "you MUST run this command"
which caused agents to re-read the ~1200 line skill output before every
single playwriter command in a session.

Updated wording to say "once per session" and "before the first playwriter
command in a session" so agents only load it once.

Fixes #97

Session: ses_0e7e6edf8ffe3nH709hIl20XEa
This commit is contained in:
Tommy D. Rossi
2026-06-30 12:43:40 +02:00
parent be17216cd9
commit 44c45b4453
+4 -4
View File
@@ -3,9 +3,9 @@ name: playwriter
description: Control the user own Chrome browser via Playwriter extension with Playwright code snippets in a stateful local js sandbox. Use this over other Playwright MCPs to automate the browser — it connects to the user's existing Chrome instead of launching a new one. Use this cli for navigating JS-heavy websites (Instagram, Twitter, cookie/login walls, lazy-loaded UIs) instead of webfetch/curl. ALWAYS load this skill before using any playwriter commands
---
## REQUIRED: Read Full Documentation First
## Read Full Documentation (once per session)
**Before using playwriter, you MUST run this command:**
**Before the first playwriter command in a session, run:**
```bash
playwriter skill # IMPORTANT! do not use | head here. read in full!
@@ -19,9 +19,9 @@ This outputs the complete documentation including:
- 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.
**Do NOT skip this step.** The examples below will fail without understanding timeouts, selector rules, and pitfalls from the full docs. You only need to do this once per session; subsequent playwriter commands in the same session do not require re-reading.
**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.
**Read the ENTIRE output.** Do NOT pipe through `head`, `tail`, or any truncation command. Critical rules are spread throughout the document, not just at the top.
## Minimal Example (after reading full docs)