Name: auth0-mfa
Rating: 70.39999999999999 (1 reviews)
Author: auth0

auth0-mfa

Use when adding MFA or step-up authentication to an app — requiring users to verify with a second factor (TOTP, SMS, passkey, push) for login or before a sensitive action. Also use for adaptive/risk-based MFA or compliance requirements like HIPAA or PCI-DSS, even if the user just says "add two-factor auth" or "require MFA before this action".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

The content is actionable and well-structured with clean progressive disclosure to real reference files, but it loses points for restating basic MFA concepts Claude already knows and for omitting validation checkpoints in the MFA-enabling workflow.

Suggestions

Remove or shrink the "### What is MFA?" section and other definitional lines (e.g. the step-up explanation) since Claude already knows these concepts; keep only Auth0-specific mechanics.

Add an explicit validation step after enabling factors (e.g. re-run `auth0 api get "guardian/factors"` to confirm the factor is enabled) with a fix-and-retry loop, raising workflow clarity.

Tighten the Overview tables and prose so every remaining token earns its place, eliminating the residual unnecessary explanation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tables and runnable commands, but the "### What is MFA?" paragraph and definitional lines like "Step-up auth requires MFA for sensitive operations without requiring it for every login" explain concepts Claude already knows, so it is not the lean 3 yet is far from verbose padding.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands such as `auth0 api put "guardian/factors/otp" --data '{"enabled": true}'` and the concrete `acr_values` parameter, matching the anchor for fully executable code/commands.	3 / 3
Workflow Clarity	Steps are sequenced (Step 1 enable, Step 2 implement step-up) but lack explicit validation checkpoints or error-recovery loops after enabling factors, so it sits at the "steps listed but validation gaps" anchor rather than the checkpointed 3.	2 / 3
Progressive Disclosure	The body is a clear overview with well-signaled one-level-deep references to existing files (examples.md, backend.md, advanced.md, api.md), each containing substantial real content with no nested re-references, matching the anchor for clear overview with properly split content and easy navigation.	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.

The description is strong: it names concrete factors and actions, supplies explicit "Use when" triggers including colloquial phrasings, and occupies a distinct MFA/step-up niche. The only minor weakness is the absence of the vendor name "Auth0", which slightly raises collision risk with a hypothetical non-Auth0 MFA skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and named factors — "adding MFA or step-up authentication", "requiring users to verify with a second factor (TOTP, SMS, passkey, push)", "adaptive/risk-based MFA" — matching the anchor for listing multiple specific concrete actions rather than the partial coverage of a 2.	3 / 3
Completeness	Explicitly answers both what (MFA/step-up/adaptive/compliance) and when via a clear "Use when..." clause plus additional triggers, satisfying the anchor for clearly answering both what AND when.	3 / 3
Trigger Term Quality	Includes natural user phrases such as "add two-factor auth", "require MFA before this action", and "step-up authentication", giving good coverage of colloquial and technical variations rather than only some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	Targets a distinct MFA/step-up niche with specific triggers (adaptive/risk-based MFA, HIPAA/PCI-DSS compliance) unlikely to fire for unrelated skills; it is not a 2 because the triggers carve a clear niche rather than a generic overlap.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: auth0/agent-skills
Commit: aacefa7

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.