Name: auth0-branding
Rating: 74.4 (1 reviews)
Author: auth0

auth0-branding

Use when customizing the look of Auth0 Universal Login to match a brand — changing colors, logo, fonts, page layout, or login text. Also use when resetting branding to defaults or checking if branding is wired up end-to-end. Does not cover full custom UI screens — use acul-screen-generator for that.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

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-architected skill body: actionable commands, explicit validation gates and feedback loops, and clean progressive disclosure to verified reference files. Its only real weakness is redundancy — capabilities are summarized in three places and some prose sections could be trimmed.

Suggestions

Collapse the triple coverage of capabilities: keep the routing table and the per-capability 'See references/X.md' pointers, but drop the re-summary of each capability that duplicates the table row.

Tighten the Plan mode section into a compact allowed/deferred/still-do checklist rather than multi-paragraph prose; the detail belongs in the relevant capability reference.

Merge the standalone 'References' list with the per-capability pointers so each capability's reference is stated once, eliminating the second redundant listing.

Dimension	Reasoning	Score
Conciseness	Mostly efficient domain-specific guidance, but the capabilities are described three times (the Capabilities table, the per-capability sections, and the References list), and the Plan mode and Prompt style sections are long prose that could be tightened — so not every token earns its place.	2 / 3
Actionability	Provides copy-paste-ready executable commands and field names — `auth0 tenants list`, `auth0 tenants use <name>`, `auth0 test login`, `PATCH /branding/themes/default`, and concrete toggle values like `universal_login_experience: classic` — plus a Common Mistakes table with exact fixes.	3 / 3
Workflow Clarity	Multi-step processes are sequenced with explicit checkpoints: the intent-vs-no-intent routing, the 'run auth0 tenants list, confirm, stop if wrong tenant' write gate, the GET-then-PATCH/merge-before-PUT patterns, and the post-apply 'Verify in browser' yes/no validation loop.	3 / 3
Progressive Disclosure	SKILL.md is a clear overview with one-level-deep, well-signaled references: every referenced file (all 9 confirmed present) is named inline per capability and listed with a one-line description in the References section, with no nested chaining.	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 description: concrete multi-action capabilities, natural trigger terms, explicit 'when to use' guidance, and explicit de-scoping against a sibling skill. It hits every dimension's top anchor concisely without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'changing colors, logo, fonts, page layout, or login text', 'resetting branding to defaults', 'checking if branding is wired up end-to-end' — matching the multiple-specific-actions anchor; uses third-person imperative voice with no first/second-person penalty.	3 / 3
Completeness	Explicitly answers both what (customizing look / resetting / checking) and when via repeated 'Use when...' / 'Also use when...' trigger clauses, satisfying the explicit-trigger anchor.	3 / 3
Trigger Term Quality	Natural terms a user would say are well covered: 'customizing the look', 'match a brand', 'colors, logo, fonts', 'login text', 'resetting branding to defaults', 'checking if branding is wired up', plus the domain noun 'Universal Login'.	3 / 3
Distinctiveness Conflict Risk	Clear Auth0-Universal-Login-branding niche, and it proactively distinguishes itself with 'Does not cover full custom UI screens — use acul-screen-generator for that', making conflict with adjacent skills unlikely.	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: 1 day 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.