CtrlK
BlogDocsLog inGet started
Tessl Logo

auth0-migration

Use when migrating users or authentication from another provider (Firebase, Cognito, Supabase, Clerk, or custom auth) to Auth0. Covers bulk user import, gradual migration strategies, and updating JWT validation — use even if the user says "switch our auth to Auth0" or "move our users to Auth0".

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-structured migration skill: actionable inline examples, clear sequencing, and excellent progressive disclosure to two real reference files. The main weaknesses are duplicated SDK/reference link listings (token waste) and the absence of an inline post-import verification checkpoint for a batch operation.

Suggestions

Add an inline 'Verify the import' checkpoint after Step 2 (e.g., check user count and test a login) rather than relegating all verification to the reference, since bulk import is a batch operation.

Remove the duplicate SDK-skills list — keep it in either Step 3 or the Related Skills section, not both — to reclaim tokens.

Drop or condense the closing 'Reference Documentation' section, which re-lists anchors already linked inline in Steps 1–4.

DimensionReasoningScore

Conciseness

Mostly efficient (compact tables for provider detection and common issues), but the SDK skills list is duplicated between Step 3 and the "Related Skills" section, and reference links are restated in the closing "Reference Documentation" section — tightening would remove redundant tokens.

2 / 3

Actionability

Provides executable, copy-paste-ready guidance inline — the `auth0 api post jobs/users-imports` CLI command and the TypeScript parallel-auth `getUser` snippet — plus concrete key-difference facts, not vague direction.

3 / 3

Workflow Clarity

A clear Step 0→4 sequence and a 4-phase gradual-migration plan exist, but this batch user-import workflow has no inline verification checkpoint; per the batch-operation guideline, validation living only in the reference caps this at 2.

2 / 3

Progressive Disclosure

The body is a well-signaled overview pointing one level deep to references/user-import.md and references/code-patterns.md via specific anchor links, all of which resolve to real sections, with content appropriately split out.

3 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete capabilities, gives explicit "Use when" triggers with natural user phrasings, names source providers for distinctiveness, and cleanly separates migration-to-Auth0 from fresh setup. No meaningful gaps relative to the rubric anchors.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Covers bulk user import, gradual migration strategies, and updating JWT validation" — rather than vague language, matching the multi-action anchor.

3 / 3

Completeness

Explicitly answers both what (bulk import, gradual migration, JWT validation) and when ("Use when migrating users or authentication... to Auth0"), satisfying the what-AND-when anchor.

3 / 3

Trigger Term Quality

Includes natural phrasings users would say ("switch our auth to Auth0", "move our users to Auth0") plus named providers (Firebase, Cognito, Supabase, Clerk), giving broad natural-term coverage.

3 / 3

Distinctiveness Conflict Risk

Scopes to migration TO Auth0 from named legacy providers with distinct triggers, making it unlikely to fire for unrelated Auth0 skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
auth0/agent-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.