Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debugging security issues.
82
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/auth-implementation-patterns/SKILL.mdQuality
Discovery
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.
This is a well-crafted skill description that excels across all dimensions. It provides specific technologies and patterns, includes natural trigger terms users would actually use, explicitly states both capabilities and when to use the skill, and carves out a distinct niche in the auth/security space.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and patterns: 'JWT, OAuth2, session management, and RBAC' along with outcomes 'build secure, scalable access control systems'. Also mentions specific use cases like 'implementing auth systems, securing APIs, debugging security issues'. | 3 / 3 |
Completeness | Clearly answers both what ('Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems') and when ('Use when implementing auth systems, securing APIs, or debugging security issues') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'authentication', 'authorization', 'JWT', 'OAuth2', 'session management', 'RBAC', 'auth systems', 'APIs', 'security issues'. These cover both technical terms and common shorthand ('auth'). | 3 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on authentication/authorization with distinct triggers (JWT, OAuth2, RBAC, session management). Unlikely to conflict with general coding or security skills due to the specific auth focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise with good progressive disclosure to detailed resources. However, it critically lacks actionability—the instructions are entirely abstract with no concrete code examples, specific commands, or executable patterns. For a security-critical domain like authentication, the absence of concrete implementation guidance significantly limits its usefulness.
Suggestions
Add at least one concrete, executable code example for a common auth pattern (e.g., JWT validation middleware or session setup)
Include specific commands or configuration snippets for common auth operations rather than abstract guidance like 'Choose auth strategy'
Add validation checkpoints to the workflow, such as 'Verify token expiration handling' or 'Test authorization policy with edge cases'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using bullet points without explaining concepts Claude already knows (JWT, OAuth2, RBAC). Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | The instructions are entirely abstract and vague ('Define users, tenants, flows', 'Choose auth strategy', 'Design authorization model') with no concrete code, commands, or executable examples. It describes what to do conceptually but provides no copy-paste ready guidance. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence (define → choose → design → plan), but there are no validation checkpoints, no feedback loops for error recovery, and no explicit verification steps for these security-critical operations. | 2 / 3 |
Progressive Disclosure | Clear overview structure with well-signaled one-level-deep references to implementation-playbook.md for detailed patterns. Content is appropriately split between overview and detailed resources. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
332e58b
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.