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".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clerk-pack/skills/clerk-sdk-patterns/SKILL.mdQuality
Discovery
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 niche (Clerk SDK), provides explicit trigger guidance, and answers both what and when. Its main weakness is that the capability descriptions are somewhat general—mentioning 'authentication flows' and 'accessing user data' rather than listing specific Clerk SDK operations or patterns. The explicit trigger phrases and 'Use when' clause are strong additions.
Suggestions
Add more specific concrete actions like 'configure middleware, manage session tokens, implement webhook handlers, set up multi-tenant organizations' to improve specificity.
| 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 don't list specific concrete actions like 'configure session tokens, manage user metadata, implement SSO.' | 2 / 3 |
Completeness | Clearly answers both 'what' (common Clerk SDK patterns and best practices for authentication flows, user data, SDK integration) and 'when' (explicit 'Use when' clause and 'Trigger with phrases like' 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'. These cover common variations of how users would phrase requests related to Clerk. | 3 / 3 |
Distinctiveness Conflict Risk | Clerk SDK is a specific third-party authentication library, making this highly distinctive. The trigger terms are narrowly scoped to Clerk specifically, so it's unlikely to conflict with general auth skills or other SDK skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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 skill with excellent actionability — every pattern includes complete, executable TypeScript code with proper imports and realistic usage. The main weaknesses are moderate verbosity (unnecessary sections like Output and Prerequisites), lack of validation/verification steps for the patterns, and a monolithic structure that could benefit from splitting detailed patterns into separate bundle files. The broken reference to 'clerk-core-workflow-a' is a minor issue.
Suggestions
Remove the 'Prerequisites', 'Output', and 'Overview' sections — they add little value and Claude already understands these concepts. The patterns speak for themselves.
Add verification steps for critical patterns, e.g., 'Test middleware by accessing a protected route without auth — should redirect to sign-in' or 'Verify JWT token with `jwt.io` before integrating with Supabase'.
Either remove the 'Next Steps' reference to 'clerk-core-workflow-a' or include it as a bundle file to avoid a broken reference.
| 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 references a file that doesn't exist in the bundle. The overview paragraph is also somewhat redundant given the title. | 2 / 3 |
Actionability | All five patterns provide fully executable TypeScript code with proper imports, realistic usage contexts, and copy-paste ready examples. The error handling table adds concrete troubleshooting guidance with specific solutions. The JWT template configuration includes the actual 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 skill. However, there are no validation checkpoints or verification steps — for example, no guidance on testing that middleware is correctly protecting routes, or verifying JWT tokens work with external services. The patterns are clear individually but lack feedback loops. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headings and patterns, but it's somewhat monolithic — all patterns are inline in a single file with no bundle files to offload detailed content. The reference to 'clerk-core-workflow-a' in Next Steps points to a non-existent file. External resource links are provided but no internal bundle references exist to support progressive disclosure. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%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 | |
- Commit
3a2d27d
- Reviewed
Table of Contents
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.