CtrlK
BlogDocsLog inGet started
Tessl Logo

auth-implementation-patterns

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.

83

1.19x
Quality

76%

Does it follow best practices?

Impact

100%

1.19x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/auth-implementation-patterns/SKILL.md

The canonical home for this skill is auth-implementation-patterns in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

The content is highly actionable with comprehensive executable code across all major auth patterns, but it is padded with basic concept explanations Claude already knows, presents no sequenced workflow with validation checkpoints, and its referenced bundle files are missing entirely.

Suggestions

Create the referenced bundle files (references/jwt-best-practices.md, references/oauth2-flows.md, references/session-security.md, assets/auth-security-checklist.md, assets/password-policy-template.md, scripts/token-validator.ts) or remove the dangling Resources entries so navigation is not broken.

Trim the 'Authentication vs Authorization' and 'Core Concepts' sections, which explain fundamentals Claude already knows, to improve token efficiency.

Add an explicit implementation workflow with validation checkpoints (e.g., verify token rotation, test session invalidation, run security checklist) to give the security-critical patterns a clear validate→fix→retry sequence.

DimensionReasoningScore

Conciseness

The body is mostly executable code, but sections like "Authentication vs Authorization" ("Who are you?", "Verifying identity...") and "Core Concepts" restate fundamentals Claude already knows, and the Best Practices / Common Pitfalls lists restate obvious advice.

3 / 5

Actionability

Provides copy-paste-ready, complete TypeScript implementations for JWT generation/verification, refresh-token flow, sessions, OAuth2/Passport, RBAC, permission checks, password hashing, and rate limiting across the common cases.

5 / 5

Workflow Clarity

The skill is organized as a pattern catalog with clear topical sections rather than a sequenced multi-step workflow, and it lacks explicit validation checkpoints or validate→fix→retry feedback loops for the security-critical operations it covers.

3 / 5

Progressive Disclosure

A Resources section clearly signals one-level-deep references (jwt-best-practices.md, oauth2-flows.md, session-security.md, auth-security-checklist.md, password-policy-template.md, token-validator.ts), but none of those referenced files actually exist in references/, assets/, or scripts/, so the inlined ~640-line body carries content that should live in those bundles.

3 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-formed: it states concrete capabilities, names specific technologies, and provides an explicit 'Use when' trigger clause with natural phrasing. Minor gaps in trigger synonyms (login, SSO, session) keep trigger quality just below maximal.

DimensionReasoningScore

Specificity

Lists several concrete capabilities and patterns ("JWT, OAuth2, session management, and RBAC", "implementing auth systems, securing APIs, or debugging security issues"), though the leading verb "Master ... patterns" is slightly abstract, keeping it just below comprehensive.

4 / 5

Completeness

Explicitly 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 concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("implementing auth systems", "securing APIs", "debugging security issues") plus named terms (JWT, OAuth2, RBAC), but omits common variations like "login", "session", or "SSO".

4 / 5

Distinctiveness Conflict Risk

Occupies a clear auth/security niche with distinct triggers ("auth systems", "securing APIs", "debugging security issues") that are unlikely to collide with unrelated skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (648 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

14

/

16

Passed

Repository
Dicklesworthstone/pi_agent_rust
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.