clerk-migration-deep-dive

Migrate from other authentication providers to Clerk. Use when migrating from Auth0, Firebase, Supabase Auth, NextAuth, or custom authentication solutions. Trigger with phrases like "migrate to clerk", "clerk migration", "switch to clerk", "auth0 to clerk", "firebase auth to clerk".

Quality

77%

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 ./plugins/saas-packs/clerk-pack/skills/clerk-migration-deep-dive/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The content is highly actionable with executable code across a well-sequenced migration workflow, but it is verbose for a SKILL.md and fails to surface its own bundled reference file. Validation checkpoints are present but disconnected from the main step flow.

Suggestions

Move the long per-provider code blocks into references/implementation-guide.md and link to it from each step, keeping SKILL.md as a lean overview with the key command per step.

Promote the migration verification script from the Examples section into an explicit 'Validate' checkpoint between Step 3 and Step 4, with a fix-and-retry loop for unmapped users.

Tighten code blocks by dropping console.log/summary-object boilerplate and removing the commented-out legacy fallback in the parallel-running step.

Dimension	Reasoning	Score
Conciseness	The body is action-dense with no concept-explanation fluff, but at ~250 lines it includes tighten-able padding (console.log lines, summary-object construction, commented-out legacy fallback) that keeps it short of the 'every token earns its place' level 3.	2 / 3
Actionability	Every step ships concrete, copy-paste-ready curl/TypeScript/bash (Auth0 export, Clerk import, DB reference update, NextAuth-to-Clerk swaps, middleware, cleanup), matching the 'fully executable code/commands' anchor despite minor scaffolding gaps like undefined db/fs imports.	3 / 3
Workflow Clarity	Steps 1-6 are clearly sequenced, but for a batch and destructive operation the validation/verification lives in a separate Examples section rather than as inline checkpoints, so feedback loops are implicit — capping it at level 2 per the batch/destructive guideline.	2 / 3
Progressive Disclosure	Section structure is reasonable, but the bundled references/implementation-guide.md is never linked or signaled from the body and detailed code is inlined in SKILL.md that could live in that reference, fitting the 'references present but not clearly signaled; content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 strong: it clearly states what the skill does and when to use it, includes natural trigger phrases, and occupies a distinct niche. Its only weakness is that it names a single action rather than enumerating multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	It names the domain and a single concrete action ("Migrate from other authentication providers to Clerk") plus specific source providers, but does not list multiple distinct concrete actions, matching the 'names domain and some actions' anchor rather than the multi-action level 3.	2 / 3
Completeness	It explicitly answers both what (migrate auth providers to Clerk) and when via an explicit "Use when migrating from..." clause, satisfying the level-3 'both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	It provides five natural trigger phrases ("migrate to clerk", "clerk migration", "switch to clerk", "auth0 to clerk", "firebase auth to clerk") that a user would plausibly say, giving good coverage across the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The Clerk-specific auth-migration niche with distinct provider-named triggers is unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/clerk-pack/skills/clerk-migration-deep-dive/SKILL.md
Commit: 4c47e33

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.