Content
72%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 with excellent executable examples and minimal over-explanation, but it is a monolithic single file with no progressive disclosure into bundled references, and it lacks explicit validation feedback loops for its batch/destructive use cases.
Suggestions
Split the config reference, the Legacy/Go section, and the 'Netlify house rules' into separate reference files linked one level deep from SKILL.md to improve progressive disclosure.
Add explicit validate-fix-retry checkpoints for batch/destructive operations (e.g., after invoking a scheduled or background function locally, verify the side effect before deploying).
De-duplicate the 'Netlify house rules' section against the body — each rule already appears inline above, so consolidate to remove the repetition and recover token budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Largely lean and reference-style with no padding explaining concepts Claude already knows, but the trailing 'Netlify house rules' section restates several points already made in the body (geo mocking, memory/vcpu, region, 4 KB env limit), which is duplication that could be trimmed. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready code examples cover the common cases — minimal handler, path routing, integrations, streaming, background, scheduled, and event handlers — each with complete config and imports. | 5 / 5 |
Workflow Clarity | Sections are well organized and the 'Local testing & deploy' section gives a rough sequence, but there are no explicit multi-step validation checkpoints or validate-fix-retry feedback loops for the batch/destructive operations the skill describes (background jobs, batch processing), which caps this dimension. | 3 / 5 |
Progressive Disclosure | Section headers are clear and navigation within the file is easy, but for a ~300-line skill the content is monolithic with no one-level-deep external references — material like the full config reference, house rules, and legacy/Go guidance that could live in separate files is all inlined. | 3 / 5 |
Total | 15 / 20 Passed |