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".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 user data export, password hash handling, or session migration.
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 | The description names the domain (authentication migration to Clerk) and the action (migrate), but doesn't list specific concrete actions like 'export user data', 'map user schemas', 'configure SSO redirects', or 'handle password hash migration'. It stays at a high level of 'migrate from X to Clerk'. | 2 / 3 |
Completeness | Clearly answers both 'what' (migrate from other auth providers to Clerk) and 'when' (explicit 'Use when' clause listing specific providers, plus a 'Trigger with phrases' section providing exact user phrases). Both components are explicitly stated. | 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', 'clerk migration'), and provider-specific combinations ('auth0 to clerk', 'firebase auth to clerk'). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Clerk' as the target and specific source providers (Auth0, Firebase, Supabase Auth, NextAuth) creates a very clear niche. Unlikely to conflict with general authentication skills or other migration skills. | 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, actionable migration guide with executable code examples covering the full migration lifecycle from multiple auth providers to Clerk. Its main weaknesses are the monolithic structure (all providers inline rather than split into separate files) and the lack of explicit validation checkpoints integrated into the workflow steps. The content could also be tightened by removing redundant sections like the Output summary and some obvious prerequisites.
Suggestions
Integrate the verification script as a mandatory checkpoint after Step 2 (import) and Step 3 (DB update) rather than relegating it to an 'Examples' section—add explicit 'validate before proceeding' gates.
Split provider-specific export instructions into separate referenced files (e.g., auth0-export.md, nextauth-export.md) to reduce the monolithic size and improve progressive disclosure.
Remove the 'Output' section which merely lists what the steps already produce, and trim the 'Overview' paragraph that restates the skill description.
| 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 like 'Git repository with clean working state'. The code examples themselves are well-sized but the overall document could be tightened. | 2 / 3 |
Actionability | Provides fully executable TypeScript and bash code for each migration step—export scripts, import scripts with error handling and rate limiting, database reference updates, before/after code replacements, and a verification script. All examples are copy-paste ready with real API calls and proper types. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (export → import → update DB → replace code → parallel run → cleanup), but there are no explicit validation checkpoints between steps. The verification script exists but is in an 'Examples' section rather than integrated as a mandatory checkpoint after Step 2 or Step 3. For a destructive batch operation like user migration, missing inline validation gates caps this at 2. | 2 / 3 |
Progressive Disclosure | The document is quite long and monolithic—all provider-specific export instructions, import scripts, code migration examples, and verification are inline. Provider-specific sections (Auth0, Firebase, Supabase, NextAuth) could be split into separate files. The external resource links at the end are helpful, but there are no bundle files to offload detailed content to. | 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
3a2d27d
- 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.