openai-netlify-deploy — Claude Code skill: what it does
openai-netlify-deploy — a Claude skill that runs a Netlify deploy end to end: sign-in check, site linking or creation, dependency install, then a preview or production release.
Apache-2.0 ★ 540 updated 2026-07-14
/plugin marketplace add trailofbits/skills-curated
/plugin install openai-netlify-deploy@skills-curatedWhat openai-netlify-deploy does
The skill walks Claude through shipping a web project to Netlify with the Netlify CLI, launched via npx so nothing is installed globally. It opens with a sign-in check (npx netlify status) and a look at whether this folder is already tied to a site.
When there is no link, it reads the origin git remote and tries npx netlify link --git-remote-url <REMOTE_URL>. If no such site exists yet, npx netlify init creates one and asks about the team, the site name and build settings. Dependencies go in, the build runs, and the release is either npx netlify deploy for a preview URL or npx netlify deploy --prod for the live one.
Build command and publish directory come from netlify.toml; with no such file the skill proposes values based on the framework it finds in package.json. Auth is the hard stop — a browser login or a NETLIFY_AUTH_TOKEN in the environment, otherwise the deploy step fails. Three reference files (references/cli-commands.md, references/deployment-patterns.md, references/netlify-toml.md) load when needed, and the allowed tools are Bash, Read, Grep, Glob, Write, Edit.
What it helps with
- push a preview build to Netlify and get a URL to test
- link a local repo to a site that already exists
- create a new Netlify site from the project folder
- trace a failed build back to the build command or publish directory
- promote a checked preview to production
Example prompts for the agent
- Deploy this project to Netlify as a preview and give me the URL.
- Link this repo to our existing Netlify site, then ship it to production.
- Check whether I'm logged into Netlify and take me through
npx netlify loginif not.
How to install openai-netlify-deploy
1Plugin marketplace
/plugin marketplace add trailofbits/skills-curated/plugin install openai-netlify-deploy@skills-curatedThis installs the whole openai-netlify-deploy plugin with all its skills
2Skills CLI (Vercel)
npx skills add trailofbits/skills-curated --skill openai-netlify-deploy -a claude-code3Manually: put the files in place
~/.claude/skills/openai-netlify-deploy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/openai-netlify-deploy/
1Skills CLI (Vercel)
npx skills add trailofbits/skills-curated --skill openai-netlify-deploy -a codex2Manually: put the files in place
.agents/skills/openai-netlify-deploy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add trailofbits/skills-curated --skill openai-netlify-deploy -a cursor2Manually: put the files in place
.cursor/skills/openai-netlify-deploy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install trailofbits/skills-curated plugins/openai-netlify-deploy/skills/openai-netlify-deploy2Manually: put the files in place
.github/skills/openai-netlify-deploy/SKILL.md1Skills CLI (Vercel)
npx skills add trailofbits/skills-curated --skill openai-netlify-deploy -a gemini-cli2Platform CLI
gemini skills install https://github.com/trailofbits/skills-curated --path plugins/openai-netlify-deploy/skills/openai-netlify-deployManually: put the files in place
.devin/skills/openai-netlify-deploy/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about openai-netlify-deploy
How do I install Anthropic-netlify-deploy in Claude Code?
Through the marketplace: first /plugin marketplace add trailofbits/skills-curated, then /plugin install openai-netlify-deploy@skills-curated.
What does Anthropic-netlify-deploy do?
It carries a web project through a Netlify deploy with npx netlify: checks the login, links or creates the site, installs dependencies, then publishes a preview or a production build.
What do I need before using it?
A Netlify account with an active session, either through npx netlify login in the browser or a NETLIFY_AUTH_TOKEN variable. The current directory also has to hold a real web project.
Source text
SKILL.md · Apache-2.0
--- name: openai-netlify-deploy description: Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys. Originally from OpenAI's curated skills catalog. allowed-tools: - Bash - Read - Grep - Glob - Write - Edit --- # Netlify Deployment Skill Deploy web projects to Netlify using the Netlify CLI with intelligent detection of project configuration and deployment context. ## Overview This skill automates Netlify deployments by: - Verifying Netlify CLI authentication - Detecting project configuration and framework - Linking to existing sites or creating new ones - Deploying to production or preview environments ## Prerequisites - **Netlify CLI**: Installed via npx (no global install required) - **Authentication**: Netlify account with active login session - **Project**: Valid web project in current directory - The deployment might take a few minutes. Use appropriate timeout values. ## Authentication Pattern The skill uses the **pre-authenticated Netlify CLI** approach: 1. Check authentication status with `npx netlify status` 2. If not authenticated, guide user through `npx netlify login` 3. Fail gracefully if authentication cannot be established Authentication uses either: - **Browser-based OAuth** (primary): `netlify login` opens browser for authentication - **API Key** (alternative): Set `NETLIFY_AUTH_TOKEN` environment variable ## Workflow ### 1. Verify Netlify CLI Authentication Check if the user is logged into Netlify: ```bash npx netlify status ``` **Expected output patterns**: - ✅ Authenticated: Shows logged-in user email and site link status - ❌ Not authenticated: "Not logged into any site" or authentication error **If not authenticated**, guide the user: ```bash npx netlify login ``` This opens a browser window for OAuth authentication. Wait for user to complete login, then verify with `netlify status` again. **Alternative: API Key authentication** If browser authentication isn't available, users can set: ```bash export NETLIFY_AUTH_TOKEN=your_token_here ``` Tokens can be generated at: https://app.netlify.com/user/applications#personal-access-tokens ### 2. Detect Site Link Status From `netlify status` output, determine: - **Linked**: Site already connected to Netlify (shows site name/URL) - **Not linked**: Need to link or create site ### 3. Link to Existing Site or Create New **If already linked** → Skip to step 4 **If not linked**, attempt to link by Git remote: ```bash # Check if project is Git-based git remote show origin # If Git-based, extract remote URL # Format: https://github.com/username/repo or [email protected]:username/repo.git # Try to link by Git remote npx netlify link --git-remote-url <REMOTE_URL> ``` **If link fails** (site doesn't exist on Netlify): ```bash # Create new site interactively npx netlify init ``` This guides user through: 1. Choosing team/account 2. Setting site name 3. Configuring build settings 4. Creating netlify.toml if needed ### 4. Verify Dependencies Before deploying, ensure project dependencies are installed: ```bash # For npm projects npm install # For other package managers, detect and use appropriate command # yarn install, pnpm install, etc. ``` ### 5. Deploy to Netlify Choose deployment type based on context: **Preview/Draft Deploy** (default for existing sites): ```bash npx netlify deploy ``` This creates a deploy preview with a unique URL for testing. **Production Deploy** (for new sites or explicit production deployments): ```bash npx netlify deploy --prod ``` This deploys to the live production URL. **Deployment process**: 1. CLI detects build settings (from netlify.toml or prompts user) 2. Builds the project locally 3. Uploads built assets to Netlify 4. Returns deployment URL ### 6. Report Results After deployment, report to user: - **Deploy URL**: Unique URL for this deployment - **Site URL**: Production URL (if production deploy) - **Deploy logs**: Link to Netlify dashboard for logs - **Next steps**: Suggest `netlify open` to view site or dashboard ## Handling netlify.toml If a `netlify.toml` file exists, the CLI uses it automatically. If not, the CLI will prompt for: - **Build command**: e.g., `npm run build`, `next build` - **Publish directory**: e.g., `dist`, `build`, `.next` Common framework defaults: - **Next.js**: build command `npm run build`, publish `.next` - **React (Vite)**: build command `npm run build`, publish `dist` - **Static HTML**: no build command, publish current directory The skill should detect framework from `package.json` if possible and suggest appropriate settings. ## Example Full Workflow ```bash # 1. Check authentication npx netlify status # If not authenticated: npx netlify login # 2. Link site (if needed) # Try Git-based linking first git remote show origin npx netlify link --git-remote-url https://github.com/user/repo # If no site exists, create new one: npx netlify init # 3. Install dependencies npm install # 4. Deploy (preview for testing) npx netlify deploy # 5. Deploy to production (when ready) npx netlify deploy --prod ``` ## Error Handling Common issues and solutions: **"Not logged in"** → Run `npx netlify login` **"No site linked"** → Run `npx netlify link` or `npx netlify init` **"Build failed"** → Check build command and publish directory in netlify.toml or CLI prompts → Verify dependencies are installed → Review build logs for specific errors **"Publish directory not found"** → Verify build command ran successfully → Check publish directory path is correct ## Troubleshooting ### Escalated Network Access Example guidance to the user: ``` The deploy needs escalated network access to deploy to Netlify. I can rerun the command with escalated permissions—want me to proceed? ``` ## Environment Variables For secrets and configuration: 1. Never commit secrets to Git 2. Set in Netlify dashboard: Site Settings → Environment Variables 3. Access in builds via `process.env.VARIABLE_NAME` ## Tips - Use `netlify deploy` (no `--prod`) first to test before production - Run `netlify open` to view site in Netlify dashboard - Run `netlify logs` to view function logs (if using Netlify Functions) - Use `netlify dev` for local development with Netlify Functions ## Reference - Netlify CLI Docs: https://docs.netlify.com/cli/get-started/ - netlify.toml Reference: https://docs.netlify.com/configure-builds/file-based-configuration/ ## Bundled References (Load As Needed) - [CLI commands](references/cli-commands.md) - [Deployment patterns](references/deployment-patterns.md) - [netlify.toml guide](references/netlify-toml.md) ## When to Use <!-- TODO: review --> ## When NOT to Use <!-- TODO: review -->
© OpenAI · Apache-2.0 · trailofbits/skills-curated