clerk-ci-integration

Configure Clerk CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Clerk tests into your build process. Trigger with phrases like "clerk CI", "clerk GitHub Actions", "clerk automated tests", "CI clerk", "clerk pipeline".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable and concise code-forward content with a clear step sequence, but it falls short on workflow validation checkpoints for fragile CI operations and fails to leverage the existing reference bundle, leaving detailed content inlined and the reference orphaned.

Suggestions

Add explicit validation checkpoints to the workflow (e.g., verify GitHub secrets exist before running, confirm e2e/.auth/user.json was saved before the authenticated project runs) with a fix-and-retry loop to lift workflow_clarity.

Link the existing references/implementation-guide.md from the body (e.g., 'See [implementation-guide.md](references/implementation-guide.md) for alternate workflow variants') and move the duplicated detailed patterns there to reduce inlining and fix the orphaned reference.

Reconcile divergent details between the body and the reference (e.g., CLERK_PK_TEST vs CLERK_PUBLISHABLE_KEY_TEST secret names, `npm run dev` vs `npm run start` webServer) so the two sources agree.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and lean — it leads with executable YAML/TypeScript blocks and tables and avoids explaining concepts Claude already knows; minimal padding, though some tightening of the additive Examples section is possible.	3 / 3
Actionability	Every step provides complete, executable code — full GitHub Actions workflow, Playwright auth setup, config, and a real @clerk/backend seed script with env-var wiring — copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	The six steps are clearly sequenced, but for fragile CI/Playwright-auth operations there are no explicit validation checkpoints or validate→fix→retry feedback loops; an Error Handling table exists but in-workflow verification is only implicit, capping this at 2.	2 / 3
Progressive Disclosure	A references/implementation-guide.md bundle file exists but is never linked or signaled from the body, and ~230 lines of detailed implementation are inlined rather than split out — structure is present, but content that should be separate is inline and the reference is orphaned.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states concrete capabilities and provides explicit 'Use when' triggers with natural keyword variations. It clearly carves out a distinct Clerk CI/CD niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Configure Clerk CI/CD integration with GitHub Actions and testing', 'setting up automated testing, configuring CI pipelines', 'integrating Clerk tests' — matching the score-3 anchor rather than the narrower score-2 'domain and some actions'.	3 / 3
Completeness	Explicitly answers both what ('Configure Clerk CI/CD integration with GitHub Actions and testing') and when ('Use when setting up automated testing, configuring CI pipelines, or integrating Clerk tests'), with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say — 'clerk CI', 'clerk GitHub Actions', 'clerk automated tests', 'CI clerk', 'clerk pipeline' — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Clerk-specific CI/CD niche with Clerk-prefixed triggers is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 4 minutes ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.