netlify-deploy

The netlify-deploy skill is part of OpenAI’s curated skills collection and gives a Codex agent a structured workflow for deploying web projects to Netlify. According to the provider, it is intended for requests to deploy, host, publish, or link a site or repository on Netlify, including preview and production deployments. It is an instructional skill for an agent, not a Netlify account, not a hosting service, and not an additional deployment API.

Purpose and operating model

The workflow starts by checking whether the Netlify CLI is authenticated. The agent should inspect the local CLI status and, when authentication is missing, guide the operator toward browser-based login. It then checks whether the project is already linked to a Netlify site. If the link is absent, the source recommends examining the project’s Git remote as a possible mapping. When no matching site exists, the documented interactive initialization process can be used to select an account, choose a site name, and establish build settings. This order reduces the risk that an agent silently targets the wrong site or team.

Project checks and deployment choices

Before uploading, the agent should inspect the project structure and verify or install dependencies with the package manager appropriate to that project. An existing netlify.toml is treated as the project’s explicit configuration. When that file is absent, the build command and publish directory must be established from the framework and repository contents. The source gives common patterns for Next.js, Vite-based React projects, and static HTML, while making clear that the project’s actual configuration takes precedence. For a controlled workflow, a preview deployment is the preferred first step for an existing site. Production deployment should be selected only when the user explicitly requests it or the surrounding context clearly authorizes it.

Boundaries and failure handling

The skill cannot repair a broken application and does not prove that a successful build is functionally correct. If login is missing, a site is unlinked, a publish directory cannot be found, or a build fails, the agent should isolate the concrete cause rather than repeatedly attempting deployments. Network failures may require additional permissions from the local execution environment; those permissions must remain visible and must not be bypassed through hidden workarounds. Interactive account selection and site creation remain operator decisions.

Security and data governance

A Netlify deployment changes an external service and may make project files publicly reachable. The agent should therefore confirm the target, branch, build output, and deployment type before production actions whenever the request does not make them explicit. Credentials, session keys, and environment values must never be placed in the skill text, chat, logs, or version control. Secrets should be managed only through the protected configuration of the relevant Netlify project. Before upload, inspect build artifacts, source maps, test fixtures, private configuration, and generated files for accidentally embedded credentials. According to the provider, the CLI can detect project and build context, but that detection is not a substitute for human review. The selected agent and its model provider may process file contents and command output; using a local CLI does not automatically make those data confidential.

Source, license, and professional context

The primary source is the skills/.curated/netlify-deploy directory in OpenAI’s official repository. Its LICENSE.txt identifies Apache-2.0. Netlify’s documentation remains authoritative for current CLI behavior, account permissions, build configuration, and platform-specific details. This skill is useful for repeatable release preparation, preview deployments, and initial site linking. It does not replace a CI/CD strategy or review of privacy, redirects, domains, rollback procedures, and access controls. Current terms and account capabilities should be checked directly with Netlify, so this catalog entry does not state concrete prices.