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 sub-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 token conversion, and OAuth provider reconfiguration when migrating 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 redirects', or 'migrate session tokens'. The action is singular and high-level. | 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 source providers (Auth0, Firebase, Supabase Auth, NextAuth), common phrases users would say ('migrate to clerk', 'switch to clerk', 'auth0 to clerk'), and the general concept of 'custom authentication solutions'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (migration TO Clerk specifically, FROM named providers). Unlikely to conflict with general auth skills, Clerk setup skills, or other migration skills due to the precise scoping. | 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 for each step and good error handling coverage. Its main weaknesses are the lack of explicit validation checkpoints between migration steps (critical for a destructive operation) and the monolithic structure that could benefit from splitting provider-specific content into separate files. The content is slightly verbose with redundant sections (Output, Overview) that restate what the steps already convey.
Suggestions
Integrate the verification script directly into the workflow as an explicit checkpoint (e.g., 'Step 2b: Verify import results before proceeding to Step 3') and add similar validation gates between other steps.
Split provider-specific export instructions (Auth0, NextAuth, Firebase, Supabase) into separate referenced files to reduce the main skill's length and improve progressive disclosure.
Remove the 'Output' section—it merely lists what the steps already produce—and trim the 'Overview' to avoid restating the skill's purpose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity—the 'Overview' section restates what the skill does, the 'Output' section is a redundant summary of what the steps already produce, and some comments are explanatory rather than essential. However, it mostly avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Provides fully executable TypeScript and bash code for each step—export scripts, import scripts with proper error handling and rate limiting, database reference updates, before/after code replacements, and verification scripts. All are copy-paste ready with real API calls. | 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. For a destructive migration operation, there should be explicit 'verify before proceeding' gates—e.g., validate export completeness before import, verify import results before updating DB references. The verification script exists but is in an 'Examples' section rather than integrated into the workflow. | 2 / 3 |
Progressive Disclosure | The skill links to external Clerk docs and references a 'clerk-prod-checklist' skill, which is good. However, the content is quite long (~200 lines) and could benefit from splitting provider-specific export instructions into separate files. The error handling table and verification script could also be referenced rather than inline. | 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
3e83543
- 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.