npx skills add ...
npx skills add firecrawl/openai-skills --skill netlify-deploy
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.
npx skills add firecrawl/openai-skills --skill netlify-deploy
Deploy web projects to Netlify using the Netlify CLI with intelligent detection of project configuration and deployment context.
This skill automates Netlify deployments by:
sandbox_permissions=require_escalated.The skill uses the pre-authenticated Netlify CLI approach:
npx netlify statusnpx netlify loginAuthentication uses either:
netlify login opens browser for authenticationNETLIFY_AUTH_TOKEN environment variableCheck if the user is logged into Netlify:
Expected output patterns:
If not authenticated, guide the user:
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:
Tokens can be generated at: https://app.netlify.com/user/applications#personal-access-tokens
From netlify status output, determine:
If already linked → Skip to step 4
If not linked, attempt to link by Git remote:
If link fails (site doesn't exist on Netlify):
This guides user through:
Before deploying, ensure project dependencies are installed:
Choose deployment type based on context:
Preview/Draft Deploy (default for existing sites):
This creates a deploy preview with a unique URL for testing.
Production Deploy (for new sites or explicit production deployments):
This deploys to the live production URL.
Deployment process:
After deployment, report to user:
netlify open to view site or dashboardIf a netlify.toml file exists, the CLI uses it automatically. If not, the CLI will prompt for:
npm run build, next builddist, build, .nextCommon framework defaults:
npm run build, publish .nextnpm run build, publish distThe skill should detect framework from package.json if possible and suggest appropriate settings.
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
If deployment fails due to network issues (timeouts, DNS errors, connection resets), rerun the deploy with escalated permissions (use sandbox_permissions=require_escalated). The deploy requires escalated network access when sandbox networking blocks outbound requests.
Example guidance to the user:
For secrets and configuration:
process.env.VARIABLE_NAMEnetlify deploy (no --prod) first to test before productionnetlify open to view site in Netlify dashboardnetlify logs to view function logs (if using Netlify Functions)netlify dev for local development with Netlify Functions