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.
98
100%
Does it follow best practices?
Impact
92%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly identifies its domain (netlify.toml configuration), lists comprehensive specific capabilities, and includes an explicit 'Use when' clause with natural trigger terms. It uses proper third-person voice and is concise without being vague. The description would effectively help Claude distinguish this skill from others in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and configuration areas: build settings, redirects, rewrites, headers, deploy contexts, environment variables, splats/conditions, functions config, and edge functions config. | 3 / 3 |
Completeness | Clearly answers both what ('Reference for netlify.toml configuration' covering specific syntax areas) and when ('Use when configuring build settings, redirects, rewrites, headers, deploy contexts, environment variables, or any site-level configuration'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'netlify.toml', 'redirects', 'rewrites', 'headers', 'deploy contexts', 'environment variables', 'edge functions', 'build settings'. These are terms developers naturally use when working with Netlify configuration. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'netlify.toml' as a clear niche identifier. The specific Netlify-related terminology makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent configuration reference skill. It is highly concise, fully actionable with copy-paste ready TOML examples, well-structured with clear section headings, and includes appropriate cross-references to related skills. The safety callout about not putting secrets in netlify.toml and the note about redirect rule ordering demonstrate good awareness of common pitfalls.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and example-driven. No unnecessary explanations of what Netlify is or how TOML works. Comments within code blocks serve as inline documentation without bloat. The only prose lines are genuinely useful caveats (rule order, secrets warning, CDN-only headers). | 3 / 3 |
Actionability | All examples are copy-paste ready TOML configurations covering the full range of netlify.toml features. Each section provides concrete, executable configuration snippets with realistic values and inline comments explaining key fields. | 3 / 3 |
Workflow Clarity | This is a reference/configuration skill rather than a multi-step workflow, so explicit validation checkpoints are less critical. The content is clearly sequenced from basic (build settings) to advanced (plugins, image CDN), and important ordering constraints (redirect rule order) and safety notes (no secrets in toml) are explicitly called out. | 3 / 3 |
Progressive Disclosure | Content is well-organized into clearly labeled sections that serve as a comprehensive but scannable reference. Cross-references to related skills (netlify-cli-and-deploy, netlify-image-cdn) are appropriately signaled without nesting. The skill stays at the right level of detail for a configuration reference without needing separate files. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- netlify/context-and-tools
- Commit
cffaf74
- 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.