clerk-auth

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with concrete, file-annotated code and useful anti-pattern/validation sections, but it is a large monolithic file with internal redundancy and no progressive disclosure to bundled references, and it lacks sequenced workflows with validation checkpoints. Splitting per-topic detail into reference files and de-duplicating repeated components would improve conciseness and disclosure.

Suggestions

Move large per-topic code references (e.g., webhook sync, organizations) into bundled reference files under references/ and link to them from a leaner SKILL.md overview to improve progressive disclosure and conciseness.

Remove redundant redefinitions (e.g., Header.tsx and DashboardPage defined in multiple sections) and clarify that the 'Advanced: Role-based protection' middleware block is an alternative, not a second default export in the same file.

Add a short sequenced setup workflow with explicit validation checkpoints (e.g., verify env vars → mount provider → confirm middleware matcher → test a protected route) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly efficient per-section (brief intro, code, anti-patterns, references) but the ~835-line body carries redundancy — Header.tsx and DashboardPage are redefined across sections and two 'export default clerkMiddleware' blocks appear — that could be tightened; not a 3 because of this unnecessary repetition, not a 1 because it avoids explaining concepts Claude already knows.	2 / 3
Actionability	Every pattern ships concrete, copy-paste-ready code with explicit file paths (app/layout.tsx, middleware.ts, webhook route with full svix verification, API routes, client hooks); not below 3 because guidance is overwhelmingly executable and specific rather than pseudocode or abstract.	3 / 3
Workflow Clarity	Content is consistently organized by topic with per-section structure, but Clerk setup is not presented as a sequenced multi-step workflow and there are no explicit validation checkpoints or validate→fix→retry feedback loops for webhook/batch operations, capping it at 2; not a 1 because the pattern sequence within each section is clear.	2 / 3
Progressive Disclosure	No bundle files exist and all 800+ lines live inline in a single SKILL.md; sections are well-organized so it is not a monolithic wall (not a 1), but content that could be split into reference files is inline with only external URLs as references, matching anchor 2.	2 / 3
	Total	9 / 12 Passed

Description

72%

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 clear and distinctively Clerk-scoped with good natural trigger terms, but it reads as a topic list rather than concrete actions and omits any explicit 'use when' trigger guidance, capping completeness. Adding an explicit trigger clause and action verbs would raise specificity and completeness.

Suggestions

Add a 'Use when…' clause listing explicit triggers (e.g., 'Use when adding Clerk authentication, sign-in/sign-up, middleware route protection, organizations, or webhook user sync').

Reframe the capability list with concrete action verbs (e.g., 'Implement Clerk auth, protect routes with middleware, sync users via webhooks') to lift specificity from a noun list to concrete actions.

Include common natural variations such as 'login', 'sign in/sign up', and 'authentication' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Clerk domain and several sub-areas ('middleware, organizations, webhooks, and user sync') but leads with 'Expert patterns for' and a noun list rather than concrete action verbs, matching anchor 2; not a 3 because no discrete actions like implement/protect/sync are stated as verbs.	2 / 3
Completeness	Clearly states what the skill covers but has no 'Use when…' or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2; not a 3 because the 'when' is entirely missing from the description.	2 / 3
Trigger Term Quality	Contains natural developer terms a user would actually say — 'Clerk auth', 'middleware', 'organizations', 'webhooks', 'user sync' — giving good coverage; not below 3 because these are domain-natural and specific rather than jargon or generic.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to a distinct niche ('Clerk auth implementation…') unlikely to trigger for unrelated skills; not below 3 because Clerk-specificity plus the enumerated sub-areas make overlap with generic auth skills unlikely.	3 / 3
	Total	10 / 12 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
Commit: 5e71bba

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