Name: netlify-config
Rating: 70.39999999999999 (1 reviews)
Author: netlify

netlify-config

Configure Netlify projects via netlify.toml and the _headers/_redirects files — covering build settings and deploy contexts alongside environment variables/scopes and the Secrets Controller plus redirect/rewrite/proxy and custom-header rules. Use when setting a build command or publish directory, adding redirect or rewrite or proxy rules, configuring custom headers or basic auth, setting or scoping environment variables and secrets, wiring up a monorepo or SPA fallback, or skipping unnecessary builds. Reach for this whenever you touch netlify.toml or ask "why is my env var undefined in a function" or "how do I redirect this path".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, actionable Netlify config reference with dense executable examples and high-value footguns, but it is a monolithic inline doc with no progressive disclosure to bundle files and no structured validation workflow for production-affecting changes. The duplicated house-rules section adds minor redundancy.

Suggestions

Remove or deduplicate the trailing 'Netlify house rules (config)' section — its four items are already covered in the Footguns section, so it adds tokens without new information.

Split the long reference tables (build variables list, read-only build metadata, env-var scopes/limits) into a bundled REFERENCE.md and link to it one level deep, keeping SKILL.md as a lean overview.

Add an explicit validation/checkpoint workflow for production-affecting changes — e.g. after editing netlify.toml redirects or secrets, note how to verify on a deploy preview before promoting (validate → fix → redeploy).

Dimension	Reasoning	Score
Conciseness	Mostly lean and information-dense with Netlify-specific footguns Claude cannot reliably infer, but the trailing 'Netlify house rules (config)' section (lines 285-302) duplicates four items already in the Footguns section, adding redundancy that could be trimmed.	4 / 5
Actionability	Copy-paste-ready executable examples throughout — concrete `netlify env:set ... --secret` CLI commands, full TOML blocks for redirects/headers/functions, `_redirects` syntax, and a Node.js ignore-build script — covering the common cases.	5 / 5
Workflow Clarity	Processes (env var setup, redirect config, secret marking) are described but not sequenced into a guided workflow with validation checkpoints; for config changes affecting production deploys there is no explicit validate→fix→retry loop, which caps this dimension.	3 / 5
Progressive Disclosure	No bundle files exist and all ~303 lines are inlined in SKILL.md; section headers are clear and navigation is reasonable, but reference-table material (env var lists, build metadata) that could live in separate files is inlined with no one-level-deep pointers.	3 / 5
	Total	15 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: third-person, comprehensive in concrete capabilities, rich in natural trigger terms including example user questions, and explicitly pairing 'what' with 'when'. Minimal conflict risk given the tightly scoped Netlify-config niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the full config surface — 'build settings and deploy contexts', 'environment variables/scopes and the Secrets Controller', 'redirect/rewrite/proxy and custom-header rules' — giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both 'what' ('Configure Netlify projects via netlify.toml and the _headers/_redirects files — covering...') and 'when' ('Use when setting a build command... Reach for this whenever you touch netlify.toml...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural terms users actually say — 'build command', 'publish directory', 'redirect', 'rewrite', 'proxy', 'custom headers', 'basic auth', 'monorepo', 'SPA fallback', plus file names (netlify.toml, _headers/_redirects) and verbatim user questions like 'why is my env var undefined in a function'.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear Netlify-config niche with distinct triggers (netlify.toml, _headers, _redirects, Secrets Controller); unlikely to fire for non-Netlify skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: netlify/context-and-tools
Path: codex/skills/netlify-config/SKILL.md
Commit: 47848e2

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.