技能 clerk-testing
📦
clerk-testing
v1.2.1 內容修訂 r1 安全 ⚙️ 外部命令🌐 網路存取🔑 環境變數
Test Clerk Authentication with Playwright or Cypress
Authentication setup and session handling can make end-to-end tests unreliable. This skill guides Clerk testing through framework-specific documentation, development keys, testing tokens, and session reuse.
支援: Claude Codex Code(CC)
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
智能體請求
Review the Skillstore skill "clerk-testing" from https://skillstore.io/skills/clerk-clerk-testing.md and its manifest at https://skillstore.io/api/skills/clerk-clerk-testing/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「clerk-testing」。 Plan Clerk authentication setup for an existing Playwright project.
預期結果:
- Consult the official Clerk Playwright testing guide.
- Initialize the testing environment and configure development credentials.
- Set up the testing token before visiting authentication pages.
- Prepare reusable authentication state with global setup while preserving isolated test contexts.
正在使用「clerk-testing」。 Review why our Cypress authentication tests fail before sign-in.
預期結果:
- Check that Clerk commands are registered in the Cypress support file.
- Verify that the testing token is configured before authentication navigation.
- Confirm that the application uses development-instance keys.
- Review the official Cypress guide for framework-specific setup requirements.
安全審計
安全v1 • 2026/10/6 開啟版本化報告
Twenty findings are false positives involving Markdown code spans, reference URLs, and documented credential requirements. One finding is confirmed: unpinned CLI execution downloads code and writes development credentials. No evidence found of prompt injection or credential exfiltration.
1
已掃描檔案
62
分析行數
1
複核項目
0
已忽略的誤報
能力複核項目 (1)
這些是真實的本機能力，對此技能而言可能是預期行為，因此需要複核，但不會按已確認的惡意行為計分。
中
Ruby/shell backtick execution
4. Use development-instance keys only (`pk_test_*` / `sk_test_*`). If the project has no keys yet, `
Although backticks are Markdown, the workflow recommends npx clerk@latest init, which executes downloaded package code and writes credentials. The mutable version creates supply-chain risk.
風險因素
審計單位: codex
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/clerk-clerk-testing/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/clerk-clerk-testing?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/clerk-clerk-testing?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/clerk-clerk-testing/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/clerk-clerk-testing.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
clerk. (2026). clerk-testing security audit report (audit version 1) [Author version 1.2.1]. Skillstore. https://skillstore.io/skills/clerk-clerk-testing/audits/1BibTeX 引用
@techreport{clerk-clerk-clerk-testing-2026,
author = {clerk},
title = {clerk-testing security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/clerk-clerk-testing/audits/1},
note = {Author version 1.2.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "clerk-testing security audit report (audit version 1)"
version: "1.2.1"
type: report
authors:
- name: "clerk"
date-released: "2026-10-06"
url: "https://skillstore.io/skills/clerk-clerk-testing/audits/1"
identifiers:
- type: other
value: "skillstore:clerk-clerk-testing:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中 55
架構
100
可維護性
87
內容
65
社群
100
規範符合度
你可以打造什麼
Add Playwright Authentication Coverage
Plan Clerk setup, testing tokens, and reusable authentication state for an existing Playwright project.
Diagnose Cypress Authentication Failures
Review command registration, navigation timing, and development keys when Clerk authentication tests fail.
Review Shared Test Configuration
Check development credential usage and authentication state handling before adopting Clerk tests in a shared pipeline.
試試這些提示
Find the Right Setup Guide
I use [Playwright or Cypress] with Clerk. Identify the official testing guide and list the setup prerequisites.
Plan Authentication Test Setup
Help plan Clerk authentication tests for my [framework] application. Include development credentials, helper initialization, and testing tokens before navigation.
Troubleshoot Failed Authentication
My Clerk tests fail during authentication in [framework]. Review testing token timing, command registration, selectors, and session isolation using the official guide.
Review Session Reuse and Provisioning
Review our Playwright globalSetup and storageState strategy for Clerk. Identify session isolation risks and credential handling concerns. Require approval before any CLI provisioning.
最佳實務
- Use development-instance credentials and keep secrets outside version control.
- Configure the Clerk testing token before navigating to authentication pages.
- Reuse authentication state where appropriate while keeping test contexts isolated.
避免
- Using production credentials in authentication tests.
- Navigating to authentication pages before configuring the testing token.
- Repeating UI sign-in in every test when reusable authentication state is suitable.
常見問題
Which testing frameworks does this skill cover?
It covers Clerk authentication testing with Playwright and Cypress through framework-specific documentation and setup guidance.
Does this skill run tests automatically?
No. It provides guidance and documentation references. Your project needs a configured test framework and application.
Which credentials should I use?
Use development-instance credentials. The skill requires a publishable key and either a Clerk secret key or a Clerk testing token.
Why is the testing token important?
The testing token bypasses Clerk bot detection for test flows. Configure it before navigating to authentication pages.
How can I reduce repeated sign-in work?
For Playwright, the skill recommends global setup and reusable authentication state. Keep each test context isolated.
What should I review before running Clerk CLI initialization?
Review the CLI version and obtain execution approval. Initialization can create an application and write development credentials to an environment file.
開發者詳細資訊
作者
clerk授權
MIT
作者版本
v1.2.1
Skillstore 修訂
r1
儲存庫
https://github.com/clerk/skills/tree/9502ec5575247ac2d5a229b9e96a3be700a4a19a/skills/clerk-testing引用
4676f9b94082a87e58987510071598b362f5d9db
維護新鮮度
2026/10/6
使用量
0 次下載 · 0 次瀏覽
檔案結構
📄 SKILL.md