netlify-identity

Use when the task involves authentication, user signups, logins, password recovery, OAuth providers, role-based access control, or protecting routes and functions. Always use `@netlify/identity`. Never use `netlify-identity-widget` or `gotrue-js` — they are deprecated.

Quality

100%

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

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean and code-forward with executable examples, clearly sequenced multi-step auth workflows, and well-signaled one-level-deep references. Minor redundancy in the deprecation warning and React example does not meaningfully reduce quality.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and assumes competence without explaining what OAuth or JWTs are; every section earns its place with only minor redundancy (the deprecation warning repeats the frontmatter and the React example overlaps earlier snippets), keeping it in the lean score-3 band rather than the could-be-tightened score 2.	3 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript/TSX across install, login, signup, OAuth, callbacks, auth state, settings, React integration, and config, with a status-code table and error handling, matching the score-3 anchor rather than the pseudocode/incomplete score 2.	3 / 3
Workflow Clarity	Multi-step flows are clearly sequenced with feedback loops (OAuth two-step flow with the "never returns" checkpoint, signup emailVerified branching, callback type switch with try/catch error recovery); no destructive/batch operations trigger the score-2 cap.	3 / 3
Progressive Disclosure	A clearly signaled "Bundled References (Load As Needed)" section points one level deep to the verified references/advanced-patterns.md, splitting edge-case patterns out of the overview, matching the score-3 anchor rather than the poorly-organized score 2.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 specific, trigger-rich, and complete with an explicit Use-when clause and clear tooling guidance. It is highly distinctive with explicit exclusions that prevent conflicts with deprecated alternatives.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions ("authentication, user signups, logins, password recovery, OAuth providers, role-based access control, or protecting routes and functions") plus a decisive tool mandate, matching the score-3 anchor rather than the partial-coverage score 2.	3 / 3
Completeness	Explicitly answers both what (auth actions and tool directive) and when via an explicit "Use when the task involves..." clause, satisfying the score-3 anchor instead of the implied-when score 2.	3 / 3
Trigger Term Quality	Uses natural terms users would actually say (signups, logins, password recovery, OAuth, role-based access control) with good variation coverage, matching the score-3 anchor rather than the partial-keyword score 2.	3 / 3
Distinctiveness Conflict Risk	Clear Netlify Identity niche with an explicit tool mandate ("Always use @netlify/identity") and deprecation exclusions ("Never use netlify-identity-widget or gotrue-js"), making it unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 12 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: openai/plugins
Path: plugins/netlify/skills/netlify-identity/SKILL.md
Commit: 11c74d6

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