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

59%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

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 solid skill description with explicit trigger guidance and good natural language keywords. The main weakness is that capabilities are listed as categories rather than concrete actions, and some trigger terms are generic enough to potentially conflict with other authentication skills.

Suggestions

Convert category nouns to action verbs: 'Configure Clerk middleware, manage organizations, handle webhooks, sync users to database' instead of just listing areas.

Add more Clerk-specific trigger terms to reduce conflict risk: 'ClerkProvider', '@clerk/nextjs', 'Clerk dashboard', 'Clerk API keys'.

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 action verbs like 'configure', 'implement', 'sync'.	2 / 3
Completeness	Clearly answers both what (Clerk auth implementation patterns for middleware, organizations, webhooks, user sync) and when (explicit 'Use when:' clause with specific triggers).	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., Firebase Auth, Auth0). The Clerk-specific terms help but don't fully prevent overlap.	2 / 3
	Total	10 / 12 Passed

Implementation

37%

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

This skill content is essentially a hollow index file that provides no standalone value. While it's concise and has clear references to sub-skills, it lacks any actionable content, quick-start guidance, or workflow overview that would make it useful without immediately navigating elsewhere.

Suggestions

Add a Quick Start section with a minimal executable example showing basic Clerk setup (e.g., wrapping app with ClerkProvider)

Include a brief workflow overview explaining when to use each sub-skill and in what order for a typical implementation

Add at least one concrete code snippet demonstrating the most common Clerk pattern (e.g., protecting a route or accessing user data)

Dimension	Reasoning	Score
Conciseness	The content is extremely minimal with no unnecessary explanation or padding. It assumes Claude knows what Clerk is and provides only structural navigation.	3 / 3
Actionability	The skill body contains zero executable code, commands, or concrete guidance. It only lists links to sub-skills without any actionable content in the main file itself.	1 / 3
Workflow Clarity	There is no workflow, sequence, or process described. The content is purely a table of contents with no indication of how to use these modules together or in what order.	1 / 3
Progressive Disclosure	References to sub-skills are one level deep and clearly signaled, but there's no quick-start content or overview to orient the reader. The main skill is essentially empty, forcing users to navigate elsewhere for any useful information.	2 / 3
	Total	7 / 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: Dokhacgiakhoa/antigravity-ide
Commit: 332e58b

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