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. Do NOT use for deploying to Vercel, Cloudflare, or Render (use their respective skills).
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add tech-leads-club/agent-skills --skill netlify-deployCompatible with
Supported agents
| name | 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. Do NOT use for deploying to Vercel, Cloudflare, or Render (use their respective skills). |
| metadata | author: github.com/openai/skills version: '1.0.0' |
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:
npx netlify status
Expected output patterns:
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
From netlify status output, determine:
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 git@github.com: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:
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.
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:
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.
# 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
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:
The deploy needs escalated network access to deploy to Netlify. I can rerun the command with escalated permissions—want me to proceed?
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 FunctionsAI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnetlify-deployExecute the skills CLI command in your project's root directory to begin installation:
epx add tech-leads-club/agent-skills --skill netlify-deployFetches netlify-deploy from tech-leads-club/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/netlify-deploy
Restart Cursor to activate netlify-deploy. Access via /netlify-deployin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
cloudflare-deploy
tech-leads-club/agent-skills · cloud · same repo
create-rfc
tech-leads-club/agent-skills · creation · same repo
ai-pricing
tech-leads-club/agent-skills · gtm · same repo
partner-affiliate
tech-leads-club/agent-skills · gtm · same repo
accessibility
tech-leads-club/agent-skills · quality · same repo
tactical-ddd
tech-leads-club/agent-skills · architecture · same repo
netlify-deploy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
netlify-deploy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
netlify-deploy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
netlify-deploy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: netlify-deploy is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: netlify-deploy is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend netlify-deploy for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in netlify-deploy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend netlify-deploy for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in netlify-deploy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 26