agentsclimarketplace
Sign in

Playwright automation

Skill majiayu000/spellbook/skills/playwright-automation

Browser automation and testing with Playwright. Use when testing web applications, automating browser tasks, taking screenshots, or validating UI behavior.From its SKILL.md

Install
npx -y skills add majiayu000/spellbook --skill playwright-automation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.3 KB, 216 tokens by cl100k_base, as published. Nobody here has run it

Playwright Browser Automation

Use this skill for Playwright scripts that inspect pages, capture screenshots, automate forms, test responsive views, or collect console/network evidence.

Routing

  • Start here to confirm scope, safety boundaries, and the minimum workflow.
  • Load references/full-guide.md before executing detailed commands, applying templates, or relying on examples from this skill.
  • Keep the work limited to the user-requested target; do not add adjacent improvements unless the user asks.

Quick Workflow

  1. Confirm the target, available context, constraints, and done-when signal.
  2. Read the relevant section of references/full-guide.md for task-specific details.
  3. Execute the smallest reversible action that satisfies the request.
  4. Verify with a runnable script, explicit target URL, captured output or artifact path, and cleanup of any started local servers.
  5. Report changed files, commands run, evidence collected, and any remaining risk.

References

  • references/full-guide.md - complete command patterns, examples, checklists, and edge cases.

What ships with it: 1 file

7.5 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most automation workflows skills give in 216 tokens

Counted across 813 of the 1,214 authors here whose files we hold, read 2026-09-06

  • Use conventional commit message formatin 38 of 813, across 34 files
  • Write tests before implementing codein 26 of 813, across 12 files
  • Achieve at least 80 percent test coveragein 24 of 813, across 11 files
  • Mock external dependencies for unit testsin 22 of 813, across 10 files
  • Read product marketing context before asking questionsin 21 of 813, across 6 files
  • Implement rollback plans for every deploymentin 21 of 813, across 9 files
  • Follow the arrange-act-assert patternin 20 of 813, across 9 files
  • Delete branches after mergingin 20 of 813, across 18 files
  • Test all edge cases and error scenariosin 20 of 813, across 8 files
  • Use semantic selectors for UI testsin 19 of 813, across 7 files
  • Define sequence type and audience contextin 18 of 813, across 5 files
  • Monitor feature drift and prediction distribution driftin 18 of 813, across 5 files

Said here and by no other author read

  • Confirm scope and safety boundaries
  • Load the full guide before executing commands
  • Limit work to the requested target
  • Execute the smallest reversible action
  • Verify with a runnable script
  • Cleanup started local servers

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.