agentleFS
Sign inStart free
JakkuSakuraJakkuSakura/skills/playright/SKILL.md

playright

Skill1 starsChanged 9 months agoMITView on GitHub

Use when validating web UI runtime behavior with browser automation, including JavaScript errors, console logs, and rendered DOM checks.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when a user asks to verify that a web UI actually works in a browser (not just build-time checks).

    line 8
  2. Distinctive:

    Prefer real browser runtime checks over static assumptions.

    line 11
  3. Distinctive:

    Verify HTTP status and basic route health.

    line 14
  4. Distinctive:

    No unhandled JS runtime errors.

    line 28
  5. Distinctive:

    No console error events (or errors are explicitly listed).

    line 29

≈ “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

Playright

Use this skill when a user asks to verify that a web UI actually works in a browser (not just build-time checks).

Core Rules

  • Prefer real browser runtime checks over static assumptions.
  • Capture pageerror and console error output before reporting success.
  • Assert key DOM elements after load.
  • Verify HTTP status and basic route health.
  • Report exact runtime failures and repro context.

Implementation Pattern

  1. Launch headless browser.
  2. Open target URL with timeout and networkidle.
  3. Collect pageerror and console error events.
  4. Assert critical UI selectors exist.
  5. Return a compact JSON-style result summary.

Verification Checklist

  • Page responds with HTTP 200.
  • Browser title is as expected.
  • Main UI landmarks are rendered.
  • No unhandled JS runtime errors.
  • No console error events (or errors are explicitly listed).

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