netlify-deploy

Overview of netlify-deploy skill

netlify-deploy is a deployment-focused skill for publishing web projects to Netlify with the Netlify CLI. It is best for users who need a repeatable path from a local repo to a preview or production deploy, especially when the project may need to be linked, initialized, or authenticated first.

The netlify-deploy skill is most useful when the job is not just “run deploy,” but “figure out the right Netlify flow for this repo.” That includes detecting whether the site is already linked, deciding between preview and production, and handling netlify.toml-driven build settings.

What this skill is for

Use the netlify-deploy skill when you want to:

• deploy a local web app, static site, or framework app to Netlify
• create a first deploy for a new project
• link an existing Git repo or local folder to an existing Netlify site
• produce a preview deploy before shipping to production

What makes it different

The main value of netlify-deploy is workflow guidance, not just a command list. It centers the Netlify CLI, checks authentication first, and accounts for common blockers like an unlinked site, missing publish directory, or incomplete build config.

When it fits best

This skill fits users who already have a real project directory and want a deployment path they can trust. It is less useful for abstract “how do I use Netlify?” questions unless the user is ready to act on a specific repo.

How to Use netlify-deploy skill

Install and read the skill first

For netlify-deploy install, start from the skill entry itself and then read the supporting references that drive command choice:

• SKILL.md
• references/cli-commands.md
• references/deployment-patterns.md
• references/netlify-toml.md

There is no script layer here, so the important decision support lives in the references. Read deployment-patterns.md first if you need help choosing between login, link, init, preview deploy, and production deploy.

Turn a vague goal into a usable prompt

The skill works best when the user states the repo state and deployment target clearly. A strong netlify-deploy usage prompt includes:

• framework or build tool, if known
• whether the site already exists on Netlify
• whether the goal is preview or production
• the expected build output folder, if known
• whether netlify.toml already exists

Example:
“Deploy this Vite app to Netlify. It is not linked yet, I want a production deploy, and the build output is dist.”

Weak input:
“Deploy my site.”

Suggested workflow

A practical netlify-deploy guide flow is:

1. Check auth with npx netlify status.
2. If needed, authenticate with npx netlify login.
3. Decide whether to link an existing site or create one with npx netlify link or npx netlify init.
4. Confirm the build output and config in netlify.toml.
5. Run npx netlify deploy for preview, or npx netlify deploy --prod for production.

Use the config files to reduce guesswork

Before deploying, inspect netlify.toml if it exists. The most important fields are build.command, build.publish, and any context-specific environment settings. If the publish path does not match the actual build output, deployment may succeed but serve the wrong directory or fail validation.

netlify-deploy skill FAQ

Is netlify-deploy only for Netlify CLI users?

Yes. The skill is built around npx netlify and the CLI workflow. If you prefer dashboard-only deployment, this is probably not the right fit.

Do I need the project already linked to use it?

No. The netlify-deploy skill covers both first-time setup and existing sites. If the repo is unlinked, the workflow should shift to link or init before deployment.

Is this better than a generic deploy prompt?

Usually yes, because netlify-deploy bakes in the real Netlify sequence: authenticate, link or init, confirm config, then deploy. That reduces the chance of skipping a prerequisite that blocks the deploy.

When should I not use it?

Do not use netlify-deploy if the project is not a web app, if you cannot run CLI commands, or if you need a broader hosting comparison rather than a Netlify-specific workflow.

How to Improve netlify-deploy skill

Give the skill the repo facts that change the deploy path

The biggest quality gains come from stating what the skill cannot safely infer:

• framework: Next.js, Astro, Vite, SvelteKit, etc.
• build command: npm run build, pnpm build, or custom
• publish directory: dist, build, .next, or other
• site state: new, linked, or already deployed
• target: preview or production

These details help the netlify-deploy skill choose the right CLI path without trial and error.

Surface config mismatches early

A common failure mode is assuming Netlify will detect everything correctly. If your app uses a nonstandard output directory, monorepo layout, or custom base path, say so upfront and point the skill at netlify.toml. That is especially important for netlify-deploy for Deployment in monorepos or framework-specific builds.

Ask for the first deploy shape, not just the command

Better results come from asking for an output that includes the sequence, not a single line. For example:
“Show me the exact steps to authenticate, link this repo, verify netlify.toml, and deploy to production.”

That prompts the skill to explain the decision points that matter before the deploy command is run.

Iterate based on the first deploy result

If the first deploy fails, feed back the exact failure and the current file layout instead of re-asking from scratch. The most useful follow-up inputs are:

• the error message from npx netlify
• the contents of netlify.toml
• the build output folder actually produced by your framework
• whether the site was linked before the failure

That makes the next netlify-deploy usage step more precise and avoids repeating authentication or linking steps that already worked.