clerk-auth

Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync Use when: adding authentication, clerk auth, user authentication, sign in, sign up.

Quality

48%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/clerk-auth/SKILL.md

The canonical home for this skill is clerk-auth in sickn33/agentic-awesome-skills

Quality

Content

14%Scale 1-3

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

This skill provides a high-level outline of Clerk authentication concepts but fails to deliver actionable guidance. It lacks executable code examples, clear implementation workflows, and meaningful references. The sharp edges table contains placeholder content that provides no value.

Suggestions

Add complete, executable code examples for each pattern (ClerkProvider setup, middleware.ts configuration, auth() usage in Server Components)

Replace the placeholder sharp edges table with actual issues and solutions, or remove it entirely

Provide step-by-step implementation workflow with validation steps (e.g., 'Test auth by visiting /dashboard - should redirect to sign-in')

Either link to actual documentation files for advanced topics or inline the essential information

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes some unnecessary explanatory text like 'Key components' and 'Key functions' lists that describe what Claude already knows about Clerk. The sharp edges table is placeholder content with no actual value.	2 / 3
Actionability	No executable code examples are provided despite describing code-heavy tasks like middleware setup, ClerkProvider configuration, and auth() usage. The content describes what to do abstractly ('Use createRouteMatcher for route groups') without showing how.	1 / 3
Workflow Clarity	No clear step-by-step sequences for setup or implementation. The sections describe concepts but don't provide ordered workflows for actually implementing Clerk auth. No validation checkpoints for verifying auth is working.	1 / 3
Progressive Disclosure	The sharp edges table references 'See docs' repeatedly without providing actual links or file references. No clear navigation to detailed implementation guides or examples. The structure exists but leads nowhere useful.	1 / 3
	Total	5 / 12 Passed

Description

82%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.

This is a solid skill description with good completeness and trigger term coverage. The explicit 'Use when:' clause with natural user terms is a strength. The main weakness is that the capabilities section lists categories rather than specific actions, and some trigger terms are generic enough to potentially conflict with other authentication skills.

Suggestions

Replace category nouns with specific action verbs: 'Configure Clerk middleware, set up organizations, handle webhooks, sync users to database' instead of just listing 'middleware, organizations, webhooks'

Add Clerk-specific trigger terms to reduce conflict risk: 'clerk middleware', 'clerk organizations', '@clerk/nextjs', 'ClerkProvider'

Dimension	Reasoning	Score
Specificity	Names the domain (Clerk auth) and lists several areas (middleware, organizations, webhooks, user sync) but these are categories rather than concrete actions. Missing specific verbs like 'configure', 'implement', 'sync users to database'.	2 / 3
Completeness	Clearly answers both what (Clerk auth implementation patterns for middleware, organizations, webhooks, user sync) and when (explicit 'Use when:' clause with trigger terms). Has the required explicit trigger guidance.	3 / 3
Trigger Term Quality	Good coverage of natural terms users would say: 'authentication', 'clerk auth', 'user authentication', 'sign in', 'sign up'. These are common phrases users naturally use when needing auth help.	3 / 3
Distinctiveness Conflict Risk	While 'Clerk' is specific, generic terms like 'authentication', 'sign in', 'sign up' could conflict with other auth-related skills (e.g., NextAuth, Auth0, Firebase Auth). The Clerk-specific terms help but don't fully prevent overlap.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/clerk-auth/SKILL.md
Commit: 7520423

Reviewed: ~15 hours 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.