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".
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clerk-pack/skills/clerk-migration-deep-dive/SKILL.mdQuality
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 well-structured skill description with excellent trigger terms and completeness, clearly specifying both when to use it and what it does. Its main weakness is the lack of specific concrete actions beyond the high-level 'migrate' — it would benefit from listing specific migration tasks like data export, schema mapping, or session handling.
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Handles user data export, password hash migration, session configuration, and webhook setup when migrating from other auth providers to Clerk.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (authentication migration to Clerk) and the general action (migrate), but doesn't list specific concrete actions like 'export user data', 'map user schemas', 'configure SSO', or 'handle password hashing migration'. | 2 / 3 |
Completeness | Clearly answers both 'what' (migrate from other auth providers to Clerk) and 'when' (explicit 'Use when' clause listing specific providers and a 'Trigger with phrases' section providing exact trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including specific provider names (Auth0, Firebase, Supabase Auth, NextAuth), common phrases users would say ('migrate to clerk', 'switch to clerk', 'auth0 to clerk'), and the general term 'clerk migration'. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — specifically about migrating TO Clerk from named providers. Unlikely to conflict with general auth skills, Clerk setup skills, or other migration skills due to the specific directional migration focus and named source providers. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable migration guide with executable code for each step of the process. Its main weaknesses are the monolithic structure (all code inline with no bundle files for progressive disclosure) and missing explicit validation checkpoints between critical steps like import and database reference updates. The error handling table and verification script are valuable additions but could be better integrated into the workflow.
Suggestions
Add explicit validation checkpoints between steps — e.g., after Step 2, require running the verification script and confirming import counts before proceeding to Step 3 (database updates).
Extract the lengthy import script, export scripts, and verification script into separate bundle files (e.g., scripts/import-to-clerk.ts) and reference them from SKILL.md to improve progressive disclosure.
Add a rollback procedure section — the code preserves legacyAuthId but never explains how to actually roll back if the migration fails.
Move the verification script from the 'Examples' section into the main workflow as an explicit Step (e.g., between Steps 3 and 4) to enforce validation before code replacement.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary padding like the 'Overview' paragraph restating what the skill does, the 'Output' section listing what was already shown, and the 'Prerequisites' section with obvious items. The code examples themselves are well-scoped, but the overall document could be tightened by ~20%. | 2 / 3 |
Actionability | Excellent executable code throughout — complete TypeScript scripts for export, import with rate limiting, database reference updates, and verification. The Auth0 curl command, NextAuth Prisma export, and Clerk import scripts are all copy-paste ready with proper error handling and typed interfaces. | 3 / 3 |
Workflow Clarity | The 6-step sequence is clearly laid out and logically ordered, but there are validation gaps. The verification script exists as an afterthought in 'Examples' rather than as an explicit checkpoint between steps. There's no explicit 'validate before proceeding' gate between import (Step 2) and database update (Step 3), and no rollback procedure despite keeping legacyAuthId. | 2 / 3 |
Progressive Disclosure | The document is quite long (~200+ lines of inline code) with no bundle files to offload detail into. The provider-specific export scripts, the full import script, and the parallel running bridge could each be separate referenced files. The Resources section links to external docs but internal structure is monolithic. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 |
Total | 9 / 11 Passed | |
- Commit
0c3a6ad
- Reviewed
Table of Contents
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.