Name: nextjs-supabase-auth
Rating: 52.8 (1 reviews)
Author: administrakt0r

nextjs-supabase-auth

Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route.

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/nextjs-supabase-auth/SKILL.md

The canonical home for this skill is nextjs-supabase-auth in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

47%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 but largely content-free: it describes what the skill covers without providing the executable guidance, code, or workflow steps needed to actually perform the integration. It reads more like a table of contents than a skill.

Suggestions

Add executable code examples for each Pattern (e.g. a real `createBrowserClient` / `createServerClient` setup, a middleware snippet that refreshes the session, and the `/auth/callback` route handler).

Expand each Anti-Pattern from a bare title into a short "do this instead" note, e.g. for "getSession in Server Components" explain to use `getUser()` for secure checks.

Replace the generic "When to Use" boilerplate with concrete guidance on when this skill applies versus the related `nextjs-app-router` and `supabase-backend` skills.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids over-explaining concepts Claude already knows, but the generic boilerplate "This skill is applicable to execute the workflow or actions described in the overview" and the somewhat redundant Capabilities list keep it just below fully efficient.	4 / 5
Actionability	It only offers high-level hints like "Create properly configured Supabase clients" and "Protect routes and refresh sessions in middleware" with no executable code or commands, and the Anti-Patterns are bare titles with no explanation of what to do instead.	2 / 5
Workflow Clarity	The Patterns section implies a rough order (client setup, middleware, callback) but there are no numbered steps, no concrete commands, and no validation checkpoints for token/session handling.	2 / 5
Progressive Disclosure	The short body is organized into clear sections (Capabilities, Requirements, Patterns, Anti-Patterns, Related Skills) with no nested references, which is good structure for a small skill, though the Pattern stubs hint at deeper content that is neither inlined nor linked.	4 / 5
	Total	12 / 20 Passed

Description

70%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 niche and supplies explicit trigger phrases, which is solid. It is held back by an abstract "what" statement and a few keyword-stuffed rather than natural trigger terms.

Suggestions

Replace the abstract "Expert integration of" with concrete actions, e.g. "Set up Supabase clients, add auth middleware, handle OAuth callbacks, and protect routes in Next.js App Router."

Soften keyword-stuffed triggers ("supabase auth next", "authentication next.js") into natural phrases such as "supabase authentication in next.js" or "add login with supabase".

Fix the missing punctuation between "App Router" and "Use when" so the trigger clause parses cleanly.

Dimension	Reasoning	Score
Specificity	"Expert integration of Supabase Auth with Next.js App Router" names the domain and a couple of concrete sub-areas (auth middleware, protected route), but the core action "integration" is abstract rather than a list of concrete actions, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It answers both "what" (integration of Supabase Auth with Next.js App Router) and "when" (explicit "Use when:" trigger phrases), but the "what" is a single abstract action rather than the concrete actions shown in the anchor-5 example, keeping it just below a 5.	4 / 5
Trigger Term Quality	The "Use when" clause lists several natural phrases a user would say ("login supabase", "auth middleware", "protected route", "authentication next.js") with good coverage, though keyword-stuffed terms like "supabase auth next" are slightly unnatural and a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The Supabase-Auth-with-Next.js-App-Router niche is mostly distinct with specific triggers, but broad terms like "authentication next.js" carry minor overlap risk with a generic Next.js or Supabase skill.	4 / 5
	Total	15 / 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-claude/skills/nextjs-supabase-auth/SKILL.md
Commit: 57c135b

Reviewed: 3 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.