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

44%

Does it follow best practices?

Impact

—

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

Content

14%

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

This skill is essentially an empty table of contents with three links to sub-skill files that don't exist in the bundle. It provides no actionable content, no code examples, no workflow guidance, and no meaningful overview of Clerk authentication patterns. To be useful, it needs substantial inline content or verified sub-skill files with a proper overview.

Suggestions

Add a quick-start section with a minimal executable example of Clerk setup (e.g., ClerkProvider wrapping, basic middleware config) so the skill is useful even without sub-files.

Provide a brief description of what each sub-skill covers and when to use it, rather than just bare links.

Include a workflow sequence explaining the order of implementation (setup → middleware → server components) with validation steps.

Either include the referenced sub-skill bundle files or inline the critical content so the skill is self-contained and actionable.

Dimension	Reasoning	Score
Conciseness	The content is very short, which is efficient, but it's so sparse that it's essentially just a table of contents with no substantive content at all. The '## Patterns' heading is empty and wastes a token. The '🧠 Knowledge Modules (Fractal Skills)' heading is unnecessary jargon.	2 / 3
Actionability	There is zero actionable content—no code, no commands, no concrete guidance. The entire skill body is just three links to sub-skill files with no inline instructions, examples, or quick-start content.	1 / 3
Workflow Clarity	There is no workflow described at all. No steps, no sequence, no validation checkpoints. The skill provides no guidance on how to implement Clerk authentication or in what order to approach the sub-skills.	1 / 3
Progressive Disclosure	While it references sub-skill files (good in principle), no bundle files were provided, so the references lead nowhere. The SKILL.md itself contains no overview, no quick-start content, and no context about what each sub-skill covers—it's an empty shell rather than a useful overview with well-signaled references.	1 / 3
	Total	5 / 12 Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is functional and well-structured with a clear 'Use when' clause and a distinct niche around Clerk authentication. Its main weaknesses are the use of vague framing ('expert patterns for') instead of concrete action verbs, and incomplete trigger term coverage missing common synonyms like 'login' and 'protected routes'.

Suggestions

Replace 'Expert patterns for Clerk auth implementation' with concrete actions like 'Configures Clerk authentication, sets up auth middleware, handles organization management, processes webhooks, and syncs user data'.

Expand trigger terms to include common variations: 'login', 'logout', 'protected routes', 'session management', 'ClerkProvider', '@clerk/nextjs'.

Dimension	Reasoning	Score
Specificity	Names the domain (Clerk auth) and lists several areas (middleware, organizations, webhooks, user sync), but uses 'expert patterns for' which is somewhat vague rather than listing concrete actions like 'configure middleware', 'set up webhook handlers', or 'sync user data'.	2 / 3
Completeness	Clearly answers both 'what' (Clerk auth implementation covering middleware, organizations, webhooks, user sync) and 'when' with an explicit 'Use when:' clause listing trigger scenarios.	3 / 3
Trigger Term Quality	Includes useful trigger terms like 'authentication', 'clerk auth', 'sign in', 'sign up', but misses common variations like 'login', 'logout', 'session management', 'protected routes', 'auth middleware', or 'Clerk SDK'.	2 / 3
Distinctiveness Conflict Risk	The specificity to 'Clerk' as an auth provider creates a clear niche that is unlikely to conflict with generic auth skills or other auth provider skills. The mention of Clerk-specific features like organizations and webhooks further distinguishes it.	3 / 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: Dokhacgiakhoa/antigravity-ide
Commit: c4a059b

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.