Content
40%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.
The body is well-sectioned and free of concept-explanation padding, but it is a skeleton: no code, no ordered workflow, no validation guidance, and anti-patterns without correct alternatives. An auth integration skill's core value (executable client/middleware/callback code) is entirely absent, leaving only high-level hints like "Use @supabase/ssr".
Suggestions
Add executable code to the Patterns sections: a @supabase/ssr browser/server client factory, the middleware.ts session-refresh snippet, and the /auth/callback route handler — copy-paste ready rather than one-line descriptions.
Expand each Anti-Pattern into prohibition + correct alternative (e.g., "❌ getSession in Server Components → use getUser() in Server Components because getSession does not revalidate the JWT"), since bare headers give no actionable guidance.
Sequence the patterns as an ordered workflow (env setup → client factories → middleware → callback route → protected routes) with verification checkpoints (e.g., confirm session cookies are set, confirm redirect on expired token), and delete the filler Capabilities/Requirements/When-to-Use sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short (~54 lines) and avoids explaining concepts Claude already knows, but contains padded zero-value sections: "Capabilities" and "Requirements" are bare kebab-case tag lists, and "This skill is applicable to execute the workflow or actions described in the overview" is circular filler. Mostly efficient but could be tightened — anchor 3. | 3 / 5 |
Actionability | The Patterns sections are one-line topic stubs with zero code ("Create properly configured Supabase clients for different contexts", "Handle OAuth callback and exchange code for session") and the Anti-Patterns name prohibitions ("❌ Storing Tokens Manually") without correct alternatives. The only concrete guidance is high-level ("Use @supabase/ssr for App Router integration", "cookie-based session flow") — anchor 2: minimal concrete guidance, missing specific steps. | 2 / 5 |
Workflow Clarity | There is no ordered workflow at all: client setup, middleware, and callback appear as unordered pattern categories with no sequence, no environment/setup step, and no validation checkpoints for an inherently multi-step integration. A rough progression is only implied, matching anchor 2 (rough sequence, steps poorly defined, validation absent) rather than 1. | 2 / 5 |
Progressive Disclosure | No bundle files exist and the body has clear, well-organized sections that are easy to navigate, which per the simple-skill note can score highly. Held at anchor 4 rather than 5 because the Patterns and Anti-Patterns sections are stubs whose natural content (executable auth code, correct alternatives) is substantial enough to warrant either inline content or one-level-deep referenced files. | 4 / 5 |
Total | 11 / 20 Passed |