clerk-auth
tessl i github:sickn33/antigravity-awesome-skills --skill clerk-authExpert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync Use when: adding authentication, clerk auth, user authentication, sign in, sign up.
Validation
69%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Implementation
27%This skill provides a structural outline for Clerk authentication but lacks the concrete, executable guidance needed to be actionable. The Sharp Edges table is entirely placeholder content, and there are no code examples despite describing code-heavy tasks like middleware setup and server component authentication. The skill reads more like a table of contents than actionable instructions.
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, or remove it entirely
Add explicit file references for detailed documentation (e.g., 'See [MIDDLEWARE.md](MIDDLEWARE.md) for advanced route matching patterns')
Include a quick-start workflow with numbered steps and validation checkpoints (e.g., 'Verify middleware is working by checking /api/auth routes')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief and avoids excessive explanation of basic concepts, but the Sharp Edges table is entirely placeholder content ('Issue', 'See docs') which wastes tokens without providing value. | 2 / 3 |
Actionability | The skill describes concepts and lists key components/functions but provides no executable code examples. Statements like 'Complete Clerk setup' and 'Protect routes using clerkMiddleware' are vague without actual implementation code. | 1 / 3 |
Workflow Clarity | There's an implicit sequence (setup -> middleware -> server components) and some best practices are listed, but no explicit step-by-step workflow with validation checkpoints for the setup process. | 2 / 3 |
Progressive Disclosure | The content is a monolithic overview with no references to detailed documentation files. The Sharp Edges table says 'See docs' but provides no actual links or file references for navigation. | 1 / 3 |
Total | 6 / 12 Passed |
Activation
82%This is a reasonably well-structured skill description with a clear 'Use when' clause and good trigger terms. The main weakness is that the capabilities section lists feature areas 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 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 |
Reviewed
Table of Contents
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.