Netlify Deploy

What This Skill Does

The Netlify Deploy skill enables the OpenClaw AI agent to interface directly with the Netlify CLI, providing a robust, terminal-first environment for managing web deployments. This skill automates the complexity of authentication, site linking, and build configuration. By utilizing local memory stored in ~/netlify-deploy/, the agent retains context about your specific project preferences, such as build directories and preferred deployment modes, ensuring that repeated tasks are executed with consistent safety parameters. It serves as a bridge between your local repository and the Netlify hosting platform, allowing for seamless preview deploys and controlled production releases.

Installation

To integrate this skill into your environment, use the OpenClaw CLI package manager: clawhub install openclaw/skills/skills/ivangdavila/netlify-deploy After installation, initialize your project workspace by consulting the setup.md file within the skill directory. This ensures all environment variables and API integrations are configured correctly for your machine.

Use Cases

This skill is ideal for developers who prefer managing deployment pipelines through CLI commands rather than browser dashboards. It is perfect for automated preview deploys on pull requests, managing multi-site projects from a single monorepo, and validating netlify.toml configurations before triggering a full production push. Whether you are performing a first-time deployment of a static site or managing a complex SPA, this skill handles the heavy lifting of linking your local git repository to Netlify site IDs, confirming build output folders, and managing authentication tokens safely.

Example Prompts

1. "I've finished the new feature on the contact-page branch. Can you deploy a preview link for me to review?"
2. "Please link the current repository to Netlify and perform a production deployment using the settings defined in our memory file."
3. "My build is failing during the deploy process. Can you check my netlify.toml and verify the publish directory settings?"

Tips & Limitations

Always follow the 'Link-First' methodology: confirm your git remote origins are correctly set before initializing a link to ensure the agent maps the right environment to the right project. Remember that by default, the agent will prioritize preview deploys to protect your production site from unintended breaking changes. Use the --prod flag explicitly when you are ready to publish. If you encounter issues with environment variables, check the setup.md file to confirm your Netlify CLI auth token is active.