Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A strong, dense reference skill: executable code throughout, critical gotchas (invite flow, role-refresh delay, CSRF, netlify dev) placed next to the code they govern, and sensible splitting of deep material into two reference files. The main costs are a duplicated house-rules tail that re-states earlier warnings, a missing end-to-end setup order, and one reference pointer whose target lacks the promised content.
Suggestions
Trim or de-duplicate the trailing 'Netlify house rules' section — it restates ~8 rules already covered in the body (netlify dev, dashboard-only config, raw OAuth, v2 functions, getSettings, failure protocol, site-gating), saving ~40 lines of token budget.
Fix the dangling pointer in the Identity event functions section: it directs readers to references/authorization-and-sessions.md for the legacy filename convention (identity-signup.ts), but that file covers admin runtime, redirect gating, and JWT refresh only — either add the legacy-filename content there or point elsewhere.
Add a short ordered getting-started sequence at the top (enable Identity in the dashboard → install @netlify/identity → add handleAuthCallback() to the landing page → test on a deploy) so configuration precedes the code that depends on it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The core body is lean and code-heavy with no re-teaching of known concepts, but the ~43-line trailing "Netlify house rules" section restates roughly eight rules already covered above (netlify dev limitation, dashboard-only config, raw OAuth warning, v2 functions, getSettings, failure protocol, site-gating), which is more than the "minor instances" of anchor 4's trimmable material yet well short of anchor 3's pervasive padding. | 4 / 5 |
Actionability | Every section ships fully executable, copy-paste-ready TypeScript or commands — client auth calls, the handleAuthCallback/acceptInvite branch, v2 function examples with getUser and role checks, verifyRequestOrigin CSRF guard, typed Identity event handlers, and _redirects/netlify.toml rules — covering the common cases across client, server, and edge. Matches the anchor-5 example standard. | 5 / 5 |
Workflow Clarity | Individual flows are well sequenced with real checkpoints (mandatory handleAuthCallback on the landing page, the invite branch with its skip-consequence, verifyRequestOrigin at handler top, and the numbered "On failure — stop, don't guess" recovery protocol), but there is no ordered getting-started sequence: dashboard configuration appears near the end, after the code that depends on it. Clear sequence with minor gaps fits anchor 4 rather than anchor 5's explicit checklists for the whole process. | 4 / 5 |
Progressive Disclosure | Good structure: an overview body with two real, clearly signaled, one-level-deep references ("Deep guides for SSR/session hydration and authorization live in references/advanced-patterns.md and references/authorization-and-sessions.md") whose contents match their promises. However, the event-functions section points to references/authorization-and-sessions.md for the "legacy filename convention (identity-signup.ts, etc.)", which that file never mentions — a misdirected pointer that constitutes the minor organization gap of anchor 4 rather than the fully clean navigation of anchor 5. | 4 / 5 |
Total | 17 / 20 Passed |