clerk-testing

Test Clerk authentication flows with Playwright or Cypress.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/YOYOMAII/foundry --skill clerk-testing-yoyomaii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk-testing
Source: https://github.com/YOYOMAII/foundry/tree/main/.agents/skills/clerk-testing
Command: npx skills add https://github.com/YOYOMAII/foundry --skill clerk-testing-yoyomaii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of testing authentication flows in Clerk-integrated applications by providing a standardized approach to session management and state persistence.

Core Features & Use Cases

  • Auth Flow Testing: Provides a structured decision tree for integrating Clerk with Playwright or Cypress.
  • Session Management: Implements best practices for isolated session state and storageState to speed up test suites.
  • Use Case: Use this skill to configure your CI/CD pipeline to run automated end-to-end tests that bypass bot detection and verify user login/signup flows without manual intervention.

Quick Start

Use the clerk-testing skill to initialize a new Playwright test suite with proper session state persistence for your Clerk-enabled application.

Frequently Asked Questions about clerk-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up E2E authentication testing for Clerk with Playwright or Cypress?

Facilitate E2E authentication testing for Clerk by using a structured decision tree to integrate Playwright or Cypress, implementing isolated session states and automated test environment setup to verify login processes efficiently.

What's the best way to manage Clerk session state in E2E tests?

Manage Clerk session state in E2E tests by implementing isolated sessions and storageState persistence to speed up test suites and bypass bot detection while verifying user signup and login flows.

Can I use this approach to bypass bot detection in Clerk automated tests?

Yes, you can bypass bot detection in Clerk automated tests by configuring your CI/CD pipeline with test-specific API keys and standardized setup commands to securely verify user authentication flows.

Do I need test-specific API keys to run automated E2E tests for Clerk authentication?

Yes, test-specific API keys are required to maintain security and test reliability when running automated end-to-end authentication tests for your Clerk-enabled web applications.

Why does my Clerk session state persist across E2E test runs?

Clerk session state persists across E2E test runs if you lack isolated session management; implementing storageState best practices ensures session isolation to speed up Playwright and Cypress test suites.

Does this Skill support both Playwright and Cypress for Clerk auth flow testing?

Yes, this Skill supports both Playwright and Cypress for Clerk auth flow testing, providing a standardized approach to session management and state persistence to ensure secure and efficient verification.