auth0-vue
Use when adding authentication to Vue.js 3 applications (login, logout, user sessions, protected routes) - integrates @auth0/auth0-vue SDK for SPAs with Vite or Vue CLI
96
95%
Does it follow best practices?
Impact
100%
1.04xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
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 well-crafted skill description that excels at trigger terms and completeness with an explicit 'Use when...' clause. The main weakness is that the capabilities could be more specific about concrete actions beyond the basic auth concepts. The technology stack specificity (Vue.js 3, Auth0, Vite/Vue CLI) makes it highly distinctive.
Suggestions
Expand the capabilities to include more specific actions like 'configure route guards', 'handle token refresh', or 'implement role-based access control' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Vue.js 3 authentication) and lists some actions (login, logout, user sessions, protected routes), but doesn't describe concrete implementation actions like 'configure auth guards' or 'implement token refresh'. The parenthetical list is helpful but somewhat surface-level. | 2 / 3 |
Completeness | Explicitly answers both what (authentication with Auth0 SDK for Vue.js 3 SPAs) and when (starts with 'Use when adding authentication to Vue.js 3 applications'). The 'Use when...' clause is present and clear. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'authentication', 'Vue.js 3', 'login', 'logout', 'user sessions', 'protected routes', 'auth0', 'SPA', 'Vite', 'Vue CLI'. These are terms developers naturally use when seeking auth help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack: Vue.js 3 + Auth0 + SPA + Vite/Vue CLI. Unlikely to conflict with React auth skills, other Vue skills, or non-Auth0 authentication approaches. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that exemplifies best practices: it's concise, provides executable code, has a clear workflow, and uses progressive disclosure effectively. The 'When NOT to Use' section and common mistakes table add significant value by preventing errors before they occur. The quick reference section provides excellent discoverability for common operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts Claude already knows. Each section serves a clear purpose with no padding or unnecessary context about what Vue.js or Auth0 are. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples including npm commands, TypeScript configuration, and a complete Vue component. The code is specific and immediately usable. | 3 / 3 |
Workflow Clarity | Clear 5-step numbered workflow with explicit sequencing. Includes a validation step (Step 5: Test Authentication) and the 'When NOT to Use' section provides important guardrails. The common mistakes table serves as a troubleshooting checklist. | 3 / 3 |
Progressive Disclosure | Excellent structure with a quick start overview and well-signaled one-level-deep references to setup.md, integration.md, and api.md. Content is appropriately split between the main skill and detailed documentation files. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- auth0/agent-skills
- Commit
fbcbfb1
- 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.