CtrlK
BlogDocsLog inGet started
Tessl Logo

netlify-config

Reference for netlify.toml configuration. Use when configuring build settings, redirects, rewrites, headers, deploy contexts, environment variables, or any site-level configuration. Covers the complete netlify.toml syntax including redirects with splats/conditions, headers, deploy contexts, functions config, and edge functions config.

96

1.03x
Quality

96%

Does it follow best practices?

Impact

92%

1.03x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is netlify-config in netlify/context-and-tools

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

A lean, highly actionable netlify.toml syntax reference with copy-paste-ready examples and useful gotchas, organized into clear sections. Its only real gap is progressive disclosure: all content is inline with no detail files, and the bundled asset images are not referenced from the body.

Suggestions

Split the larger or more advanced sections (edge functions, Image CDN, plugins, deploy contexts) into one-level-deep reference files and link to them from a concise overview in SKILL.md, so the main file stays a navigable entry point.

Either reference the bundled assets (netlify.png / netlify-small.svg) where relevant in the body, or remove them if they are purely decorative, so the bundle structure is actually used and signaled.

Cross-link the sibling skills already mentioned (netlify-cli-and-deploy, netlify-image-cdn) as explicit 'See X skill for...' pointers in their respective sections to strengthen navigation.

DimensionReasoningScore

Conciseness

The body is lean TOML reference material with minimal prose; the few prose lines ('Rule order matters', 'Headers apply only to files served from Netlify's CDN', 'Do not put secrets in netlify.toml') are non-obvious gotchas that earn their tokens rather than concept re-explanation.

3 / 3

Actionability

Every section provides concrete, copy-paste-ready executable TOML — redirects with splats/conditions, headers, deploy contexts, functions, edge functions, dev server, plugins, image CDN — with specific values and inline comments.

3 / 3

Workflow Clarity

This is a single-purpose config reference, well-organized into clearly sequenced sections, so the simple-skill allowance applies; configuring netlify.toml is not a destructive/batch operation requiring validation checkpoints, and 'Rule order matters' serves as a useful ordering cue.

3 / 3

Progressive Disclosure

The body is well-organized into sections but is entirely inline in one ~170-line file with no one-level-deep reference files (references/ and scripts/ are empty), and the asset bundle files (netlify.png, netlify-small.svg) are present but never signaled or referenced. It exceeds the 50-line simple-skill exemption, so a 3 is not justified despite good section structure.

2 / 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.

A strong, third-person description that concisely states its reference purpose, lists concrete configuration domains, and provides an explicit 'Use when' trigger with good natural keyword coverage. It is distinctively Netlify-scoped and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete configuration tasks — 'build settings, redirects, rewrites, headers, deploy contexts, environment variables' — plus the full syntax scope (splats/conditions, functions, edge functions), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It states what ('Reference for netlify.toml configuration') and an explicit 'Use when configuring...' trigger clause, satisfying the 'clearly answers both what AND when with explicit triggers' anchor; not a 2 because the when is explicit, not merely implied.

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered: 'netlify.toml', 'redirects', 'headers', 'build settings', 'environment variables', and 'deploy contexts', matching the 'good coverage of natural terms users would say' anchor rather than the narrower score-2 set.

3 / 3

Distinctiveness Conflict Risk

The scope is tightly scoped to netlify.toml site configuration with Netlify-specific triggers, giving it a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
Reviewed

Table of Contents

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.