Content
86%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.
An excellent, highly actionable skill body: copy-paste-ready code, exact commands, and a concentration of Netlify-specific gotchas that are exactly what a skill should supply. The two soft spots are occasional long-winded passages (the disambiguation and CORS sections) and an implicit rather than explicit workflow sequence lacking a final deployed-endpoint verification step.
Suggestions
Tighten the "Netlify MCP means two different things" paragraph and the CORS section by 2-3 sentences each — both carry explanatory framing that could be compressed without losing the actionable core.
Add an explicit end-of-workflow verification step (e.g. after deploy, run a tools/list call against the production URL with the bearer token via MCP Inspector or curl) so the build sequence closes with a concrete checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with genuinely non-obvious, platform-specific facts (WebStandard transport vs Node bridge, the 406 Accept-header gotcha, GET-to-SSE 502 behavior, per-instance state, declarative rate limits, secrets-scanning deploy failure) that Claude cannot know, so nearly every token earns its place. However, the "two different things" disambiguation paragraph and the CORS section carry a few sentences of over-explanation that could be trimmed — matching the 'efficient; minor instances of over-explanation' anchor rather than the lean 5. | 4 / 5 |
Actionability | The server function is complete and copy-paste deployable (imports, handler, config export), the bearer check, rate-limit block, and CORS snippet are concrete, and client connection plus dev/test/deploy are given as exact commands (claude mcp add, mcp.json shape, netlify dev, MCP Inspector). The only placeholders (getItem) are inherently the user's own app logic, so common cases are fully covered. | 5 / 5 |
Workflow Clarity | The document follows a coherent build order (decide auth model → stack → server function → tools → auth → safety → rate limiting → clients → dev/deploy) with real checkpoints and error-recovery feedback: test via MCP Inspector, 406 means fix the client's Accept header, a browser CORS console error has a specific fix, Identity must be tested on a deploy preview. It falls short of the 5 anchor because the sequence is topical rather than explicitly stepped, and there is no final 'verify the deployed endpoint end-to-end' checkpoint. | 4 / 5 |
Progressive Disclosure | The body stays at overview level while deep material (full per-user key schema/hashing/revocation, the complete three-step upload flow, the full client matrix and OAuth deep-dive) lives in three references, each one level deep, clearly signaled inline at the point of need and again in a closing index — and all three referenced files exist in references/. | 5 / 5 |
Total | 18 / 20 Passed |