CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/auth0-tests

Authors tests against Auth0 - uses tenant isolation strategy (per-PR tenant or shared dev tenant with namespaced data); exercises Universal Login + auth-code-with-PKCE + client-credentials + RO-password (legacy) flows; tests Action scripts (Auth0's serverless extension hooks); tests Rules / Hooks (deprecated but still common); integrates with Auth0 Deploy CLI (`a0deploy`) for environment parity. Use when the user works with Auth0 SaaS and needs unit / integration tests for tenant config, auth flows, or Action scripts. Does not cover session lifecycle (refresh-token rotation, silent re-auth): use session-management-test-author for that. Differentiates from oauth-flow-test-author by Auth0-tenant specifics: Action scripts, Rules / Hooks, a0deploy config-drift, and Universal Login.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

A well-structured, actionable skill body with concrete executable examples, a sequenced workflow including validation, and properly one-level-deep references. The only weakness is mild verbosity in the worked example and a few explanatory sentences Claude does not need.

Suggestions

Trim the 'Worked example' to a few lines or fold its unique content into the relevant steps, since it re-narrates Steps 1, 2, 4, and 8 already covered above.

Cut context Claude already knows, e.g. 'Actions are the current Auth0 serverless extension model (post-Hooks)' and 'Rules + Hooks are deprecated as of 2024' is already in Limitations.

Consider moving the mock-OIDC server alternative (Step 7) detail into the references to keep the main flow tighter.

DimensionReasoningScore

Conciseness

Largely lean with no padding about what Auth0 is, but the 'Worked example' re-narrates steps already detailed above and some sentences ('Actions are the current Auth0 serverless extension model (post-Hooks)') explain context Claude already knows, so it could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready examples across bash (a0deploy export/import/diff), Python (M2M token test), Jest (Action unit test), Node (Rules/Hooks) and CI YAML, matching the top anchor.

3 / 3

Workflow Clarity

An explicit 8-step sequence with cross-references and a genuine validation feedback loop — the config-drift check re-exports and diffs ('diff -r ... # expect empty if no drift') and the CI block repeats it, satisfying the checkpoint anchor.

3 / 3

Progressive Disclosure

Clear overview plus one-level-deep references that are real files (references/session-checklist.md exists), with a well-signaled References section listing sister tools and RFCs; navigation is easy.

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.

A strong, dense description that names concrete capabilities, gives an explicit 'Use when' trigger, and actively disambiguates against sibling skills. Voice is third person throughout, consistent with the rubric guidance.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'exercises Universal Login + auth-code-with-PKCE + client-credentials + RO-password flows', 'tests Action scripts', 'tests Rules / Hooks', 'integrates with Auth0 Deploy CLI (a0deploy)' — matching the highest anchor.

3 / 3

Completeness

Explicitly answers both what ('Authors tests against Auth0...') and when ('Use when the user works with Auth0 SaaS and needs unit / integration tests...'), satisfying the top anchor.

3 / 3

Trigger Term Quality

Includes natural user-facing terms ('Auth0 SaaS', 'unit / integration tests for tenant config, auth flows, or Action scripts') with good coverage of what a user would actually say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Delineates a clear Auth0-tenant-specific niche and explicitly differentiates from sibling skills ('Differentiates from oauth-flow-test-author...', 'use session-management-test-author for that'), unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents