Content
78%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 overview with excellent reference structure: nearly every line is a non-obvious platform fact, command, or configuration example, and detail is correctly split into well-signaled one-level-deep references. The main weakness is token efficiency — the appended house-rules section duplicates warnings already stated in the body, and some inlined detail (button URL variants, version pins) could be consolidated or moved out.
Suggestions
Deduplicate the trailing 'Netlify house rules' section: rules 1, 2, and 5–9 restate warnings already present in the body (no-rollbacks, .gitignore, secrets scanning, manual --prod, button template root), so trim it to only net-new conventions to save ~30 lines of tokens.
Move the Deploy-to-Netlify button URL parameter variants and [template] config block into a reference file (e.g. references/deployment-patterns.md or a new button reference), keeping only the basic markdown snippet and the root-config caveat inline.
Consolidate version-sensitive notes (Netlify CLI 23.11.0+, Astro 5.15.0+) into a single dedicated section so time-sensitive figures age in one place instead of being scattered inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Most of the body is dense with non-obvious, Netlify-specific facts that earn their tokens (atomic deploys, files-per-directory limit, X-Robots-Tag behavior, skew-protection constraints), but the trailing "Netlify house rules" section (~36 lines) restates warnings already made in the body — no-rollback, .gitignore, secrets scanning, manual --prod warning, button template root rule all appear twice. That duplication, plus inline version pins ("Netlify CLI 23.11.0+", "Astro 5.15.0+"), means the content could be noticeably tightened, fitting 'mostly efficient but could be tightened' rather than 'minor instances that could be trimmed'. | 3 / 5 |
Actionability | Guidance is fully executable throughout: copy-paste-ready CLI commands ("netlify deploy --prod", "npm update -g netlify-cli"), complete netlify.toml context examples including the double-bracket plugins syntax, a ready-to-use Deploy button markdown snippet with concrete URL parameter variants, and exact dashboard navigation paths ("Project configuration > Developer settings > Continuous deployment > Branches and deploy contexts > Configure"). Specific examples cover the common cases, matching the top anchor. | 5 / 5 |
Workflow Clarity | The body progresses coherently from creation paths to deploy management to failure handling, and risky operations carry explicit warnings with mitigations (manual --prod is flagged with the lock suggestion, deletion is flagged as permanent, secrets-scan failures get scoped remediation). It falls short of the top anchor because there is no explicit validate→fix→retry loop in the body itself — preview-before-production and troubleshooting feedback loops live in the references rather than the SKILL.md. | 4 / 5 |
Progressive Disclosure | The body is an overview that pushes depth into three real, one-level-deep reference files, each clearly signaled at the exact point of need ("See references/netlify-toml.md for the full context precedence rules", "See references/cli-commands.md for the full CLI surface and flags"). All three referenced files exist in the bundle, none of them nest further into additional files within this skill (they point onward to separate skills, not nested references), and navigation is easy — matching the top anchor. | 5 / 5 |
Total | 17 / 20 Passed |