clerk-core-workflow-a

Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%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 highly actionable with executable, copy-paste-ready Clerk code, but it is verbose due to duplication with an unreferenced bundle file and lacks explicit validation checkpoints in its workflow. Tightening the inline examples to reference the existing implementation guide would improve both conciseness and progressive disclosure.

Suggestions

Reference references/implementation-guide.md from the body (e.g., under each step or an 'Advanced' section) and trim the inline code to the essentials, removing the duplication that currently inflates token count.

Add explicit validation checkpoints to the workflow — e.g., after Step 1 confirm env vars are loaded, and after Step 3 verify OAuth redirect URIs in the Dashboard match redirectUrl before proceeding.

Resolve the divergence between the body and implementation-guide.md (different appearance props, different sign-in error handling) so the linked reference stays authoritative and consistent.

Dimension	Reasoning	Score
Conciseness	Code is largely lean without over-explaining Clerk concepts, but the ~330-line body duplicates much of references/implementation-guide.md (same five steps restated), adding length without new value. Mostly efficient but could be tightened by offloading detail to the reference.	2 / 3
Actionability	Provides fully executable Next.js/TypeScript with real imports, concrete env-var configuration, and specific error-code switch handling — copy-paste ready, matching the level-3 anchor.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced and the sign-up verification sub-flow is handled, but there are no explicit validation/verification checkpoints (e.g., confirm redirect URIs match, verify env vars loaded). Sequence present but checkpoints implicit, capping at 2.	2 / 3
Progressive Disclosure	A bundle file references/implementation-guide.md exists but is never referenced or signaled in the body, and its content duplicates the inline steps rather than being linked as the detailed layer. Some structure present but references are orphaned rather than clearly signaled.	2 / 3
	Total	9 / 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 strong: it states concrete capabilities, gives explicit use-when guidance, and lists natural trigger phrases scoped to a distinct Clerk authentication niche. No significant weaknesses to address.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Implement user sign-up and sign-in flows", "building authentication UI", "customizing sign-in experience", "implementing OAuth social login" — matching the level-3 anchor of multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers what ("Implement user sign-up and sign-in flows with Clerk") and when ("Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login"), matching the level-3 anchor.	3 / 3
Trigger Term Quality	Provides natural phrases users would actually say — "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login" — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Clerk authentication with distinct clerk-prefixed triggers; unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 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

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/clerk-pack/skills/clerk-core-workflow-a/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.