moai-platform-auth

Authentication and authorization specialist covering Auth0, Clerk, and Firebase Auth. Use when implementing authentication, MFA, SSO, passkeys, WebAuthn, social login, or security features.

Quality

63%

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 ./.moai/archive/skills/v2.16/moai-platform-auth/SKILL.md

Quality

Content

42%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 a well-organized overview that avoids explaining basics Claude already knows, but it lacks executable code and outsources all concrete implementation to four reference files that are not present in the bundle, leaving it more descriptive than actionable with broken navigation.

Suggestions

Ship the four referenced bundle files (reference/auth0.md, clerk.md, firebase-auth.md, comparison.md) or inline the essential implementation steps so the skill is self-contained.

Add at least one minimal executable snippet per platform (e.g. SDK init / token validation) so the body provides concrete, copy-paste-ready guidance instead of only descriptions.

Merge the redundant 'Quick Platform Selection' and 'Quick Decision Guide' sections to remove the restated Best For / Choose-when overlap and tighten token usage.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no padding of basic concepts Claude already knows, but the 'Quick Platform Selection' (Best For / Key Strengths) and 'Quick Decision Guide' (Choose X when) sections restate the same guidance, creating redundant sections that could be tightened.	3 / 5
Actionability	The body is largely descriptive ('Auth0 uses refresh token rotation, Clerk uses session tokens') and delegates all concrete platform-specific implementation to reference files; with no executable code or commands present, it offers only high-level hints for an implementation skill.	2 / 5
Workflow Clarity	A Navigation Guide lists a clear 5-step sequence, but the steps are abstract ('Review Common Authentication Patterns', 'Open platform-specific reference file') with no validation checkpoints or concrete commands, and the central implementation step points to a missing file.	3 / 5
Progressive Disclosure	The overview is well structured with clearly signaled one-level-deep references (reference/auth0.md, clerk.md, firebase-auth.md, comparison.md) and a navigation guide, but none of the referenced bundle files exist, so the disclosure path leads to dead ends.	3 / 5
	Total	11 / 20 Passed

Description

83%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.

A strong, third-person description that clearly states scope and provides an explicit 'Use when' trigger with concrete capability keywords. It is held back from a perfect score only by the vague 'security features' tail and a few missing common synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain (Auth0, Clerk, Firebase Auth) and lists several concrete capabilities ('implementing authentication, MFA, SSO, passkeys, WebAuthn, social login'), but the trailing 'or security features' is generic, leaving a minor coverage gap short of the comprehensive anchor.	4 / 5
Completeness	Explicitly answers both what ('Authentication and authorization specialist covering Auth0, Clerk, and Firebase Auth') and when ('Use when implementing authentication, MFA, SSO, passkeys, WebAuthn, social login, or security features') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural terms users would say ('authentication, MFA, SSO, passkeys, WebAuthn, social login') plus named platforms, but common synonyms like 'login', 'sign in', or '2FA' are absent.	4 / 5
Distinctiveness Conflict Risk	The three named platforms create a clear, distinct niche with minimal conflict, but the generic 'security features' clause introduces minor overlap risk with a general security skill.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: modu-ai/moai-adk
Path: .moai/archive/skills/v2.16/moai-platform-auth/SKILL.md
Commit: 4100d87

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.