CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

77%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/clerk-pack/skills/clerk-migration-deep-dive/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 highly actionable migration guide with executable code for each step and good error handling coverage. Its main weaknesses are the monolithic structure (all provider paths inline rather than split into separate files) and the lack of explicit validation checkpoints between migration steps, which is important for a destructive operation like auth migration. The verification script should be integrated into the workflow rather than relegated to an Examples section.

Suggestions

Integrate the verification script as an explicit checkpoint between Steps 2 and 3 (e.g., 'Run verify-migration.ts and confirm all users imported before updating database references').

Add explicit validation gates: after each major step, include a '**Verify before continuing**' checkpoint with specific success criteria (e.g., 'migration-results.json shows 0 errors').

Split provider-specific export instructions into separate files (e.g., auth0-migration.md, nextauth-migration.md) and keep SKILL.md as a concise overview with links to each provider path.

Remove the Overview paragraph and Prerequisites items that Claude can infer (e.g., 'Git repository with clean working state') to improve conciseness.

DimensionReasoningScore

Conciseness

The skill is fairly long (~200+ lines) with some unnecessary elements like the Overview paragraph explaining what the guide covers (Claude can infer this), and the Prerequisites section includes generic advice like 'Git repository with clean working state.' However, the code examples themselves are dense and useful, and the error handling table is efficient.

2 / 3

Actionability

The skill 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 a verification script. These are copy-paste ready with real API calls and concrete patterns.

3 / 3

Workflow Clarity

The 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., after Step 2, 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 content is a monolithic document with all migration paths inline. The Auth0, NextAuth, Firebase, and Supabase paths could be split into separate files with the SKILL.md serving as an overview. The Resources section references external docs but doesn't link to any bundle files. For a skill this long covering multiple providers, better splitting would improve navigation.

2 / 3

Total

9

/

12

Passed

Description

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 that the 'what' portion is somewhat high-level — it says 'migrate' but doesn't enumerate the specific sub-tasks involved in a migration (e.g., user data export, schema mapping, session handling). Overall it's a strong description that would perform well in skill selection.

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.'

DimensionReasoningScore

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', etc. 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 concrete 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 concept of custom authentication solutions.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — the combination of 'Clerk' as the target platform and specific source providers (Auth0, Firebase, Supabase Auth, NextAuth) creates a very clear niche that is unlikely to conflict with other skills.

3 / 3

Total

11

/

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.