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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

A highly actionable troubleshooting reference with executable code throughout, but it is held back by redundancy between the inline table and the bundled reference, missing verify-the-fix feedback loops, and a broken pointer to a non-existent bundle.

Suggestions

Move the detailed per-error implementations into references/implementation-guide.md and keep SKILL.md as a concise overview that links to it, eliminating the duplication between the inline Error Handling table and the bundled guide.

Add explicit validation/confirmation steps after each fix (e.g., re-run the diagnostic command or confirm the error no longer reproduces) so the workflow includes a fix-then-verify loop.

Fix or remove the 'Proceed to clerk-debug-bundle' Next Steps pointer, since no such bundle file exists in the skill.

Dimension	Reasoning	Score
Conciseness	Each error entry is lean with cause/fix comments and executable code and no padding about concepts Claude already knows, but the inline Error Handling table duplicates the per-error fixes already given above it, and much of the body overlaps the bundled implementation-guide.md.	2 / 3
Actionability	Fully executable, copy-paste-ready TypeScript and bash examples for each error (ClerkProvider wrapping, middleware matcher, svix webhook verification, diagnostic commands), with no pseudocode.	3 / 3
Workflow Clarity	Errors are clearly grouped into sequenced categories with an ordered 1-4 diagnostic checklist, but there are no explicit validation/confirmation checkpoints verifying a fix actually resolved the error.	2 / 3
Progressive Disclosure	The body is well-sectioned and points to a real one-level reference (references/implementation-guide.md), but it keeps all five error categories inline and largely duplicates the reference instead of splitting detail out, and the 'Next Steps' link to clerk-debug-bundle points to a bundle file that does not exist.	2 / 3
	Total	9 / 12 Passed

Description

90%

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, well-structured description that clearly defines both purpose and trigger conditions in third-person voice. The only soft spot is specificity, where a single generic action ('Troubleshoot') replaces a fuller enumeration of concrete capabilities.

Suggestions

Expand specificity by listing concrete actions, e.g. 'Diagnose, configure, and resolve Clerk authentication, middleware, webhook, and server/client component errors' rather than the single generic verb 'Troubleshoot'.

Dimension	Reasoning	Score
Specificity	Names the Clerk domain and the general action 'Troubleshoot common Clerk errors and issues', but does not list multiple distinct concrete actions, so it stops at 'names domain and some actions'.	2 / 3
Completeness	Explicitly states what it does ('Troubleshoot common Clerk errors and issues') and when to use it ('Use when encountering authentication errors, SDK issues, or configuration problems with Clerk'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides natural user phrases — 'clerk error', 'clerk not working', 'clerk authentication failed', 'clerk issue', 'fix clerk' — giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear Clerk-specific niche with Clerk-prefixed trigger phrases, making it 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
Commit: 02d6341

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