Use when adding authentication to Express.js server-rendered web applications with session management - integrates express-openid-connect for traditional web apps
86
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 — 98%
↑ 1.25xAgent success when using this skill
Validation for skill structure
Protected routes and auth middleware setup
Correct auth package
100%
100%
dotenv loaded
100%
100%
authRequired false
100%
100%
auth0Logout enabled
100%
100%
Env vars for credentials
66%
100%
requiresAuth on routes
100%
100%
isAuthenticated check
100%
100%
User profile access
100%
100%
Auth0 app type documented
100%
100%
gitignore for env file
100%
100%
Without context: $0.4117 · 1m 41s · 25 turns · 32 in / 5,261 out tokens
With context: $1.0136 · 3m 1s · 44 turns · 3,942 in / 9,314 out tokens
API integration with access tokens
Correct auth package
100%
100%
authorizationParams present
100%
100%
audience configured
100%
100%
response_type code
0%
100%
offline_access scope
100%
100%
Access token destructuring
66%
100%
Bearer token in request
100%
100%
Route requires auth
100%
100%
Env vars for credentials
100%
100%
Without context: $0.3980 · 1m 48s · 24 turns · 30 in / 5,217 out tokens
With context: $0.8859 · 3m 32s · 36 turns · 4,213 in / 10,184 out tokens
Advanced auth config and security hardening
errorOnRequiredAuth
57%
71%
attemptSilentLogin
28%
100%
idpLogout enabled
50%
100%
afterCallback hook
71%
85%
Session enrichment
100%
100%
helmet security headers
100%
100%
Rolling session config
0%
100%
Absolute session duration
0%
100%
Env vars for credentials
83%
100%
Without context: $0.4676 · 2m 31s · 23 turns · 28 in / 7,926 out tokens
With context: $0.6484 · 2m 24s · 28 turns · 2,240 in / 6,912 out tokens
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.