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

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

80%Weight 40%Scale 1-3

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

The body is lean and highly actionable with copy-paste-ready code across a clear six-step sequence. Its weaknesses are missing validation checkpoints in the workflow and an unreferenced, duplicative bundle file that underuses progressive disclosure.

Suggestions

Add explicit validation checkpoints to the workflow — e.g., verify GitHub secrets are configured and the seed test user exists before the 'Run E2E tests' step — to support a validate-then-proceed feedback loop.

Either link references/implementation-guide.md from the body (e.g., a '## Advanced patterns' section pointing to it) or remove the duplicated workflow/E2E/test-user content from one of the two locations so the bundle is clearly signaled and not redundant.

Distinguish the body's quick-start path from the reference's expanded examples so the SKILL.md serves as an overview pointing one level deep to the guide.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable code and compact tables with no padding about what Clerk or Playwright is; every section earns its tokens and assumes Claude's competence, matching the lean anchor rather than the over-explained 2.	3 / 3
Actionability	Provides fully executable, copy-paste-ready GitHub Actions YAML, Playwright setup/config, E2E specs, a Clerk seed script, and a Vitest mock example, satisfying the top anchor.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced and an Error Handling table exists, but there are no explicit validation checkpoints (e.g., verify secrets exist or the test user exists before running E2E), so it sits at the checkpoints-missing anchor rather than 3.	2 / 3
Progressive Disclosure	A references/implementation-guide.md bundle exists but is never linked from the body and largely duplicates the body's workflow/E2E/test-user content, fitting 'references present but not clearly signaled; content that should be separate is inline' rather than the well-signaled 3.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

The description is concise, third-person, and cleanly answers both what the skill does and when to use it with natural trigger phrases. It is distinctive within a clear Clerk CI/CD niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Configure Clerk CI/CD integration with GitHub Actions and testing', 'setting up automated testing', 'configuring CI pipelines', 'integrating Clerk tests into your build process' — matching the multi-action anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Clearly 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 explicit triggers, satisfying the top anchor.	3 / 3
Trigger Term Quality	Explicit trigger phrases ('clerk CI', 'clerk GitHub Actions', 'clerk automated tests', 'CI clerk', 'clerk pipeline') are natural terms a user would actually say, giving good coverage rather than the partial coverage at 2.	3 / 3
Distinctiveness Conflict Risk	The Clerk-specific niche with 'clerk'-prefixed triggers makes it clearly distinguishable and unlikely to fire for unrelated skills, matching the clear-niche anchor.	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
Path: plugins/saas-packs/clerk-pack/skills/clerk-ci-integration/SKILL.md
Commit: 4c47e33

Reviewed: 1 day 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.