netlify-cli-and-deploy

Guide for using the Netlify CLI and deploying sites. Use when installing the CLI, linking sites, deploying (Git-based or manual), managing environment variables, or running local development. Covers netlify dev, netlify deploy, Git vs non-Git workflows, and environment variable management.

1.12x

Quality

93%

Does it follow best practices?

Impact

100%

1.12x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

87%Weight 40%Scale 1-3

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 CLI reference with executable commands throughout and clean section organization. Its main gap is workflow clarity: deploy flows lack explicit validation checkpoints (e.g. verifying a preview deploy before promoting to production), which matters because `--prod` deploys are effectively irreversible.

Suggestions

Add an explicit verify-then-promote checkpoint to the deploy workflow, e.g. 'Run `netlify deploy` (draft) and check the preview URL; only run `netlify deploy --prod` once the preview is confirmed.'

Frame the linking flow's `netlify status` check as a validation step with a clear branch ('If already linked, skip to Deploying; otherwise run `netlify link` or `netlify init`).'

Include a brief post-deploy verification command (e.g. `netlify status` or checking the deploy URL/logs) so the deploy sequence has a closing feedback loop.

Dimension	Reasoning	Score
Conciseness	Tight command blocks with brief inline comments and no padding explaining what Netlify is or how CLIs work; every section earns its place. Not a 2 because there is no unnecessary explanation to trim.	3 / 3
Actionability	Provides fully executable `netlify` commands with real flags (e.g. `netlify env:set API_KEY "value" --context production`, `netlify deploy --prod --dir=dist`) that are copy-paste ready; not a 2 because examples are complete rather than pseudocode.	3 / 3
Workflow Clarity	Sequences are present (check `netlify status` then link; draft `netlify deploy` then `--prod`) but there are no explicit validation checkpoints for the irreversible `--prod` deploy, so checkpoints remain implicit. Not a 3 because no verify-before-promote feedback loop is stated; not a 1 because the steps are clearly ordered.	2 / 3
Progressive Disclosure	Well-organized into clear sections with one clearly-signaled one-level cross-reference ('See the netlify-frameworks skill') and no nested references; the bundle contains only decorative image assets not needed for navigation. Not a 2 because the overview is appropriately self-contained and easy to navigate.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 the skill's purpose, lists concrete capabilities, and provides an explicit 'Use when' trigger covering the main user intents. It is distinguishable from adjacent skills and free of fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'installing the CLI, linking sites, deploying (Git-based or manual), managing environment variables, or running local development' — matching the anchor for listing several specific actions; not a 2 because coverage is comprehensive rather than partial.	3 / 3
Completeness	Explicitly answers 'what' ('Guide for using the Netlify CLI and deploying sites... Covers netlify dev, netlify deploy...') and 'when' via an explicit 'Use when' clause; not a 2 because the trigger guidance is explicit, not merely implied.	3 / 3
Trigger Term Quality	Includes natural terms users would say — 'installing the CLI', 'linking sites', 'deploying', 'environment variables', 'netlify dev', 'netlify deploy' — with good coverage of common variations; not a 2 because both layperson and command-level terms are present.	3 / 3
Distinctiveness Conflict Risk	'Netlify CLI' is a clear niche with distinct deploy/CLI triggers unlikely to fire for unrelated skills; not a 2 because the scope is narrowly bounded to Netlify CLI and deployment rather than overlapping generic categories.	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: openai/plugins
Path: plugins/netlify/skills/netlify-cli-and-deploy/SKILL.md
Commit: 11c74d6

Reviewed: 17 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.