netlify-ops

Create Netlify sites, deploy builds, and manage domains via CLI and REST API.

1|1|Updated May 24, 2026
One-click install
npx skills add https://github.com/bm629/agent-skills --skill netlify-ops-bm629
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: netlify-ops
Source: https://github.com/bm629/agent-skills/tree/main/skills/netlify-ops
Command: npx skills add https://github.com/bm629/agent-skills --skill netlify-ops-bm629

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Driving Netlify hosting operations from an agent requires juggling the CLI, a 174-operation REST API, async deploy lifecycles, and strict token-handling rules — this Skill packages that entire workflow with validated scripts and a bundled OpenAPI spec so operations run headlessly without interactive logins. ## Core Features & Use Cases - CLI-first site and deploy management: Create sites, run draft or production deploys, and poll deploy status through the netlify CLI using four validated shell scripts. - Full REST long tail: Resolve any of the ~174 Netlify API operations from a bundled Swagger 2.0 spec via an endpoint index and a $ref-resolving Python helper, covering custom domains, DNS zones, and fine-grained reads. - Strict credential contract: Consumes a caller-injected token by variable name through NETLIFY_AUTH_TOKEN, never printing the value and never running netlify login. - Use Case: Ask the agent to deploy a ./dist build to production on a specific site; it creates or targets the site, runs the deploy, polls until state: ready, and returns the live URL. ## Quick Start Use netlify-ops to deploy the ./dist directory to my Netlify site in production and report the live URL once the deploy is ready.

Frequently Asked Questions about netlify-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a site to Netlify from the command line?

Run `netlify deploy --dir <dir> --site <site_id> --json` with NETLIFY_AUTH_TOKEN set; add `--prod` to publish to production. The skill's deploy.sh script wraps this, always passing `--site` explicitly since fresh checkouts have no link state.

How do I set a custom domain on a Netlify site via the API?

Send a PATCH request to `/api/v1/sites/<site_id>` with a JSON body of `{"custom_domain": "example.com"}` and a Bearer token. Setting the domain does not make it resolve — follow up with DNS configuration via configureDNSForSite or dns_zones records.

Can the Netlify CLI run without interactive login?

Yes. The CLI reads the NETLIFY_AUTH_TOKEN environment variable (or an `--auth` flag) and runs fully headlessly with `--json` and `--force`. This skill forbids `netlify login` entirely and treats a missing token as a caller error.

Why is my Netlify deploy stuck and never reaching ready state?

A hand-rolled REST createSiteDeploy returns a `required` array of SHA1 file digests that must each be uploaded before the deploy reaches `ready`. Using the CLI's `netlify deploy --dir` avoids this because it performs the digest diff and upload automatically.

What are the Netlify API rate limits for deploys?

Netlify allows 500 requests per minute generally, but deploys are limited to 3 per minute and 100 per day. Honor the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers and back off when remaining hits zero.

When should I not use Netlify for hosting?

Netlify here covers static/JAMstack sites plus serverless functions only. For full-stack container or app hosting, use platforms like Render, Fly.io, or Railway instead, as this skill does not target container-based deployments.