auth-implementation-patterns

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

Quality

49%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/auth-implementation-patterns/SKILL.md

The canonical home for this skill is auth-implementation-patterns in rmyndharis/antigravity-skills

Quality

Content

50%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 body is well-structured and concise with clear use/do-not-use guidance, but the instructions are abstract high-level directives with no executable specifics, and the single referenced detail file is missing from the bundle.

Suggestions

Add concrete, actionable guidance inline (e.g. specific token lifecycle patterns, example RBAC policy checks, or a minimal code/config snippet) rather than relying solely on the missing playbook.

Provide the referenced `resources/implementation-playbook.md` (or correct the path) so the signaled progressive-disclosure reference resolves to real content.

Add validation/verification checkpoints for security-sensitive steps (e.g. "verify tokens are not logged", "confirm least-privilege on policy enforcement") to strengthen the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of concept over-explanation, assuming Claude's competence; the only redundancy is the repeated "Build secure, scalable..." tagline duplicating the frontmatter description.	4 / 5
Actionability	Instructions are high-level planning directives ("Define users, tenants, flows...", "Plan secrets storage, rotation, logging...") with no concrete commands, code, or specific steps, and the playbook that would carry the detail does not exist.	2 / 5
Workflow Clarity	A reasonable sequence is present (define -> choose strategy -> design authz -> plan secrets -> optional playbook), but there are no validation checkpoints or feedback loops for the credential/security-sensitive steps.	3 / 5
Progressive Disclosure	Sections are well-organized and the playbook reference is clearly signaled in both Instructions and a Resources section, but the referenced `resources/implementation-playbook.md` does not exist, breaking navigation to the detail content.	3 / 5
	Total	12 / 20 Passed

Description

48%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 clearly identifies the auth/authz domain and uses appropriate third-person voice, but it is padded with buzzwords ("industry-standard patterns", "modern best practices") and omits any explicit trigger guidance for when to invoke the skill.

Suggestions

Replace buzzword phrases ("industry-standard patterns", "modern best practices") with concrete capabilities such as "implement OAuth2/social login, SSO, session management, JWT lifecycle, and RBAC policy enforcement".

Add an explicit trigger clause, e.g. "Use when implementing user authentication, securing REST/GraphQL APIs, adding OAuth2/SSO, or designing RBAC/session management".

Include natural synonyms users say ("login", "auth", "SSO", "OAuth") to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ("authentication and authorization systems") and one generic action ("Build"), but "using industry-standard patterns and modern best practices" is buzzword fluff with no concrete actions; falls below the midpoint toward anchor 2.	2 / 5
Completeness	Has a clear "what" but no "when" — there is no "Use when..." clause or explicit trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes the natural core terms "authentication" and "authorization", but misses common synonyms users say like "login", "auth", "SSO", "OAuth", or "session".	3 / 5
Distinctiveness Conflict Risk	Authentication/authorization is a fairly distinct niche with limited overlap risk against unrelated skills, though the breadth of "systems" leaves minor overlap with general security skills.	4 / 5
	Total	12 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/auth-implementation-patterns/SKILL.md
Commit: debb2ec

Reviewed: 1 day 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.