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".
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-common-errors/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 with excellent trigger terms and completeness. Its main weakness is that the capabilities described are somewhat general ('troubleshoot common errors') rather than listing specific concrete troubleshooting actions. The Clerk-specific focus gives it strong distinctiveness.
Suggestions
Add specific concrete actions like 'resolve middleware configuration errors, debug token/session issues, fix SDK version conflicts, troubleshoot webhook failures' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk) and mentions some categories of issues (authentication errors, SDK issues, configuration problems), but doesn't list specific concrete actions like 'resolve middleware conflicts', 'fix token expiration', or 'debug webhook failures'. | 2 / 3 |
Completeness | Clearly answers both 'what' (troubleshoot common Clerk errors and issues) and 'when' (encountering authentication errors, SDK issues, or configuration problems) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms that users would actually type: 'clerk error', 'clerk not working', 'clerk authentication failed', 'clerk issue', 'fix clerk'. These cover common phrasings well. | 3 / 3 |
Distinctiveness Conflict Risk | Clerk is a specific product/service, and the trigger terms are all Clerk-specific, making this highly unlikely to conflict with other skills. The niche is clearly defined. | 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 troubleshooting reference with highly actionable, executable code examples covering the most common Clerk errors. Its main weaknesses are moderate verbosity from duplicated content (the summary table restates the detailed sections) and the lack of explicit verification/feedback loops after applying fixes. The organization by error category is intuitive for lookup but could benefit from offloading some detail to supporting files.
Suggestions
Add a brief verification step after each fix (e.g., 'Restart dev server and confirm no error in console') to create feedback loops — their absence in a troubleshooting context limits workflow clarity.
Remove the Error Handling summary table or the detailed sections — having both is redundant. Keep the table as a quick-reference and move detailed fixes to a separate bundle file.
Remove the Prerequisites and Output sections — they add little value and consume tokens on information Claude can infer.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with code-focused solutions, but includes some unnecessary elements like the Prerequisites section (Claude knows what browser dev tools are), the Output section that restates what the skill does, and the Error Handling summary table that largely duplicates the detailed sections above it. | 2 / 3 |
Actionability | Excellent actionability — every error includes executable TypeScript/bash code with specific fixes. The diagnostic checklist is copy-paste ready, webhook examples show both correct and incorrect patterns, and server/client component distinctions include complete working components. | 3 / 3 |
Workflow Clarity | The diagnostic checklist at the end provides a clear sequence, but the main body is organized as a reference lookup rather than a workflow. For a troubleshooting skill this is reasonable, but there's no explicit 'identify error → diagnose → fix → verify' feedback loop within each error category — fixes are given but verification steps are mostly absent. | 2 / 3 |
Progressive Disclosure | Content is well-organized into error categories with clear headers, but the skill is quite long (~150+ lines of inline content) with no bundle files to offload detail into. The reference to 'clerk-debug-bundle' in Next Steps is good but the webhook and middleware sections could be split out. The summary table partially serves as a quick-reference layer but duplicates content. | 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.