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.

Install with Tessl CLI

npx tessl i github:sickn33/antigravity-awesome-skills --skill clerk-auth

What are skills?

0.98x

Quality

48%

Does it follow best practices?

Impact

98%

0.98x

Average score across 6 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/clerk-auth/SKILL.md

SKILL.md

Review

Evals

Discovery

82%

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 reasonably well-structured skill description with explicit 'Use when' triggers and good natural language keywords. The main weakness is that the capabilities section lists feature areas rather than concrete 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 feature areas.

Add Clerk-specific trigger terms to reduce conflict risk: 'clerk middleware', 'clerk organizations', '@clerk/nextjs', 'clerk webhooks' to better distinguish from other auth providers.

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

Implementation

14%

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. The complete absence of code examples for a code-heavy integration task, combined with placeholder content in the Sharp Edges table, makes this skill largely unusable. The description promises coverage of webhooks, organizations, and user sync, but the content doesn't address these topics.

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 specific solutions, not just 'See docs'

Add coverage for webhooks, organizations, and user sync as promised in the skill description

Include a step-by-step setup workflow with validation checkpoints (e.g., 'Test auth by visiting /api/auth/me and confirming userId is returned')

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. The Sharp Edges table is placeholder content with no actual value.	2 / 3
Actionability	No executable code examples provided despite describing code-heavy tasks like middleware setup, ClerkProvider configuration, and auth() usage. All guidance is abstract descriptions rather than copy-paste ready implementations.	1 / 3
Workflow Clarity	No clear step-by-step sequences for setup or implementation. The Sharp Edges table contains only placeholder 'Issue' and 'See docs' entries with no actual guidance. No validation checkpoints for middleware or auth configuration.	1 / 3
Progressive Disclosure	All content is in a single file with no references to detailed documentation. The 'See docs' references in the table are vague and don't point to specific files. No clear navigation structure for advanced topics like webhooks or user sync mentioned in the description.	1 / 3
	Total	5 / 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

Reviewed: about 18 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.