CtrlK
BlogDocsLog inGet started
Tessl Logo

acul-screen-generator

Use when building or customizing Auth0 Universal Login screens with full UI control — creating branded login, signup, or MFA screens using the ACUL React or Vanilla JS SDK. Use this even if the user says "custom login page", "style my Auth0 login", or "build my own Universal Login UI" without mentioning ACUL directly. Does not cover basic branding (colors/logo only) — use auth0-branding for that.

73

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

85%

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

A thorough, highly actionable 9-phase workflow with strong validation loops and well-organized progressive disclosure into real reference and template files. Its main weakness is length: the screen-registration runtime gotcha and reference hierarchy are restated multiple times, adding tokens that could be consolidated.

Suggestions

Consolidate the screen-registration / 'Screen not implemented' guidance into a single canonical section and cross-reference it from Phase 2B, Phase 6, and Phase 7 instead of re-explaining it three times.

Merge the inline 'Reference Hierarchy' code block with the later 'Reference Files' table so the resolution order and the load-conditions live in one place.

Tighten Phase 2B and the 'auth0-acul-samples Architecture' section, which overlap on samples-availability checks and the modular directory layout.

DimensionReasoningScore

Conciseness

The body is dense and largely free of filler Claude already knows, but it is very long and repeats the same screen-registration / 'Screen not implemented' gotcha across three sections (Phase 2B Step 4d, Phase 6 Screen Registration, Phase 7 Runtime check) plus a duplicated Reference Hierarchy, so it could be tightened. It is mostly efficient rather than fully lean.

2 / 3

Actionability

Provides exact CLI commands (e.g. `auth0 acul init <app_name> -t react -s login-id,login-password,signup`), copy-paste-ready index.tsx and manager-hook templates, file paths, and an error-pattern→fix table — fully executable guidance.

3 / 3

Workflow Clarity

A clearly sequenced 9-phase pipeline (0–8) with explicit gating checkpoints (Node ≥ 22 before proceeding, custom-domain check) and a Phase 7 iterative build/fix loop with a 5-iteration cap and stop-on-plateau rule.

3 / 3

Progressive Disclosure

SKILL.md acts as an overview pointing to one-level-deep, clearly-signaled bundle files — verified-present references (screen-catalog, sdk docs, social-providers, theming-patterns, cli-commands) and asset templates, each introduced via 'Load when'/'Use when' tables with easy navigation.

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, specific description that states concrete capabilities, gives natural-language trigger terms, and explicitly delimits its scope against the related auth0-branding skill. It answers both what the skill does and when to use it without filler.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'building or customizing Auth0 Universal Login screens with full UI control — creating branded login, signup, or MFA screens using the ACUL React or Vanilla JS SDK' — naming both the domain and specific frameworks. Voice is imperative ('Use when building...') matching the rubric's own good examples rather than first/second-person narration, so no specificity penalty applies.

3 / 3

Completeness

Explicitly answers both 'what' (building/customizing ACUL Universal Login screens with the React or Vanilla JS SDK) and 'when' with two explicit trigger clauses ('Use when building...', 'Use this even if the user says...').

3 / 3

Trigger Term Quality

Good coverage of natural user phrasings — "custom login page", "style my Auth0 login", "build my own Universal Login UI" — terms a user would actually say, plus explicit ACUL and SDK keywords.

3 / 3

Distinctiveness Conflict Risk

Clear niche with distinct ACUL/Universal-Login triggers, and it explicitly disambiguates from a neighboring skill ('Does not cover basic branding (colors/logo only) — use auth0-branding for that'), making wrong-skill conflicts unlikely.

3 / 3

Total

12

/

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (557 lines); consider splitting into references/ and linking

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 2 missing, 8 deeper-than-1-level

Warning

Total

13

/

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.