supabase-auth

Setup and manage Supabase authentication including project connection, tokens, login methods, and user management. Use when configuring Supabase access, implementing authentication, or managing users.

Quality

81%

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

Quality

Content

76%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 content is highly actionable with complete, executable code and sensible progressive disclosure to three real reference files. Its main gaps are a missing validation checkpoint before destructive admin operations and minor conciseness redundancy.

Suggestions

Add an explicit validation/verification step before destructive admin operations such as deleteUser (e.g., confirm the user ID, check the user exists, and verify authorization) so workflow_clarity is not capped at 3.

Trim redundant tokens such as the opening sentence that repeats the frontmatter description and obvious inline comments like '// Sign up' to push conciseness toward anchor 5.

Move the detailed per-method auth examples into references/auth-methods.md and keep only a quick-start representative in SKILL.md to make the progressive-disclosure split cleaner.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code with tight headers and assumes Claude already knows what Supabase and authentication are, but the opening line repeats the description and a few comments ('// Sign up', '// Sign out') state the obvious, fitting anchor 4 rather than 5.	4 / 5
Actionability	Code is fully executable and copy-paste ready across signup, signin, OTP, OAuth, anonymous auth, sessions, password recovery, and admin operations, with specific examples covering the common cases, matching anchor 5.	5 / 5
Workflow Clarity	Sections are coherently organized by topic but this is a reference catalog rather than a sequenced workflow, and the destructive admin operation deleteUser has no validation/verification checkpoint; the destructive-operation cap limits this to anchor 3.	3 / 5
Progressive Disclosure	Clear section headers and a References section point to three real one-level-deep files (auth-methods.md, session-management.md, mfa-setup.md), but some auth/session detail is inlined that also lives in the references, so it is anchor 4 rather than a clean anchor 5 split.	4 / 5
	Total	16 / 20 Passed

Description

87%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 is strong: third-person, concrete, and explicitly paired with 'Use when...' trigger guidance covering multiple natural scenarios. Its only weakness is moderate keyword coverage that lacks common synonyms like 'login' or 'auth'.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete actions ('project connection, tokens, login methods, and user management'), but the sub-capabilities are enumerated at a high level rather than comprehensively, fitting anchor 4.	4 / 5
Completeness	Explicitly answers both 'what' (setup/manage with enumerated capabilities) and 'when' ('Use when configuring Supabase access, implementing authentication, or managing users') with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('configuring Supabase access', 'implementing authentication', 'managing users'), but omits common synonyms such as 'login', 'auth', or 'sign-in', so it is not anchor 5.	4 / 5
Distinctiveness Conflict Risk	'Supabase authentication' is a clear niche with distinct, specific triggers and minimal overlap risk with unrelated skills, matching anchor 5.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: fernandezbaptiste/Skrillz
Path: skills/supabase-auth/SKILL.md
Commit: 93ed392

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.