Content
71%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 dense, highly actionable reference: nearly all code is copy-paste executable, limits and gotchas are exact, and local-testing checkpoints are embedded at the risky spots. The two real weaknesses are the ~55-line duplicated 'house rules' section (which also contains maintainer-only meta rules) and the absence of any progressive disclosure — a 360-line monolith with the event-handler, region, and legacy/Go references all inlined where separate reference files belong.
Suggestions
Remove the appended 'Netlify house rules' section from the rendered body — its operative rules (mocked geo/ip, region/memory admonitions, 4 KB env-var cap, [[headers]] scope) are already stated inline at their point of use, and the merge artifact plus authoring rules (10–15) waste ~55 lines of context.
Split the platform-event handler reference (deploy/identity/form event tables), the Legacy/Go section, and the region airport-code list into references/ files linked one level deep from short summary sections, giving the main file a quick-start-to-advanced gradient.
Add an explicit validate-then-ship step to the Local testing section (e.g. 'run netlify functions:invoke and confirm on a deploy preview before declaring done') to close the local-mock vs. production gap that the geo and bundled-files warnings each describe separately.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly dense, fact-only reference material (terse bullets, tables like the Identity-events deny/mutate matrix, exact limits '60s execution, 20 MB response'), but the appended 'Netlify house rules' section duplicates content already stated inline — e.g. rules 5–9 restate the mocked 'context.geo'/'context.ip' warning, the region/memory admonitions, the '[[headers]]' rule, and the ~4 KB env-var limit verbatim, and rules 10–15 are instructions to skill authors about what the body must contain, not guidance for using the skill. That is ~55 lines of unnecessary duplication, matching the score-3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened'); score 4 would require only minor trimming, but this duplication is a whole padded section, so score 4 overstates it, and score 2's pervasive explainer padding understates how lean the rest is. | 3 / 5 |
Actionability | Nearly every section is copy-paste-ready executable code with exact commands and values: the minimal handler ('export default async (req: Request, context: Context) => new Response("Hello, world!")'), path routing with 'path: "/travel-guide/:city/:country"', purgeCache, the OpenAI streaming proxy, background and scheduled config blocks, and netlify.toml snippets. Concrete commands and exact limits are given throughout ('netlify dev --geo=mock --country=DE', 'netlify functions:invoke <name>'). This matches the score-5 anchor ('Fully executable; copy-paste ready code or commands; specific examples cover the common cases'); the only placeholders (e.g. 'messages: [/* ... */]' in the streaming proxy) are inputs the user must supply, not missing detail, so score 4's 'minor gaps' does not apply. | 5 / 5 |
Workflow Clarity | The write → test → deploy sequence is present with concrete checkpoints: 'verify on a real deploy' after exercising mocked geo branches locally, 'Scheduled functions don't fire on a schedule locally — invoke once with netlify functions:invoke <name>', 'After changing region, redeploy', and 'then redeploy' after the runtime override. This matches the score-4 anchor ('clear sequence with most checkpoints present; minor validation gaps'). Score 5 is not earned because there is no explicit validate-then-proceed loop for the local-to-production gap beyond scattered ⚠️ notes (e.g. the bundled-files ENOENT trap has a workaround but no 'confirm in production' step), and score 3 would ignore that checkpoints are consistently embedded at each risky transition. | 4 / 5 |
Progressive Disclosure | The body has clear section headers and strong internal organization, but there are no bundle files at all — references/, scripts/, assets/ are absent — so everything is inlined in one ~360-line file. Content that clearly belongs one level deep is inline: the Legacy/Go Lambda-compat migration, the full platform-event handler reference (deploy/identity/form event tables), and the airport-code region list. This matches the score-3 anchor ('some structure... content that should be separate is inline') rather than score 4 ('most content is appropriately placed'), since none of the reference material is split out; score 2 is avoided because headers make navigation easy and nothing is buried. | 3 / 5 |
Total | 15 / 20 Passed |