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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clerk-common-errors88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 well-structured skill description with excellent trigger terms and clear 'when to use' guidance. The main weakness is the lack of specific concrete actions - it describes categories of problems (authentication errors, SDK issues) rather than specific troubleshooting capabilities. Adding 2-3 specific actions would elevate this from good to excellent.
Suggestions
Add specific concrete actions like 'diagnose webhook failures, resolve session token issues, fix middleware configuration, debug redirect loops' to improve specificity
Consider adding file extensions or specific Clerk concepts users might mention like '.env configuration', 'ClerkProvider', 'useAuth hook', 'JWT tokens'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk) and categories of issues (authentication errors, SDK issues, configuration problems), but doesn't list specific concrete actions like 'diagnose webhook failures', 'fix session token issues', or 'resolve middleware conflicts'. | 2 / 3 |
Completeness | Clearly answers both what (troubleshoot common Clerk errors and issues) and when (encountering authentication errors, SDK issues, configuration problems) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually say: 'clerk error', 'clerk not working', 'clerk authentication failed', 'clerk issue', 'fix clerk'. These are realistic phrases users would type when encountering problems. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically targets Clerk (a specific authentication service) troubleshooting. The explicit 'clerk' keyword throughout makes it unlikely to conflict with general authentication or other auth provider skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted troubleshooting skill with excellent actionability and conciseness. The error categories are comprehensive with executable solutions. The main weakness is the lack of a structured diagnostic workflow that guides through verification steps after applying fixes.
Suggestions
Add a diagnostic workflow section at the top that guides through: identify error -> apply fix -> verify resolution -> escalate if needed
Include verification commands after each solution to confirm the fix worked (e.g., 'After applying the fix, verify with: npm run dev and check console for errors')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting error messages, causes, and solutions without unnecessary explanation. It assumes Claude understands TypeScript, Next.js, and authentication concepts without over-explaining. | 3 / 3 |
Actionability | Every error category includes executable code snippets that are copy-paste ready. Solutions include specific bash commands, TypeScript code, and concrete patterns for handling each error type. | 3 / 3 |
Workflow Clarity | While individual error solutions are clear, the skill lacks explicit diagnostic workflows with validation checkpoints. There's no structured 'diagnose -> fix -> verify' sequence for troubleshooting, which is important for debugging tasks. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear categories, a quick reference table for fast lookup, and appropriate external references to Clerk documentation. The structure allows quick scanning to find relevant errors. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.