auth-implementation-patterns

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

Quality

58%

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 ./skills/auth-implementation-patterns/SKILL.md

Quality

Content

68%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 commendably lean and well-organized with clean sectioning and a clear external reference, but its instructions stay high-level and lack inline validation checkpoints, and the referenced playbook file is missing from the bundle.

Suggestions

Add an explicit validation/checklist step in the Instructions workflow (e.g., 'Verify token lifecycle, policy enforcement, and secret rotation before completing') so checkpoints are inline rather than only implied by Limitations.

Make the action bullets more concrete with specific sub-steps or decision points (e.g., when to choose JWT vs session vs OIDC) instead of deferring all detail to the playbook.

Add the referenced resources/implementation-playbook.md to the bundle, or remove/fix the reference, so the one-level-deep navigation actually resolves.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with no concept explanations Claude already knows; every section is tight bullets that assume competence, with only trivial redundancy (the intro echoes the frontmatter description).	5 / 5
Actionability	Bullets name concrete specifics (session, JWT, OIDC; secrets storage, rotation, audit) but each is a high-level planning directive ('Design authorization model') missing the specific steps to execute, and real detail is deferred to the external playbook.	3 / 5
Workflow Clarity	A rough define-choose-design-plan sequence is present, but there are no explicit validation/verification checkpoints in the workflow itself; the 'stop and ask' note lives in Limitations rather than inline, so checkpoints are only implicit.	3 / 5
Progressive Disclosure	Clear section structure with a well-signaled one-level-deep reference to resources/implementation-playbook.md, but the referenced file does not exist in the bundle, which breaks navigation despite good organization.	4 / 5
	Total	15 / 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 its domain but is vague on concrete actions, relies on buzzword padding, and omits any explicit use-when trigger guidance. It is reasonably distinct from other skills but would benefit from sharper, more specific language.

Suggestions

Replace buzzword padding ('secure, scalable', 'industry-standard patterns', 'modern best practices') with concrete actions such as 'implement OAuth2/OIDC login, JWT/session lifecycle, and RBAC policy enforcement'.

Add an explicit 'Use when ...' trigger clause naming natural phrases users say (login, SSO, social login, API authentication, role-based access control).

Include common synonyms/file-format-style triggers (JWT, OAuth2, OIDC, RBAC, session management) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('authentication and authorization systems') but offers only one generic action ('Build ... systems') padded with vague fluff ('secure, scalable', 'industry-standard patterns', 'modern best practices') rather than concrete capabilities.	2 / 5
Completeness	It gives a clear 'what' (build auth/authz systems) but no 'when'/Use-when trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'authentication and authorization' are relevant natural terms, but common variations users actually say (login, OAuth, SSO, JWT, RBAC, access control, permissions) are absent from the description.	3 / 5
Distinctiveness Conflict Risk	'authentication and authorization systems' is a clear niche with distinct triggers, with only minor overlap risk against broader 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: sickn33/antigravity-awesome-skills
Path: skills/auth-implementation-patterns/SKILL.md
Commit: 1f67c44

Reviewed: about 17 hours 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.