← Search

Clerk E2E testing with Playwright and Cypress
Developer tools 🧪 Install ran in our test sandbox · Nov 18, 2026 📌 Pinned version: commit a02dbd2
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a Clerk app plus Playwright or Cypress set up…

Clerk E2E testing with Playwright and Cypress

Test Clerk auth flows end to end — clerkSetup, testing tokens, storageState, bot-detection bypass, best practices

At a glance
What
Test Clerk auth flows end to end — clerkSetup, testing tokens, storageState, bot-detection bypass, best practices
Cost
Free
Needs
a Clerk app plus Playwright or Cypress set up; Clerk development keys (pk_test_*/sk_test_* — free, auto-generable with `clerk init`); never use production keys in tests; no license declared in the source repo — read it yourself before reusing its content
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Clerk testing is a free short pointer to the official guide for end-to-end testing of Clerk apps. It covers the mental model of test auth as isolated session state, clerkSetup and setupClerkTestingToken to bypass bot detection, reusing auth state with storageState for speed, and the Playwright globalSetup versus Cypress command differences, with best practices.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit a02dbd2

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Clerk app plus Playwright or Cypress set up; Clerk development keys (pk_test_*/sk_test_* — free, auto-generable with `clerk init`); never use production keys in tests; no license declared in the source repo — read it yourself before reusing its content Install "Clerk E2E testing with Playwright and Cypress" for me. Fetch the SKILL.md and its reference files from the source repository into a temporary folder, review them for anything suspicious, and report in two or three sentences what the guide covers (test auth mental model, clerkSetup/testing tokens, storageState reuse, framework specifics) so I can follow it in my own project. Do not copy the guide's content into my project — this is a reference lookup only. Repository: https://raw.githubusercontent.com/clerk/skills/a02dbd2a933b8929525129a6cb9dcf6ed66d0adf/skills/clerk-testing/SKILL.md Pinned version: install the code at commit a02dbd2a933b8929525129a6cb9dcf6ed66d0adf exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: don't touch anything outside the temp folder. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit a02dbd2 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 18, 2026
👁 Observed during the install test · Nov 18, 2026 : no network contact
🔎 Last checked · Oct 4, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
a02dbd2 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 18, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Oct 4, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.