auth-implementation-patterns

Build secure, scalable authentication and authorization systems using industry-standard patterns and modern best practices.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

The skill body is concise and well-organized, but it stays at an abstract planning level with no executable code or commands, and it references a `resources/implementation-playbook.md` file that does not exist in the bundle. Adding concrete examples or the missing playbook would raise actionability and progressive disclosure.

Suggestions

Provide at least one concrete, executable example (e.g. a JWT verification snippet or an RBAC policy check) rather than only planning-level bullets.

Either create `resources/implementation-playbook.md` or remove the references to it, since the referenced file is not present in the bundle.

Add an explicit validation/checkpoint step in the workflow (e.g. 'verify token handling and policy enforcement before deploying') to support the sensitive nature of auth changes.

Dimension	Reasoning	Score
Conciseness	The body is lean: short bullet lists and directive instructions with no padding or restating of concepts Claude already knows; every section earns its place.	3 / 3
Actionability	Instructions like "Choose auth strategy (session, JWT, OIDC)" give direction but no executable code, commands, or concrete examples, so guidance is actionable in intent but incomplete in specifics.	2 / 3
Workflow Clarity	The Instructions list a sensible sequence (define → choose → design → plan) and the Limitations add validation/clarification checkpoints, but auth changes are sensitive operations lacking an explicit validate-then-fix feedback loop, capping clarity at 2.	2 / 3
Progressive Disclosure	It signals one external reference (`resources/implementation-playbook.md`) at one level of depth, but no `resources/`, `scripts/`, or `assets/` bundle directories exist, so the referenced file is not actually present and navigation cannot be verified.	2 / 3
	Total	9 / 12 Passed

Description

62%

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 specific and occupies a clear niche, but it omits an explicit "Use when..." trigger clause and natural user terms like "login", "OAuth", or "SSO". Adding trigger guidance would lift completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when building login, OAuth/SSO, session management, or RBAC systems.'

Add natural user-facing terms such as 'login', 'sign-in', 'auth', 'JWT', and 'OAuth' to improve trigger coverage.

Consider trimming 'industry-standard patterns and modern best practices' as it reads as mild buzzword padding.

Dimension	Reasoning	Score
Specificity	"Build secure, scalable authentication and authorization systems" names the domain and multiple concrete actions (build, secure, scalable) with explicit techniques (industry-standard patterns, modern best practices).	3 / 3
Completeness	It clearly states what the skill does (build secure auth/authz systems) but lacks an explicit "Use when..." clause, so the when-side is only implied, capping completeness at 2.	2 / 3
Trigger Term Quality	Terms like "authentication", "authorization", and "authentication systems" are relevant, but common user phrasings such as "login", "OAuth", "SSO", "auth", or "JWT" are absent, so coverage of natural terms is incomplete.	2 / 3
Distinctiveness Conflict Risk	The combined focus on authentication AND authorization systems is a clear, well-scoped niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: boisenoise/skills-collections
Commit: f36337d

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.