CtrlK
BlogDocsLog inGet started
Tessl Logo

auth0-angular

Use when adding Auth0 login, logout, route guards, or HTTP interceptors to an Angular application. Integrates @auth0/auth0-angular for SPAs — use even if the user says "protect my Angular routes" or "add authentication to Angular" without naming the SDK.

76

1.16x
Quality

Does it follow best practices?

Impact

100%

1.16x

Average score across 1 eval scenario

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-structured, highly actionable skill with clean progressive disclosure and executable code throughout. The main gaps are minor duplication of examples across reference files and a thin testing/verification step in the workflow.

Suggestions

Expand the "Test Authentication" step into explicit validation checkpoints (verify callback redirect, token presence, and error$ handling) so the workflow has a real feedback loop rather than just `ng serve`.

De-duplicate examples that appear in both SKILL.md and the reference files (e.g., environment.ts config and the auth guard) — keep the inline version minimal and point to the reference for the full version.

Trim the inline app.component template in Step 4 (loading/authenticated/loggedOut branches) to a minimal login/logout example, moving the richer UI patterns into a reference.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable code and little conceptual padding, but examples are duplicated across files (environment config appears in both SKILL.md and setup.md; an auth guard appears in both api.md and integration.md) and the inline app.component template is lengthy. It is not score 3 because the duplication and verbose template mean not every token earns its place; not score 1 because there is no explanation of concepts Claude already knows.

2 / 3

Actionability

Provides fully executable, copy-paste-ready code: install commands, environment files, module/standalone configs, component templates, guards, and interceptors with real import paths and method signatures. It is not score 2 because the guidance is complete and runnable rather than pseudocode or missing key details.

3 / 3

Workflow Clarity

A clear 5-step Quick Start sequence is present (Install → Configure Env → Configure Module → Add UI → Test), but the "Test Authentication" step is minimal ("ng serve" with no verification of callback/token/error states) so checkpoints are implicit. It is not score 3 because there are no explicit validation or feedback-loop steps; not score 1 because the steps are clearly sequenced and complete.

2 / 3

Progressive Disclosure

SKILL.md is an overview with well-signaled, one-level-deep references to real files (references/setup.md, integration.md, api.md) organized in a "Detailed Documentation" section plus contextual inline links with anchors. It is not score 2 because content is appropriately split and navigation is easy rather than left inline or poorly signaled.

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.

A strong, specific description with an explicit "Use when" trigger, concrete enumerated actions, and natural paraphrased trigger phrases that reduce conflict risk. It clearly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Auth0 login, logout, route guards, or HTTP interceptors" — and names the specific SDK "@auth0/auth0-angular for SPAs", matching the score-3 anchor of multiple specific concrete actions. It is not score 2 because the actions are enumerated comprehensively rather than naming only the domain and a few actions.

3 / 3

Completeness

An explicit "Use when adding..." clause answers when, and the enumerated actions answer what, satisfying both halves required for score 3. It is not score 2 because the "when" trigger guidance is explicit rather than merely implied.

3 / 3

Trigger Term Quality

Includes natural phrasings users would say — "protect my Angular routes" and "add authentication to Angular" — alongside login/logout terms, giving good coverage including paraphrased variants. It is not score 2 because it covers common variations users actually speak, not just a single keyword.

3 / 3

Distinctiveness Conflict Risk

The niche is clearly scoped to Angular + the @auth0/auth0-angular SDK with distinct triggers, making conflict with generic auth skills unlikely. It is not score 2 because the Angular + Auth0-SDK pairing is specific enough not to overlap meaningfully with sibling skills.

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_field

'metadata' should map string keys to string values

Warning

Total

15

/

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.