Content
73%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.
The body is a dense, highly actionable routing guide — exact UI paths, plan gating, footguns, and executable code — with a clear disambiguation-first workflow and a properly signaled one-level reference file. Its main defect is redundancy: the merged 'Netlify house rules' section at the end duplicates most of the guidance already given, inflating token cost without adding instruction value.
Suggestions
Deduplicate the trailing 'Netlify house rules (access-control)' section: every rule that restates the no-API boundary, double-login/context.user guidance, netlify-identity routing, Reviewer remedy, or who-can-change-settings list already appears in the body above — keep a single statement of each.
If the house-rules block must remain for ctx-gen merging, move it to a reference file (like two-layer-pattern.md) or collapse it to a short pointer so SKILL.md carries the guidance once.
Consolidate plan-gating details that currently appear in both the decision guide and the 'Constraints & footguns' section (e.g. 'Password not available on Credit-based Free/Personal' is stated three times) into the constraints section alone.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Roughly 60 of the ~155 body lines are a merged "Netlify house rules" section that restates content already delivered above it nearly verbatim — the no-API/never-curl rule, the double-login no-bridge guidance, the context.user behavior, the netlify-identity routing, the internal-app single-sign-in decision, the Reviewer remedy, and the who-can-change-settings list all appear twice. This is several unnecessary duplicated sections (anchor 2), not merely 'some' tightening (anchor 3), even though the non-duplicated material itself is lean and assumes Claude's competence. | 2 / 5 |
Actionability | Guidance is fully executable for a no-API domain: exact dashboard click paths with templated URLs (e.g. "Project configuration > General > Visitor access > Project visibility — https://app.netlify.com/projects/{site_name}/configuration/general/#project-visibility"), plan-gated options for every recommendation, a copy-paste-ready JS snippet for the 401/refresh symptom, and doc URLs for out-of-scope specifics. Not level 4, as there are no material gaps for the common cases. | 5 / 5 |
Workflow Clarity | The routing workflow is unambiguous and correctly ordered: "First: disambiguate 'auth' — three unrelated layers", then a decision guide mapping each user intent to a specific layer, then exact UI paths, then constraints/footguns that act as checkpoints (e.g. "Free/Personal have no Password option — use Private", "Internal Builders cannot make a project public"). As a simple single-purpose skill with no destructive or batch operations, its single action — pick the layer — is unambiguous, meeting the level-5 exception. | 5 / 5 |
Progressive Disclosure | The single bundle file, references/two-layer-pattern.md, is real, one level deep, and well-signaled with its purpose stated inline ("For the combined layered pattern and its tradeoffs, see references/two-layer-pattern.md"), and headers make the body navigable. It falls short of level 5 because the trailing duplicated house-rules block and some long inline constraint paragraphs (e.g. plan-gating details repeated across sections) could be organized or split better, leaving minor structure gaps. | 4 / 5 |
Total | 16 / 20 Passed |