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

netlify-config

Reference for netlify.toml configuration and site environment variables. Use when configuring build settings, redirects, rewrites, headers, deploy contexts, the `[dev]` block that controls `netlify dev` (command, port, targetPort, framework), or any site-level configuration — and when managing environment variables or secrets with the Netlify CLI, including scoping values to specific deploy contexts. Covers the complete netlify.toml syntax including redirects with splats/conditions, headers, deploy contexts, functions config, edge functions config, and the `[dev]` block (including when `framework` must be `"#custom"` — required when both a custom `command` and `targetPort` are set).

1.14x

Quality

92%

Does it follow best practices?

Impact

92%

1.14x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews 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, actionable netlify.toml reference with executable examples and well-signaled offloading to sibling skills. Its only weakness is mild verbosity in the prose caveats around precedence and scoping.

Suggestions

Tighten the long prose caveats (netlify.toml-vs-UI precedence, redirects/headers being global, build-vs-runtime env scoping) into shorter bullets so the code blocks dominate the token budget.

Consider moving the env-variable runtime-scoping detail and CLI context-scoping nuance into the referenced netlify-functions/frameworks skills, keeping only a one-line pointer here.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste TOML/bash blocks, but several long caveat sentences (netlify.toml-vs-UI precedence, redirects/headers being global, build-vs-runtime env scoping) could be tightened; matches 'mostly efficient but could be tightened'.	2 / 3
Actionability	Fully executable TOML and bash snippets with inline comments and concrete values (redirects with splats, env:set --context, [dev] block); copy-paste ready per the anchor.	3 / 3
Workflow Clarity	This is a config reference, not a multi-step destructive workflow; each single action is unambiguous and rules (e.g. 'first matching rule wins') are stated, satisfying the simple-skill allowance.	3 / 3
Progressive Disclosure	Cleanly sectioned (Build, Redirects, Headers, Deploy Contexts, Env, Functions, Edge, Dev, Plugins, Image CDN) and offloads tangential detail to clearly signaled one-level sibling skills (netlify-deploy, netlify-frameworks, netlify-functions, netlify-image-cdn).	3 / 3
	Total	11 / 12 Passed

Description

100%

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

The description is specific, trigger-rich, and complete, clearly stating both what the skill covers and when to use it. It is somewhat long but each clause adds a concrete capability or trigger rather than fluff.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities — 'build settings, redirects, rewrites, headers, deploy contexts, the [dev] block', env vars, CLI scoping, splats/conditions, edge functions — matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states what ('Reference for netlify.toml configuration and site environment variables') and when ('Use when configuring build settings... or any site-level configuration — and when managing environment variables or secrets with the Netlify CLI').	3 / 3
Trigger Term Quality	Covers natural terms users would say ('netlify.toml', 'build settings', 'redirects, rewrites, headers', 'deploy contexts', 'environment variables or secrets', 'Netlify CLI', 'netlify dev'); not merely technical jargon.	3 / 3
Distinctiveness Conflict Risk	Niche is clearly scoped to netlify.toml/site env config with distinct triggers, unlikely to be confused with or trigger for other skills.	3 / 3
	Total	12 / 12 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: b4ac277

Reviewed: about 13 hours 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.