clerk-auth

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

Quality

52%

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

51%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 SKILL.md is a well-structured, lean routing document that exemplifies good progressive disclosure by delegating detail to a single real reference file, but the body itself carries almost no actionable or sequenced execution guidance, relying entirely on the referenced guide.

Suggestions

Add a brief inline quick-start or minimal executable example (e.g. a sample middleware snippet) so the body is actionable without forcing a full reference load for simple cases.

Surface a short numbered workflow with at least one explicit validation checkpoint inline (e.g. verify webhook signature before persisting), even if the guide holds the full procedure.

Trim the repetitive 'User mentions or implies:' prefix on each trigger bullet to reduce padding.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; the only padding is the repeated overview line and the verbose 'Detailed Guide' paragraph and the repetitive 'User mentions or implies:' prefix on every trigger bullet, which keep it just below fully lean.	4 / 5
Actionability	The body itself provides only high-level routing ('Read the detailed guide before executing this skill') and a when-to-use list, with no concrete code, commands, or implementation steps inline — the specific steps to execute are delegated entirely to the reference file.	2 / 5
Workflow Clarity	There is only a rough implicit sequence (read the guide, then execute) and no inline validation checkpoints; while the body says to treat the guide's validation requirements as mandatory, the actual checkpoints live in the referenced file, leaving gaps and absent inline validation for auth/webhook operations.	2 / 5
Progressive Disclosure	The body is a clear, concise overview that points to a single one-level-deep reference (references/detailed-guide.md, which exists as a real 20KB file) via a well-signaled markdown link, with content appropriately split and easy to navigate.	5 / 5
	Total	13 / 20 Passed

Description

53%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 clearly conveys what the skill covers and targets a specific product niche, but it omits an explicit 'Use when' trigger clause and lacks natural synonym keywords users would say, capping completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user mentions Clerk, sign-in, sign-up, login, organizations, or webhooks.'

Include natural synonym keywords users actually say ('login', 'sign in', 'sign up', 'authentication') alongside 'Clerk auth'.

Reframe topic areas as concrete actions where possible (e.g. 'configure middleware', 'sync users', 'verify webhooks') to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the Clerk domain plus several specific sub-areas ('middleware, organizations, webhooks, and user sync'), but these are topic areas rather than concrete actions like 'extract' or 'fill', so it sits at the domain-plus-actions anchor rather than the comprehensive-actions anchor above.	3 / 5
Completeness	The 'what' is clearly stated ('Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	It includes the strong natural term 'Clerk auth' plus 'organizations' and 'webhooks', but misses common variations users actually say such as 'login', 'sign in', 'sign up', and 'authentication' spelled out, so it has relevant but incomplete keyword coverage.	3 / 5
Distinctiveness Conflict Risk	'Clerk auth' names a specific commercial product giving it a clear niche with minimal conflict risk, though it could still overlap with general auth or NextAuth skills, placing it just below the fully-distinct anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/clerk-auth/SKILL.md
Commit: b1aebac

Reviewed: ~18 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.