Skip to content
Skillv1.0.0

playwright

Automate real browsers from the terminal.

by OpenKnots(0) 0 installs
Free
Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from OpenKnots/okcode (packages/shared/src/skills-catalog/recommended/playwright/SKILL.md). Install upstream with npx skills add OpenKnots/okcode --skill playwright. Copyright stays with the author.

Playwright Skill

When to use this skill

  • Use when the task needs browser automation, UI verification, end-to-end testing, or scripted web interactions.
  • Use when the user needs reproducible validation of browser behavior rather than manual spot-checking.
  • Use when screenshots, DOM assertions, navigation flows, or form automation are part of the task.
  • Use when the user wants a reliable browser-based regression check from the terminal.

What this skill does

  • Designs Playwright workflows that are deterministic, inspectable, and resilient to minor UI changes.
  • Prefers stable selectors and event-driven waits over brittle timing assumptions.
  • Captures actionable failure context such as URLs, selectors, screenshots, and expectation mismatches.
  • Keeps test intent focused on behavior, not incidental implementation details.

Implementation

  • Clarify whether the goal is one-off browser automation, a reusable test, or a debugging workflow.
  • Prefer semantic selectors and stable locators over deep CSS selectors tied to styling structure.
  • Use assertions that reflect user-observable behavior rather than implementation accidents.
  • Prefer waits based on navigation, visible UI state, or network/DOM readiness rather than arbitrary sleep intervals.
  • If the task is exploratory, keep scripts short and focused on reproducing the target behavior.
  • If the task is test authoring, structure steps and assertions so failures are easy to diagnose.
  • Capture enough context on failure for a human to reproduce and fix the issue quickly.

Best practices

  • Avoid timing-based waits unless no stronger signal exists.
  • Keep selectors robust and understandable.
  • Prefer behavior-level assertions over snapshotting everything.
  • Include screenshots or other evidence when reporting a browser failure.
  • Keep scripts and tests maintainable; do not overfit to current DOM noise.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/openknots-okcode-playwright/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

openknots-okcode-playwright.ocm.jsonjson
{
  "ocm": "1",
  "id": "openknots-okcode-playwright",
  "kind": "skill",
  "name": "playwright",
  "description": "Automate real browsers from the terminal.",
  "publisher": "OpenKnots",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "browser",
      "testing",
      "automation",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Automate real browsers from the terminal."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/OpenKnots/okcode",
      "path": "packages/shared/src/skills-catalog/recommended/playwright/SKILL.md",
      "ref": "3ab6345d68cb1e4cf2d9d068d4f6cc5f1ee34121",
      "url": "https://github.com/OpenKnots/okcode/blob/3ab6345d68cb1e4cf2d9d068d4f6cc5f1ee34121/packages/shared/src/skills-catalog/recommended/playwright/SKILL.md",
      "key": "OpenKnots/okcode/packages/shared/src/skills-catalog/recommended/playwright/SKILL.md"
    }
  },
  "instructions": "# Playwright Skill\n\n## When to use this skill\n\n- Use when the task needs browser automation, UI verification, end-to-end testing, or scripted web interactions.\n- Use when the user needs reproducible validation of browser behavior rather than manual spot-checking.\n- Use when screenshots, DOM assertions, navigation flows, or form automation are part of the task.\n- Use when the user wants a reliable browser-based regression check from the terminal.\n\n## What this skill does\n\n- Designs Playwright workflows that are deterministic, inspectable, and resilient to minor UI changes.\n- Prefers stable sele",
  "cost": {
    "context_tokens": 474
  }
}

Fetch it by URL: GET /api/v1/registry/openknots-okcode-playwright/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.