$ ~/registry/skill/openai-curated-netlify-deploy

SKILL

netlify-deploy

Name: netlify-deploy
Author: OpenAI

Deploy, publish, and link web projects to Netlify using the CLI.

Stars

★ 23,132

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 22.0k

Summary

This appears to be an open-source, widely trusted prompt-only deployment skill with overall low risk. The main considerations are its intended workflow of running local Netlify/NPM/Git commands and sending site content to Netlify, which are normal behaviors for a deployment-oriented skill.

CredentialsCaution

Although the metadata says no keys/env vars are required, the README explicitly requires an existing Netlify login session and optionally supports NETLIFY_AUTH_TOKEN. There is no indication that the skill itself collects, hardcodes, or exfiltrates credentials; the main credential exposure is the normal use of local CLI/OAuth or environment-variable-based authentication.

Network egressCaution

The skill is explicitly for deploying to Netlify; the README describes netlify status/login/link/init/deploy workflows, so site metadata and deployment artifacts are expected to be sent to Netlify. No unknown third-party endpoints or unrelated exfiltration are described, but outbound transfer of website content is inherent to its deployment function.

Code executionCaution

The README instructs use of local commands such as npx netlify, git, and npm install for detection, dependency installation, and deployment, which is normal local process execution for developer tooling. There is no sign of unrelated privileged system access, but if executed, standard command-execution and dependency-installation risks still apply.

Data accessCaution

The material indicates it inspects the current project directory, reads Git remotes, checks dependencies, and deploys site files, which is broadly consistent with the stated function of deploying the current web project. There is no indication of reading unrelated directories, system-sensitive files, or obviously excessive access.

Supply chainLow risk

The source is the GitHub repository openai/skills, with system flags for open-source and strong community trust (22k+), providing good auditability and reputation signals. Although the license is unspecified, maintenance status is unknown, and runtime use of npx introduces ordinary dependency risk, the available source evidence does not support a high-risk rating.

Recommendations

Use it only in trusted project directories and verify that deployment files do not contain secrets, test data, or other sensitive content.
Prefer browser-based OAuth or least-privilege short-lived Netlify credentials instead of exposing a long-lived NETLIFY_AUTH_TOKEN.
Before running npm install / npx, lock dependency sources and review package.json, lockfiles, and install scripts.
Confirm the target Netlify site/team before deployment to avoid linking or publishing to the wrong environment.

Audited by: gpt-5.4 · 2026-06-16

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "netlify-deploy" skill from askskill:
1. Download https://raw.githubusercontent.com/openai/skills/main/skills/.curated/netlify-deploy/SKILL.md
2. Save it as ~/.claude/skills/netlify-deploy/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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
When sandboxing blocks the deployment network calls, rerun with sandbox_permissions=require_escalated.
The deployment might take a few minutes. Use appropriate timeout values.

Authentication Pattern

The skill uses the pre-authenticated Netlify CLI approach:

Check authentication status with npx netlify status
If not authenticated, guide user through npx netlify login
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:

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:

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:

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:

# 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):

# Create new site interactively
npx netlify init

This guides user through:

Choosing team/account
Setting site name
Configuring build settings
Creating netlify.toml if needed

4. Verify Dependencies

Before deploying, ensure project dependencies are installed:

# 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):

npx netlify deploy

This creates a deploy preview with a unique URL for testing.

Production Deploy (for new sites or explicit production deployments):

npx netlify deploy --prod

This deploys to the live production URL.

Deployment process:

CLI detects build settings (from netlify.toml or prompts user)
Builds the project locally
Uploads built assets to Netlify
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

…

View full docs ↗

Build and deploy an existing Power Pages code site to a target environment.

microsoftGet→

MCP

AppDeploy

Turn app ideas from chat into live full-stack web applications instantly.

—Get→

SKILL

★440

deploy

Build and deploy a Power Apps code app to Power Platform.

microsoftGet→

MCP

Cloudflare Deployer

Deploy full-stack apps to Cloudflare with databases, auth, and storage using natural language.

—Get→

$ loading_