clerk-auth

Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync

Quality

58%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/clerk-auth/SKILL.md

Quality

Content

47%Weight 40%Scale 1-5

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

The body is a clean, token-efficient overview with a genuine one-level-deep reference to a well-organized detailed guide. However, it functions almost purely as a pointer: no quick-start snippet, no named workflow steps, and no section index, leaving actionability and workflow clarity to whatever the reader finds in the referenced file.

Suggestions

Add a minimal quick-start block to SKILL.md (e.g. the clerkMiddleware wrap and one auth() server-component snippet) so the overview is not a bare pointer.

List the detailed guide's section names (Next.js App Router setup, middleware route protection, server/client component auth, organizations, webhook user sync, API route protection, sharp edges) so 'for focused work, load the relevant sections' is actionable without opening the whole guide.

State at least one concrete validation checkpoint inline, e.g. 'verify the webhook signature via Svix headers and confirm the middleware blocks an unauthenticated route before finishing'.

Dimension	Reasoning	Score
Conciseness	The body is lean — no explanations of concepts Claude already knows, no padding, everything earns its place except the 'User mentions or implies:' prefix repeated verbatim across nine bullets, which could be collapsed to one stem. This is a minor trim rather than the verbosity or unnecessary explanation of the lower anchors, so it sits just below the 'lean and efficient' 5.	4 / 5
Actionability	The body contains no code, commands, or task-specific steps — its only directive is 'Read [the detailed guide](references/detailed-guide.md) before executing this skill'. That is a high-level pointer missing the specific steps to execute, matching the 'minimal concrete guidance; high-level hints but missing the specific steps' anchor; it is not a 1 because the pointer names a real file and sets mandatory validation expectations.	2 / 5
Workflow Clarity	There is a rough directive ('read the guide before executing'; 'for focused work, load the relevant sections') but no sequenced workflow, no named checkpoints, and validation is only gestured at ('Treat its safety, prerequisites, and validation requirements as mandatory') rather than specified. It matches 'rough sequence present but many gaps; steps poorly defined' better than the 3 anchor, which requires an actual listed step sequence.	2 / 5
Progressive Disclosure	The bundle is one clearly-signaled reference one level deep: 'Read [the detailed guide](references/detailed-guide.md)' points to a real, well-structured file (per-pattern sections, Sharp Edges, anti-patterns), and the body distinguishes focused vs. end-to-end loading. It misses a 5 because 'load the relevant sections' gives no section index — Claude must open the 820-line guide to discover what the relevant sections even are.	4 / 5
	Total	12 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 focused, distinctive description that clearly states what the skill covers, anchored by the specific 'Clerk' niche. Its main weakness is the absence of any 'when to use' trigger guidance, which caps completeness, and it misses several natural trigger synonyms (sign in, login, SSO) that its own body's 'When to Use' section already contains.

Suggestions

Append a 'Use when...' clause to the description, e.g. 'Use when implementing or debugging Clerk authentication, sign-in/sign-up flows, organizations, or webhook-based user sync in a Next.js/React app.'

Include the natural trigger terms already listed in the body (sign in, sign up, SSO, multi-tenancy, user management) in the description itself so the frontmatter works as a standalone trigger surface.

Phrase capabilities as concrete actions (e.g. 'Protect routes with middleware, configure organizations, sync users via webhooks') to push specificity from area-listing toward comprehensive action coverage.

Dimension	Reasoning	Score
Specificity	The description lists several concrete areas — 'Clerk auth implementation, middleware, organizations, webhooks, and user sync' — going beyond naming the domain alone. It falls short of a 5 because it names topical areas rather than a comprehensive set of concrete actions, and short of the specificity of the top anchor's 'extract, fill, merge, convert' style.	4 / 5
Completeness	The 'what' is clear ('Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync'), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3; it is not a 2 because the 'what' is specific rather than vague.	3 / 5
Trigger Term Quality	'Clerk auth', 'middleware', 'organizations', and 'webhooks' are natural phrases users would say, giving good keyword coverage. Common variations a user might naturally say — 'sign in', 'login', 'SSO', 'multi-tenancy' — are absent (they only appear in the body, not the description), which keeps it below the comprehensive-synonym coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	'Clerk auth' names a specific vendor/product niche with distinct triggers, making it clearly distinguishable from generic authentication or other auth-provider skills. It matches the 'clear niche with distinct triggers; minimal conflict risk' anchor; a 4 would require some overlap with closely related skills, which the Clerk-specific framing avoids.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/clerk-auth/SKILL.md
Commit: 7b534bc

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