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 well-structured, highly actionable reference skill with executable examples and clear sectioning, plus a properly signaled one-level-deep reference file. Its main weakness is redundancy between the main body and the appended house-rules section, which inflates the token budget.
Suggestions
Remove the duplicated 'Netlify house rules' section (lines 135-160) or reduce it to a one-line pointer — its guidance (percent-encoding, blurhash text, local 404, regex escape) is already covered in the body, and the duplication hurts conciseness.
Consolidate the percent-encoding and regex-escape guidance into a single 'Remote source gotchas' callout so the same advice isn't restated in two places.
If the house-rules block is required by the ctx-gen merge process, mark it explicitly as machine-managed so a reader knows it intentionally mirrors the body and can skip it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and token-efficient — tables for params/fit/frameworks, no padded explanations of what images or CDNs are — but the appended 'Netlify house rules' section (lines 135-160) duplicates guidance already in the body (percent-encoding, blurhash text, local 404, regex dot-escape), so it is not fully lean. | 4 / 5 |
Actionability | It provides copy-paste-ready, executable examples across the common cases — a working curl request, netlify.toml remote_images, encodeURIComponent JS, _redirects and _headers snippets — covering the actual operations a user needs. | 5 / 5 |
Workflow Clarity | Sections are clearly organized by task (endpoint params, remote sources, redirects, headers, frameworks, local dev) with a useful diagnostic feedback loop for the local-404 case, but there is no explicit multi-step validated workflow since this is a reference-style skill rather than a destructive/batch process. | 4 / 5 |
Progressive Disclosure | The body is well-sectioned and points the user-uploads pipeline to references/user-uploads.md, a verified one-level-deep file with no nested references; the bulk reference content is mostly appropriately placed, with only minor organization gaps. | 4 / 5 |
Total | 17 / 20 Passed |