CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 as a platform-selection router with a clear navigation sequence and a useful verification checklist, but it is padded with generic security guidance Claude already knows, duplicated platform descriptions, and internal refactor bookkeeping. Its reference pointers don't resolve to any bundle files, and no executable guidance exists at any level.

Suggestions

Cut the generic Security Best Practices section (token storage, HTTPS, signature validation, password policies) and the Refactor Notes/SPEC bookkeeping — they restate known material or serve internal process, costing tokens without adding skill-specific value.

De-duplicate the platform profiles: 'Best For' and the 'Choose X when' bullets repeat the same criteria; merge them into a single decision table.

Fix the progressive-disclosure defects: create the referenced files (or correct the paths — 'reference/' vs the bundle's 'references/' convention) so every pointer resolves, and move the Common Patterns and Rationalizations/Red Flags content into them to slim the overview.

DimensionReasoningScore

Conciseness

Several sections restate what Claude already knows — generic security best practices ("Always use HTTPS in production", "Always validate token signatures", "Enforce strong password requirements") and marketing-style platform blurbs whose "Best For" content is then duplicated nearly verbatim in the "Choose X when" bullets. The trailing "Refactor Notes" with internal bookkeeping ("R4 audit verdict... SPEC-V3R2-WF-001 §6.2 line 272") is pure process noise. This matches anchor 2's 'noticeably verbose; several unnecessary explanations or padded sections' better than the mostly-efficient anchor 3.

2 / 5

Actionability

The decision guidance is concrete for platform selection ("Choose Clerk when: Building modern Next.js or React applications") and the Context7 section names specific tool calls ("Use resolve-library-id with 'auth0'"), but there is no executable code, command, or config example anywhere — all implementation is deferred to reference files. This is 'some concrete guidance but incomplete', not the level-2 vague-hints anchor, since the routing and lookup instructions are specific.

3 / 5

Workflow Clarity

The Navigation Guide gives a clear numbered sequence ("1. Start with Quick Platform Selection... 5. Use Context7 tools") and the Verification checklist ("Tokens stored in httpOnly, Secure, SameSite cookies", "Password reset invalidates all existing sessions") provides explicit checkpoints. No destructive or batch operations are involved, so the validation cap doesn't apply; it falls short of anchor 5 only because there are no feedback/retry loops, which barely matter for a routing skill.

4 / 5

Progressive Disclosure

The four reference files (auth0.md, clerk.md, firebase-auth.md, comparison.md) are one level deep and well signaled with contents and key sections, but none of them exist in the bundle — the body points to 'reference/*.md' while no such files are present (and the path spelling 'reference/' vs the conventional 'references/' is inconsistent). Meanwhile substantial content that belongs in those files (Common Patterns, Security Best Practices, Rationalizations) is inlined. This lands at anchor 3: 'some structure but could be better organized; references present but' pointing at files not in the bundle.

3 / 5

Total

12

/

20

Passed

Description

78%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 description in third-person voice with an explicit 'Use when' trigger clause and good natural trigger terms. Its main weakness is that the 'what' half names the platforms but no concrete actions, and 'security features' slightly widens the trigger surface.

DimensionReasoningScore

Specificity

The description names the domain ("Authentication and authorization specialist covering Auth0, Clerk, and Firebase Auth") but the 'what' offers no concrete verbs — it's a specialist 'covering' platforms rather than performing named actions. Concrete tasks only appear in the 'when' clause ("implementing authentication, MFA, SSO, passkeys"), matching the 'names domain and 1-2 concrete actions' anchor rather than the level-4 'lists several specific actions'.

3 / 5

Completeness

It explicitly answers both: 'what' ("Authentication and authorization specialist covering Auth0, Clerk, and Firebase Auth") and 'when' with concrete trigger phrases ("Use when implementing authentication, MFA, SSO, passkeys, WebAuthn, social login, or security features"), matching the anchor-5 example structure exactly. It is not level 4 because the 'when' clause is already explicit and specific, not merely present.

5 / 5

Trigger Term Quality

"authentication, MFA, SSO, passkeys, WebAuthn, social login, or security features" are natural phrases users would say. Common variations like 'login', 'sign-in', 'OAuth', or 'passwordless' are missing, so it falls just below the comprehensive-synonyms anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — three named auth platforms distinguish it from generic skills — but "or security features" is broad and could overlap a general security-audit skill, giving minor conflict risk. It is above anchor 3 (which would lack named platforms) but not the minimal-risk anchor 5.

4 / 5

Total

16

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

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.