clerk-common-errors

Troubleshoot common Clerk errors and issues. Use when encountering authentication errors, SDK issues, or configuration problems with Clerk. Trigger with phrases like "clerk error", "clerk not working", "clerk authentication failed", "clerk issue", "fix clerk".

Quality

85%

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

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.

A well-organized, highly actionable troubleshooting reference with lean, executable fixes across five error categories. Its main weaknesses are the absence of explicit validation feedback loops and broken cross-file navigation around the implementation-guide reference.

Suggestions

Link the existing references/implementation-guide.md from the body (e.g., a '## Implementation Guide' section with a relative link) instead of the non-existent 'clerk-debug-bundle', or remove the dangling Next Steps reference.

Add an explicit validate-fix-retry loop for the diagnostic checklist (e.g., 'After applying a fix, re-run the relevant diagnostic step; only proceed when it passes') to lift workflow clarity.

Split the five full inline error-category code blocks into the implementation guide and keep SKILL.md as a concise overview pointing one level deep, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence — it does not explain what Clerk or authentication is, and goes straight to terse '// Cause' / '// Fix' comments plus executable code, with every section earning its place.	3 / 3
Actionability	Each error is paired with concrete, copy-paste-ready TypeScript/TSX, bash, and curl snippets (e.g. createClerkClient diagnostic, middleware matcher, req.text() webhook fix), matching the fully-executable anchor.	3 / 3
Workflow Clarity	The Quick Diagnostic Checklist provides a numbered sequence, but there are no explicit validation feedback loops (validate -> fix -> retry); checkpoints are implicit, and the body is organized as a reference catalog rather than a sequenced workflow.	2 / 3
Progressive Disclosure	Internal section organization is clean, but cross-file navigation is broken: references/implementation-guide.md exists yet is never linked from the body, while 'Next Steps' points to a non-existent 'clerk-debug-bundle' — references are present but not correctly signaled.	2 / 3
	Total	10 / 12 Passed

Description

90%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.

A strong description that clearly states purpose, usage conditions, and natural trigger phrases, with a distinct Clerk niche. The only weakness is that the capability statement relies on a single generic verb ('Troubleshoot') rather than enumerating specific actions.

Dimension	Reasoning	Score
Specificity	It names the domain ('common Clerk errors and issues') and references sub-domains (authentication, SDK, configuration), but the only concrete action verb is 'Troubleshoot' — it does not list multiple specific actions like the score-3 anchor ('Extract text... fill forms, merge documents').	2 / 3
Completeness	It explicitly answers both 'what' ('Troubleshoot common Clerk errors and issues') and 'when' ('Use when encountering authentication errors, SDK issues, or configuration problems'), with explicit trigger phrases.	3 / 3
Trigger Term Quality	It lists five natural phrases a user would actually say ('clerk error', 'clerk not working', 'clerk authentication failed', 'clerk issue', 'fix clerk'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Clerk-specific niche and clerk-prefixed trigger phrases make it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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-common-errors/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.