Content
75%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 that leans on six real per-framework guides for depth while keeping quick config and critical gotchas inline. Its main weakness is redundancy: the trailing house-rules section reiterates rules already stated in the body.
Suggestions
Remove or deduplicate the 'Netlify house rules' entries that restate the body (SPA catch-all removal, env-var redeploy, client-prefix-for-secrets) so each rule appears once; keep only rules that add new info like the Next.js skew-protection version condition (rule 7).
Consolidate the scattered framework version floors (5.12.0+, 5.11.0, 1.132.0+, plugin v2.1.1+, 14.1.4, etc.) into a single 'Version requirements' table or an 'old patterns / deprecated' section so time-sensitive numbers don't dilute the overview.
Move the full inline adapter configuration blocks (SolidStart, React Router middleware/edge setup) that exceed overview depth into their respective references/*.md files, leaving a one-line pointer plus the critical caveat in SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and expert-level with no basic-concept padding, but the 'Netlify house rules' section restates content already in the main body (rules 3, 4, 6 duplicate the SPA catch-all, env-var redeploy, and client-prefix guidance), and version floors are scattered inline rather than isolated in an 'old patterns' section. | 3 / 5 |
Actionability | Pervasive copy-paste-ready guidance — install commands (`npm install -D @sveltejs/adapter-netlify`), config snippets (`astro.config.mjs`, Vite plugin imports), `netlify.toml` blocks, and the Express serverless handler — covering the common cases concretely. | 5 / 5 |
Workflow Clarity | Per-framework setup is sequenced with concrete commands (e.g. SvelteKit install → config → split/edge options), and gotchas are foregrounded; minor gaps are the absence of explicit validate-then-proceed checkpoints, though the operations are not batch/destructive so the workflow cap does not bind. | 4 / 5 |
Progressive Disclosure | Body routes deep work to real one-level-deep reference files (references/astro.md ... vite.md, all present) signaled in the opener, the house rules, and per-section 'Details in references/nextjs.md' notes; the inline per-framework adapter detail (e.g. full SolidStart config, React Router middleware) is borderline but stays at overview level. | 4 / 5 |
Total | 16 / 20 Passed |