Netlify Deployment Assistant
Connect, preview, and publish web projects on Netlify through the Netlify CLI.
The documentation requires authentication checks, defaults to preview deployment, and warns against committing secrets. However, npx/npm introduce dynamic external dependencies, npm install may run project scripts, production deployment lacks explicit second confirmation and rollback guidance, and the data flow is not fully disclosed, so points are deducted.
The main workflow, common errors, and some recovery steps are reasonably coherent. However, there are no tests, version pinning, or execution evidence; framework detection, CLI behavior, and listed exit codes cannot be confirmed statically, so the score remains conservative under the static ceiling.
Triggers, authentication, site linking, preview, and production scenarios are clearly described, with coverage for several frameworks and monorepos. Non-fit boundaries, input requirements, and Chinese-language support are limited, while core deployment depends on Netlify, GitHub, npm, and other overseas network services that may be difficult to reach from mainland China, so points are deducted.
The skill uses a main guide plus progressive reference files, with useful examples and troubleshooting. However, the individual skill license is unknown, and versioning, changelog, maintenance ownership, and update procedures are not stated; some assumptions also depend on interactive CLI behavior, so points are deducted.
It provides a directly usable deployment workflow for common web projects, and preview-first guidance has practical value. However, artifacts, build settings, and current CLI compatibility are unverified, and production cases still require user judgment and fixes; under static review the score is capped at 7.
Specific commands, expected outputs, error handling, and official documentation links provide limited auditability. There is no committed test suite, CI execution evidence, or independent corroboration, so the conclusion is based mainly on static documentation and points are deducted.
- Production deployment creates material external state changes, but the skill does not require explicit confirmation, a preflight checklist, or a rollback procedure.
- npx, npm install, project build scripts, and Netlify plugins may download or execute third-party code; dependencies and plugin provenance should be reviewed and pinned.
- Netlify, GitHub, npm, and browser-based OAuth require external network access and may fail in mainland-China environments.
- The documentation provides no current CLI version, test results, license, or explicit maintenance commitment.
What it does & when to use it
This Agent Skill deploys web projects with the Netlify CLI. It checks authentication, detects project configuration and framework context, and attempts to link an existing site or create a new one. It supports preview and production deployments and provides guidance for dependencies, build settings, and common failures. It is part of the deprecated openai/skills repository; the README points to the OpenAI Plugins repository for current examples.
Runs npx netlify status to check authentication and site-link status; when needed, it guides the user through npx netlify login or NETLIFY_AUTH_TOKEN setup. It can inspect a Git remote and run npx netlify link --git-remote-url or npx netlify init to link or create a site, and it recommends npm, yarn, or pnpm dependency installation as appropriate. It runs npx netlify deploy for a preview deployment or npx netlify deploy --prod for production, then reports deployment URLs, the site URL, and log access. If netlify.toml is present, the CLI uses it; otherwise, the CLI prompts for build and publish settings.
- A frontend developer needs a unique preview URL to test recent website changes.
- A project owner explicitly wants an existing web project published to Netlify production.
- A developer has a Git-based project that is not yet linked to a Netlify site.
- A maintainer needs to create a Netlify site interactively and configure its build settings.
Pros & cons
- Covers authentication checks, site linking or creation, dependency preparation, and deployment reporting.
- Supports both preview and production deployments.
- Can try to link an existing site through the project's Git remote.
- Includes guidance for netlify.toml, environment variables, and common deployment errors.
- Requires an active Netlify login session or NETLIFY_AUTH_TOKEN.
- Requires outbound network access; sandbox restrictions may require escalated network permissions.
- Without netlify.toml, build and publish settings require interactive input.
- The supplied material does not document a test suite, verified platform coverage, or the individual skill's license contents.
- The parent openai/skills repository is marked deprecated in the README.
How to install
The skill is located at skills/.curated/netlify-deploy/. The README says curated skills can be installed in Codex with: $skill-installer netlify-deploy. Restart Codex after installation. The README also marks this repository as deprecated and directs readers to the OpenAI Plugins repository for current examples.
How to use
After installation, use a request such as “Deploy the current web project to Netlify” or “Create a Netlify preview deployment for this project.” The typical flow is npx netlify status, npx netlify login if necessary, dependency installation, and npx netlify deploy; an explicit production request uses npx netlify deploy --prod. A netlify.toml file is used automatically; without one, the CLI asks for the build command and publish directory.