netlify-deploy

The netlify-deploy skill automates deploying web projects to Netlify using the Netlify CLI invoked through npx (no global install required). It covers the full path from authentication through to a live or preview URL, intelligently detecting project configuration and deployment context along the way. Typical triggers are requests to deploy, host, publish, or link a site or repository on Netlify, including both preview and production deploys.

The workflow proceeds in steps. First it verifies authentication with npx netlify status, guiding the user through npx netlify login (browser-based OAuth) or, as an alternative, setting the NETLIFY_AUTH_TOKEN environment variable. Next it determines whether the project is already linked to a Netlify site; if not, it attempts to link by Git remote using netlify link --git-remote-url, falling back to netlify init to create and configure a new site interactively. It then installs dependencies (npm install, or the appropriate command for yarn or pnpm), and deploys with npx netlify deploy for a preview/draft or npx netlify deploy --prod for production. After deployment it reports the deploy URL, site URL, and where to find logs.

The skill handles netlify.toml automatically when present, and otherwise prompts for the build command and publish directory, with documented framework defaults (Next.js builds to .next, Vite/React to dist, static HTML needs no build). It includes guidance for common errors such as not being logged in, no site linked, build failures, and missing publish directories. Because deploys make outbound network calls, it notes that when sandbox networking blocks them the deploy should be rerun with escalated permissions (sandbox_permissions=require_escalated) and that deploys may take several minutes, so generous timeouts are appropriate. Secrets should never be committed; they belong in the Netlify dashboard environment variables. Bundled reference files cover CLI commands, deployment patterns, and the netlify.toml format.