Skip to content
TrustedSkillsbeta
Back to all skills

Playwright Visual Testing

Checked
manutej·vlatest·testing

Helps with Playwright, testing as part of testing, debugging, and quality assurance workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add manutej/luxor-claude-marketplace --skill playwright-visual-testing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

manutej

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned manutej/luxor-claude-marketplace at 1861cc9720.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1861cc9720
Manifest
plugins/luxor-specialized-tools/skills/playwright-visual-testing/SKILL.md
Scanned
5 files, 5,516 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to perform automated visual regression testing on web applications using Playwright. It captures screenshots of rendered pages and compares them against baseline images to detect unintended visual changes in the UI.

When to use it

  • Validating that recent code deployments did not break the layout or styling of critical user flows.
  • Detecting subtle CSS regressions, such as misaligned buttons or broken grids, that unit tests might miss.
  • Ensuring consistency across different browsers and screen sizes by comparing visual outputs side-by-side.
  • Automating QA workflows where manual screenshot comparison is time-consuming or error-prone.

Key capabilities

  • Executes Playwright browser automation to render web pages.
  • Captures high-fidelity screenshots of specific elements or full page views.
  • Compares current images against stored baseline references.
  • Generates detailed reports highlighting pixel-level differences between versions.

Example prompts

  • "Run a visual regression test on the checkout flow and compare the results against the last known good build."
  • "Capture screenshots of the login page on Chrome, Firefox, and Safari, then check for any visual discrepancies."
  • "Identify which specific UI elements changed visually after the latest commit to the CSS stylesheet."

Tips & gotchas

Visual testing requires a stable baseline; ensure you have a verified 'golden image' before running comparisons to avoid false positives. This skill is best suited for detecting layout shifts or color changes, not for verifying functional logic like form validation states.