agentleFS
Sign inStart free
rakaarwakyrakaarwaky/agents-arwaky/skills/devops/playwright-tooling/SKILL.md

playwright-tooling

Skill0 starsChanged 4 days agoMITView on GitHub

Recover Playwright browser cache on restricted hosts.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer the mirror path over raw CDN: when the CDN is reachable by curl but not by Playwright's Node fetch client.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Playwright Tooling

Playwright browser infrastructure: cache recovery, headless Chromium setup, and mirror routing for network-restricted hosts.

When to Use

  • playwright install times out or fails on GFW/corporate proxy/data-cap hosts.
  • curl reaches the CDN but Playwright's Node fetch cannot.
  • Browser dirs are wiped on each playwright install run.
  • headless-shell or FFmpeg is missing from ~/.cache/ms-playwright/.

Global Rules

  • Verify dir names before placing files. Dashes in browser names normalize to underscores on disk; placing in the dashed dir makes Playwright wipe it on every install.
  • Create both marker files after every manual placement. Without INSTALLATION_COMPLETE, Playwright re-downloads.
  • Prefer the mirror path over raw CDN when the CDN is reachable by curl but not by Playwright's Node fetch client.
  • Cache dir naming is the single source of truth for exact directory names — see the layout table in references/cache-layout.md.

Routing

StepReferencePurpose
Cache layout + recoveryreferences/cache-layout.mdDir names, marker files, CDN-unreachable recovery procedure.
Verificationreferences/verify.mdPost-placement checks: marker presence, install exit 0, headless launch.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free