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: nearly every line carries Netlify-specific, non-inferable facts, and the executable examples cover the realistic use cases end to end. The main weaknesses are duplication between the footguns section and the appended house rules, and the absence of an explicit end-to-end workflow or bundle split for the API-detail material.
Suggestions
Deduplicate the house-rules section against the footguns list: rules 2, 3, 5, and 7 restate the path "/*" warning, the no-route silent no-op, the cache: manual both-parts requirement, and context.user semantics already covered above — keep only the genuinely new guidance (framework-adapter-first, edge vs serverless workload shape, never trust client-sent identity headers).
Add a short numbered workflow at the top (check framework adapter → write file with default export + config → declare route inline or in netlify.toml → netlify dev with --geo mock to verify → deploy) so the reference sections hang off an explicit sequence with validation checkpoints.
Move the Context property table, Web APIs, and module-loading lists into a references/ file (e.g. references/context-api.md) linked from the body, keeping SKILL.md as a leaner overview and enabling one-level-deep progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and fact-bearing (footgun list, config tables, limits, terse code) with no padding of concepts Claude already knows, but the trailing house-rules section re-states several facts already covered above (no-route silent no-op, cache: manual + headers both-or-neither, path "/*" intercepts everything, context.user semantics), which is more than a minor trim. | 4 / 5 |
Actionability | Ten complete, copy-paste-ready examples (hello, redirect/rewrite, middleware transform, conditional request, body replay, user gate, waitUntil, streaming SSR, caching) plus concrete CLI flags (--edge-inspect, --geo=mock --country=DE) and a worked ordering trace ("A request to /admin runs auth, then common, then injector") fully cover the common cases. | 5 / 5 |
Workflow Clarity | The core path is unambiguous (template → declare route inline or in toml → netlify dev → deploy) with real checkpoints (check the framework adapter first, check the route first when a function does nothing, fail-closed onError guidance for auth), but the sections read as reference material with no explicit end-to-end step sequence tying them together, so it sits between the 4 and 5 anchors rather than clearly at 5. | 4 / 5 |
Progressive Disclosure | A single self-contained file with well-organized sections and external doc links for deeper material (API, declarations, limits, examples). However, no bundle files exist and API-reference-like content (the full Context table, Web APIs and module lists, and ~40 lines of house rules) is inlined in the entry file, which is a minor organization gap rather than the clear split of the 5 anchor. | 4 / 5 |
Total | 17 / 20 Passed |