1. Habit
  2. Skills
  3. Playwright Stealth Verify skill
liarjsdev · 98K installs

Playwright Stealth Verify skill
Runs by itself, PR changes test harness.

Automation harness stays coherent per PR.

Install the Playwright Stealth Verify skill and make it a habit: follow https://gethabit.dev/skills/liarjsdev/playwright-stealth-verify.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

98K installs4 starsMIT licenceSource on GitHub ↗

Playwright Stealth Verify

by liarjsdev · 98K installs

The skill

The playwright stealth verify skill checks whether a Playwright, Puppeteer, Selenium or CDP browser shows a coherent fingerprint, using liarjs checkPage on a Page you already have.

Only when you ask.

The habit

Automation harness stays coherent per PR.

↻ Runs by itselfPR changes test harness

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

PR changes test harness. Runs in GitHub Actions.

  • ↻ PR changes test harness
  • pull_request paths: playwright.config.*, harness launch code

02

It checks its work

checkPage assertions pass. If a check fails, it tells you.

  • ✓result.score is 85 or above
  • ✓no check has status bad
  • ✓liarjs is pinned as a dev dependency in the lockfile

03

It remembers

failing ids per PR. The next run reads it first: check ids that failed on recent pull requests.

loops/harness-coherence-test-loop/run-log.md

One run, step by step.
Then it stops.

Stop ruleOne test run per pull request, no retries.

  1. 01

    Pin liarjs

    Install it with npm install --save-dev liarjs so the version sits in the lockfile.

  2. 02

    Measure the page

    Call checkPage(page) on the harness's own Page with its real flags, plugins and proxy.

  3. 03

    Assert

    Expect the score at 85 or above and zero checks with status bad.

  4. 04

    Read the ids

    Map failures like webdriver, native-integrity, headless-ua and worker-consistency to their cause.

  5. 05

    Log and hand off

    Log the failing ids and send full reports to fingerprint-failure-triage.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Playwright Stealth Verify skill helps.

Use it when

  • ✓ You measure a stealth plugin's effect
  • ✓ A headless setup needs checking
  • ✓ You want fingerprint asserts in tests

Skip it when

  • – You need evasions, not measurements
  • – You do not drive a browser from code

Questions

Playwright Stealth Verify skill, answered.

Does liarjs change my browser?

No. The skill says it only measures and ships no evasions or profiles.

Can the suite stay inside my network?

Yes. Use --offline for JS-layer checks only, or --endpoint to point at your own deployment.

Why does my headless run score low?

The skill says a stock headless Chrome scores low and that this is the correct measurement.

How do I install the Playwright Stealth Verify skill?

Copy the prompt at the top into your agent. It installs the skill from liarjsdev/liarjs-skills and sets up the habit. Or run npx skills add liarjsdev/liarjs-skills --skill playwright-stealth-verify.

Is the Playwright Stealth Verify skill free?

Yes. It is published under MIT. Habit is free too.

Playwright Stealth Verify. Now as a habit.

Install the Playwright Stealth Verify skill and make it a habit: follow https://gethabit.dev/skills/liarjsdev/playwright-stealth-verify.md

  • Free
  • No account
  • Undo in one line

All liarjsdev skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by liarjsdev, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.