clerk-core-workflow-b
Implement session management and middleware with Clerk. Use when managing user sessions, configuring route protection, or implementing token refresh logic. Trigger with phrases like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clerk-core-workflow-b81
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 term coverage and clear 'Use when' guidance. The main weakness is that the capability descriptions could be more concrete with specific actions rather than general categories like 'session management'. The explicit trigger phrases significantly strengthen the description's utility for skill selection.
Suggestions
Expand specificity by listing concrete actions like 'configure session expiry, set up protected API routes, handle token refresh callbacks, implement custom session claims'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk) and some actions (session management, middleware, route protection, token refresh logic), but the actions are somewhat general rather than listing multiple concrete specific operations like 'configure session expiry', 'set up protected routes', etc. | 2 / 3 |
Completeness | Clearly answers both what (implement session management and middleware with Clerk) and when (managing user sessions, configuring route protection, implementing token refresh logic) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'clerk session', 'clerk middleware', 'clerk route protection', 'clerk token', 'clerk JWT'. These are specific, natural terms that cover common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Clerk authentication library with distinct triggers like 'clerk session', 'clerk middleware', 'clerk JWT'. Unlikely to conflict with generic auth skills or other authentication providers. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, actionable code examples for Clerk session management and middleware implementation. The main strengths are executable code and good organization. Weaknesses include some unnecessary explanatory content and missing validation checkpoints for middleware configuration, which is a common source of routing issues.
Suggestions
Add a validation checkpoint after Step 1 middleware configuration, such as 'Test by visiting a protected route while signed out - you should be redirected to /sign-in'
Remove the 'Prerequisites' section or reduce it to just 'Clerk SDK configured' - Claude doesn't need to be told it should understand Next.js middleware
Add a debugging step for common middleware issues like infinite redirect loops before the Error Handling table
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary elements like the 'Prerequisites' section mentioning 'Understanding of Next.js middleware' which Claude already knows, and the 'Output' section that restates what the code does. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready TypeScript code for middleware configuration, session management, token handling, and multi-session support. All examples are complete and specific with proper imports. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. For middleware configuration which can cause routing issues, there's no 'test this before proceeding' guidance or feedback loops for debugging middleware problems. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate use of external resource links at the end, and a 'Next Steps' pointer to related content. Content is appropriately organized without deep nesting or monolithic blocks. | 3 / 3 |
Total | 10 / 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.