CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/mfa-flow-test-author

Build-an-X workflow for authoring automated tests covering multi-factor authentication flows: TOTP (RFC 6238, deterministic codes from a known secret + fixed time), HOTP (RFC 4226, counter-based), SMS/email OTP, WebAuthn/passkey registration and authentication via Chrome DevTools Protocol virtual authenticator (WebAuthn L2 §11), recovery codes, MFA enrollment, and step-up authentication challenges. Use when the team needs end-to-end MFA test coverage beyond what oauth-flow-test-author covers, or when introducing a new second factor to an existing auth surface.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

The body is a well-structured, actionable 8-step recipe with executable code, test vectors, explicit checkpoints, and clean progressive disclosure via a single verified reference. The only meaningful weakness is mild verbosity from restating mechanics Claude already knows.

Suggestions

Tighten the conceptual explanations in Steps 1-2 (e.g., the HOTP counter-increment narrative) to pure pointers, trusting Claude's existing knowledge of TOTP/HOTP mechanics.

Trim the Overview paragraph that re-describes the companion skills already named in the frontmatter description to reduce redundancy.

Consider moving the RFC test-vector lines into the relevant reference or a compact table to further compress the inline body.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes competence (RFC section pointers, terse test vectors), but includes some conceptual restatement of mechanics Claude knows (e.g., HOTP counter increment behavior) and a body length that could be tightened in places.

2 / 3

Actionability

Provides fully executable pytest functions with real library calls (pyotp, Playwright CDP), concrete endpoints/headers, and RFC test vectors — copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

Eight clearly sequenced steps with explicit negative-case checkpoints (wrong/expired/replay/single-use), a final coverage checklist, and an anti-patterns table providing feedback loops for fragile operations.

3 / 3

Progressive Disclosure

Body is a concise overview with the lengthy WebAuthn ceremony detail correctly split into a single, clearly signaled one-level-deep reference file (verified to exist at references/webauthn-virtual-authenticator.md).

3 / 3

Total

11

/

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 specific, trigger-rich, and explicitly answers both what the skill does and when to use it, with a clear niche that distinguishes it from companion first-factor skills. Voice is appropriately third person throughout.

DimensionReasoningScore

Specificity

Enumerates six concrete second-factor mechanisms (TOTP, HOTP, SMS/email OTP, WebAuthn/passkey, recovery codes, enrollment, step-up) as distinct actions, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly states what it does ('authoring automated tests covering multi-factor authentication flows') and when to use it ('Use when the team needs end-to-end MFA test coverage beyond...'), satisfying both what and when.

3 / 3

Trigger Term Quality

Includes natural terms a user would say ('MFA test coverage', 'second factor', 'TOTP', 'passkey', 'OTP', 'step-up') alongside technical identifiers, giving good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche (second-factor MFA test authoring) with an explicit boundary against the companion oauth-flow-test-author and distinct triggers, minimizing conflict risk.

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_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents