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

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/clerk-pack/skills/clerk-sdk-patterns/SKILL.md

Quality

Content

64%

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

This is a solid reference-style skill with excellent actionability — every pattern includes complete, executable TypeScript code with realistic usage. The main weaknesses are moderate verbosity (unnecessary overview, output, and prerequisites sections) and lack of validation/verification steps for the patterns. The content would benefit from trimming redundant sections and either splitting into multiple files or keeping it leaner as a single file.

Suggestions

Remove the 'Prerequisites', 'Output', and 'Overview' sections — they explain things Claude already knows and add no actionable value.

Add brief validation/verification notes to key patterns, e.g., 'Test middleware by accessing a protected route while signed out — should redirect to sign-in' after the middleware pattern.

Consider splitting the error handling table and the Supabase JWT integration into separate referenced files to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good code examples, but includes some unnecessary sections like 'Prerequisites' (Claude knows what Clerk needs), the 'Output' section which just restates what the patterns do, and 'Next Steps' which adds little value. The overview paragraph is also somewhat redundant given the title.	2 / 3
Actionability	All patterns include fully executable TypeScript code with proper imports, realistic usage contexts, and copy-paste ready examples. The error handling table provides specific causes and solutions. The JWT template configuration includes both code and the JSON claims structure.	3 / 3
Workflow Clarity	The patterns are presented as independent recipes rather than a sequenced workflow, which is appropriate for a reference-style skill. However, there are no validation checkpoints or feedback loops — for example, no guidance on verifying middleware is working correctly, no steps to test JWT template configuration, and no verification that auth() is returning expected values during development.	2 / 3
Progressive Disclosure	The content is well-structured with clear headings and patterns, but it's a fairly long monolithic file (~150 lines of content) with no bundle files to offload detail into. The error handling table and examples could be in separate referenced files. External links to Clerk docs are provided but internal progressive disclosure is absent.	2 / 3
	Total	9 / 12 Passed

Description

89%

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

This is a solid skill description that clearly identifies its domain (Clerk SDK), provides explicit trigger guidance, and is distinctive enough to avoid conflicts. Its main weakness is that the capability descriptions could be more concrete—listing specific patterns, methods, or components rather than general categories like 'authentication flows' and 'accessing user data.'

Suggestions

Add more specific concrete actions, e.g., 'Configure ClerkProvider, use useUser/useAuth hooks, set up sign-in/sign-up flows, manage session tokens, implement middleware protection.'

Dimension	Reasoning	Score
Specificity	Names the domain (Clerk SDK) and mentions some actions like 'implementing authentication flows, accessing user data, integrating Clerk SDK methods,' but these are somewhat general and not highly concrete (e.g., doesn't list specific methods, hooks, or patterns).	2 / 3
Completeness	Clearly answers both 'what' (common Clerk SDK patterns and best practices for auth flows, user data, SDK integration) and 'when' (explicit 'Use when' clause and 'Trigger with phrases' section providing clear activation guidance).	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'clerk SDK', 'clerk patterns', 'clerk best practices', 'clerk API usage', 'authentication flows', 'user data'. Good coverage of terms a developer would naturally use when seeking Clerk help.	3 / 3
Distinctiveness Conflict Risk	Clerk SDK is a specific third-party authentication library, making this clearly distinguishable from generic auth skills or other SDK skills. The trigger terms are specific enough to avoid conflicts with general authentication or other auth provider skills.	3 / 3
	Total	11 / 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 — 9 / 11 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	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 5 days 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.