Use when starting Auth0 integration in any framework - detects your stack (React, Next.js, Vue, Angular, Express, Fastify, React Native) and routes to correct SDK setup workflow
Install with Tessl CLI
npx tessl i github:auth0/agent-skills --skill auth0-quickstart92
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 94%
↑ 1.14xAgent success when using this skill
Validation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger terms covering multiple frameworks and a clear 'Use when' clause. The main weakness is that it describes the meta-action (detecting and routing) rather than the concrete integration tasks the skill actually performs. Adding specific actions like 'configure authentication flows' or 'set up callbacks' would improve specificity.
Suggestions
Add 2-3 concrete actions the skill performs beyond detection, such as 'configure authentication callbacks', 'implement login/logout flows', or 'set up protected routes'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Auth0 integration) and mentions detection and routing actions, but doesn't list specific concrete actions like 'configure callbacks', 'set up authentication middleware', or 'implement login flows'. | 2 / 3 |
Completeness | Clearly answers both what ('detects your stack and routes to correct SDK setup workflow') and when ('Use when starting Auth0 integration in any framework') with explicit trigger guidance at the start. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Auth0', 'React', 'Next.js', 'Vue', 'Angular', 'Express', 'Fastify', 'React Native', 'SDK setup', 'integration'. These are exactly what developers would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically Auth0 integration with explicit framework list. Unlikely to conflict with generic authentication skills or other identity provider integrations due to the Auth0-specific focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured quickstart skill with excellent actionability and progressive disclosure. The framework detection table and executable CLI commands make it immediately useful. Main weaknesses are missing validation steps in the workflow and some content redundancy between sections.
Suggestions
Add validation checkpoints after key steps, e.g., 'Verify installation: `auth0 --version`' and 'Confirm app created: check output for client_id'
Remove or consolidate the 'Related Skills' section since it duplicates Step 4's framework skill list
Add a quick verification command after 'auth0 login' to confirm successful authentication
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the 'Related Skills' section largely duplicates information already in Step 4, and the extensive Tier 2 framework links could be condensed. The common mistakes table adds value but some entries explain obvious concepts. | 2 / 3 |
Actionability | Provides fully executable commands throughout - framework detection commands, CLI installation, app creation with specific flags, and credential retrieval. All commands are copy-paste ready with concrete examples for each application type. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (Detect → Setup → Create → Use), but lacks validation checkpoints. No verification that CLI installed correctly, no confirmation that app was created successfully, and no feedback loop for common errors during setup. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview and well-signaled one-level-deep references. Core content stays concise while pointing to specific sections in reference files (cli.md, environments.md, concepts.md) for detailed information. Navigation is intuitive. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Table of Contents
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.