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

63%

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

89%

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 keyword coverage. The main weakness is that capabilities are listed as categories (middleware, organizations) rather than concrete actions (configure middleware, sync users). The Clerk-specific focus provides excellent distinctiveness.

Suggestions

Convert category nouns to action phrases: 'configure middleware, manage organizations, handle webhooks, sync users' instead of just listing 'middleware, organizations, webhooks, user sync'.

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	Clearly scoped to Clerk specifically, not generic auth. The mention of 'Clerk' and Clerk-specific features (organizations, webhooks, user sync) creates a distinct niche unlikely to conflict with other auth skills.	3 / 3
	Total	11 / 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 is essentially a stub or index file with no substantive content. While it's concise, it fails to provide any actionable guidance, workflow clarity, or meaningful overview. A skill file should contain at least a quick-start section or summary of when/how to use the linked resources, not just be a list of links.

Suggestions

Add a Quick Start section with a minimal executable code example for basic Clerk setup

Include a brief decision guide explaining when to use each sub-skill (e.g., 'Start with Next.js App Router Setup for new projects')

Add at least one concrete code snippet showing the most common Clerk authentication pattern

Provide a workflow overview showing the typical sequence: setup → middleware → server components

Dimension	Reasoning	Score
Conciseness	The content is extremely minimal with no unnecessary explanation or padding. Every line serves a purpose - title, section header, and links to sub-skills.	3 / 3
Actionability	The skill provides no concrete guidance, code, or commands. It's purely a table of contents with links to other files, offering no executable or actionable content in the main skill file itself.	1 / 3
Workflow Clarity	There is no workflow, sequence, or process described. The content is just a list of links with no indication of order, dependencies, or when to use each sub-skill.	1 / 3
Progressive Disclosure	The skill attempts progressive disclosure by linking to sub-skills, but the main file provides zero overview or quick-start content. It's essentially an empty shell that forces 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: 3395991

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