Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A high-quality operational skill: executable commands, clear deploy workflows with strong error-recovery discipline, and well-structured progressive disclosure into verified reference files. The main weakness is token efficiency — a redundant commands table and some lengthy gotcha prose could be trimmed without losing clarity.
Suggestions
Remove or slim the "Useful Commands" table: `netlify deploy`, `netlify deploy --prod`, `netlify deploy --dir`, and `netlify logs` are already demonstrated in the Deploying and Logs sections, so the table mostly repeats them; keep only the genuinely new entries (`netlify build`, `netlify clone`, `netlify open`).
Tighten the longer gotcha paragraphs (e.g. the manual `--prod`-replaced-by-Git and monorepo config-discovery explanations) to their core rule plus the one consequence, preserving the operational punchline without the surrounding narrative.
The "Deploy URLs are public by link" section could be shortened to the rule plus the protection pointer to the netlify-access-control skill, cutting the explanatory middle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body assumes Claude's competence (no basic-concept filler) and is mostly high-signal, but the "Useful Commands" table duplicates commands already shown in the Deploying and Logs sections and several gotcha paragraphs run long, so it could be tightened. It is not a 3 because not every token earns its place. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready commands and exact env-var/flag names throughout — `netlify deploy --prod`, `netlify deploy --dir=dist`, `netlify link --git-remote-url`, `NETLIFY_SITE_ID`, `SECRETS_SCAN_OMIT_KEYS`, `netlify logs --source functions --function my-fn` — with no pseudocode. | 3 / 3 |
Workflow Clarity | Clear install→authenticate→link→deploy sequencing with explicit validation and feedback loops — run the build to find the real output dir before setting `publish`, get the exact error from the deploy log then address the cause, and the "surface and stop" discipline for failed deploys and secrets-scan failures. | 3 / 3 |
Progressive Disclosure | The body is a well-organized overview that defers detail to one-level-deep, clearly signaled references (cli-commands.md, deployment-patterns.md, netlify-toml.md — all present on disk) and routes config/frameworks/access-control to sibling skills, with easy navigation via the References section. | 3 / 3 |
Total | 11 / 12 Passed |