clerk-auth

Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/clerk-auth/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

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

The body is a comprehensive, actionable reference with code and anti-patterns per pattern, but it is monolithic with no progressive file split and lacks explicit validation feedback loops for destructive operations. Splitting reference material into bundle files and adding validation checkpoints would improve it.

Suggestions

Move the per-pattern API code and Prisma schema into separate reference files (e.g., references/webhooks.md, references/middleware.md) and link from SKILL.md, rather than inlining ~840 lines.

Add explicit validation checkpoints for destructive/batch paths (e.g., verify svix signature → on failure log and 400 → only then upsert; test middleware matcher against known routes before deploying).

Remove the duplicated `export default clerkMiddleware` block (lines ~133 and ~150) and present the advanced role-based variant as a clearly labeled alternative to avoid non-executable code.

Dimension	Reasoning	Score
Conciseness	Mostly lean per-pattern intros followed directly by code with little concept re-explanation; minor duplication (Header.tsx appears twice) keeps it just below fully efficient.	4 / 5
Actionability	Provides extensive copy-paste-ready code across setup, middleware, server/client auth, orgs, and webhooks, with minor gaps such as two `export default` declarations in one middleware block that is not executable as written.	4 / 5
Workflow Clarity	Patterns are clearly grouped and each has Anti_patterns, but there are no explicit validate→fix→retry checkpoints for destructive operations like webhook DB writes and role-based access, capping clarity at 3.	3 / 5
Progressive Disclosure	Structure is well-sectioned but ~840 lines of patterns and code are all inlined in SKILL.md with no bundle files (references/scripts/assets absent) and only external URL references, so content that belongs in separate files is not split out.	3 / 5
	Total	14 / 20 Passed

Description

58%Weight 40%Scale 1-5

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 specific and well-scoped to Clerk auth, but it lacks an explicit "Use when..." trigger clause and some natural user-facing trigger terms. Adding trigger guidance and synonyms would raise completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause naming concrete user triggers (e.g., 'Use when adding Clerk auth, sign-in/sign-up, middleware, organizations, or user sync webhooks').

Add natural synonyms users say in the description itself — 'sign in', 'sign up', 'SSO', 'multi-tenancy' — rather than only in the body's When-to-Use list.

Lead with action verbs (e.g., 'Implements Clerk auth...') to convert the noun-list phrasing into concrete stated actions.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities — "middleware, organizations, webhooks, and user sync" — but is a touch below comprehensive coverage, lacking explicit action verbs per capability.	4 / 5
Completeness	The description gives a clear "what" but no "Use when..." clause, so per rubric guidance a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant keywords ("Clerk auth", "middleware", "organizations", "webhooks") but the description field itself omits natural variations users say ("sign in", "sign up", "sso", "multi-tenancy") that appear only in the body.	3 / 5
Distinctiveness Conflict Risk	Clearly scoped to Clerk-specific auth with named subsystems, making it largely distinct from generic auth skills with only minor overlap risk.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (844 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/clerk-auth/SKILL.md
Commit: 1f67c44

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