clerk-core-workflow-b

Implement session management and middleware with Clerk. Use when managing user sessions, configuring route protection, or implementing token refresh and custom JWT templates. Trigger with phrases like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT".

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

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

A concise, well-structured skill body with a clear sequenced workflow and an explicit verification step, plus a cleanly signaled one-level reference for deep detail. Its main weakness is actionability: the body relies on descriptive dialogue examples and defers all executable code to reference files.

Suggestions

Add at least one minimal executable code snippet inline (e.g. a clerkMiddleware + createRouteMatcher skeleton) so the body is copy-paste actionable without opening references.

Replace the dialogue-style Examples with concrete before/after code or command pairs that show the actual configuration produced.

Link the existing references/implementation.md from the body (e.g. in Instructions or a References section) so it is not an orphan file unreachable from the SKILL entry point.

Dimension	Reasoning	Score
Conciseness	The body is lean: terse numbered steps, no explaining of what Clerk/Next.js is, and detail deferred to the deep-dive reference, so every token earns its place rather than padding concepts Claude already knows.	3 / 3
Actionability	Steps name specific APIs (clerkMiddleware, auth(), currentUser) and the Examples describe intent, but the body contains no copy-paste executable code (it lives in references) and the examples are dialogue-style descriptions rather than concrete code, fitting the incomplete-guidance anchor at 2.	2 / 3
Workflow Clarity	Six clearly sequenced steps culminate in an explicit validation checkpoint ("Verify: signed-out user cannot hit protected routes; signed-in user can; org role gates hold"), and the operation is config rather than destructive/batch so the missing retry loop does not cap it at 2.	3 / 3
Progressive Disclosure	A concise overview points via a clearly signaled one-level link to [session-middleware-deep-dive.md](references/session-middleware-deep-dive.md), keeping the SKILL.md as an entry point with detail split into a reference file.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

A strong, well-structured description that clearly states capabilities, provides explicit natural trigger phrases, and answers both what and when in third person. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: "managing user sessions, configuring route protection, or implementing token refresh and custom JWT templates", matching the multi-action anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Answers both "what" ("Implement session management and middleware with Clerk") and "when" with an explicit "Use when..." clause plus trigger phrases, satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Explicit natural triggers like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT" are phrases a user would actually say, giving good coverage rather than the partial set at 2.	3 / 3
Distinctiveness Conflict Risk	The Clerk-specific niche with clerk-prefixed triggers ("clerk session", "clerk middleware") makes it unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/clerk-pack/skills/clerk-core-workflow-b/SKILL.md
Commit: 4c47e33

Reviewed: 3 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.