clerk-sdk-patterns

Common Clerk SDK patterns and best practices. Use when implementing authentication flows, accessing user data, or integrating Clerk SDK methods in your application. Trigger with phrases like "clerk SDK", "clerk patterns", "clerk best practices", "clerk API usage".

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 catalog of Clerk SDK patterns with lean executable code and a useful error-handling table. It loses points for an orphaned bundle file that duplicates inline content and for lacking explicit validation/sequencing in its auth workflows.

Suggestions

Reference the existing bundle from the body (e.g. 'For expanded route-handler and hook examples, see [implementation-guide.md](references/implementation-guide.md)') and move the duplicated Pattern 1–2 detail there to keep SKILL.md as an overview.

Add brief validation checkpoints to the riskier patterns — e.g. after getToken() note 'verify the JWT template is configured in Dashboard > JWT Templates', and after auth() checks note the server-context requirement — to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean executable TypeScript with terse inline comments and minimal prose; it assumes Claude's competence and avoids explaining React/Next.js or auth basics.	3 / 3
Actionability	Each pattern is complete, copy-paste-ready TypeScript with real imports and runnable logic, plus a concrete error-handling table mapping causes to fixes.	3 / 3
Workflow Clarity	Patterns are cleanly sectioned (Pattern 1–5, Error Handling, Examples) but there is no explicit multi-step sequencing or validation checkpoint guidance for operations that can fail (e.g. getToken, auth checks).	2 / 3
Progressive Disclosure	A bundle file references/implementation-guide.md exists (192 lines, expanded Pattern 1–2 examples) but is never linked or signaled from the SKILL.md body, and much of that detail is duplicated inline rather than split out.	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 solid, third-person description that covers what and when with explicit, natural trigger phrases. Its main weakness is the generic 'patterns and best practices' framing, which undersells the concrete capabilities listed in the 'Use when' clause.

Suggestions

Lead with concrete actions (e.g. 'Implement server/client auth, middleware-protected routes, org-aware queries, and custom JWT templates with the Clerk SDK') instead of the generic 'Common Clerk SDK patterns and best practices'.

Broaden trigger phrases beyond the 'clerk X' formula to include task-oriented terms users actually say, e.g. 'clerk authentication', 'clerk login flow', 'clerk middleware'.

Dimension	Reasoning	Score
Specificity	Names the Clerk domain and some actions ('implementing authentication flows, accessing user data, or integrating Clerk SDK methods') but the lead 'Common Clerk SDK patterns and best practices' is generic and not a comprehensive list of concrete actions.	2 / 3
Completeness	Explicitly answers both what ('Common Clerk SDK patterns and best practices') and when ('Use when implementing authentication flows...') with an explicit trigger clause.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would say — 'clerk SDK', 'clerk patterns', 'clerk best practices', 'clerk API usage' — giving good coverage of likely utterances.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear Clerk-SDK niche with Clerk-specific triggers, 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
Path: plugins/saas-packs/clerk-pack/skills/clerk-sdk-patterns/SKILL.md
Commit: 0540a62

Reviewed: about 21 hours 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.