netlify

What This Skill Does

The netlify skill for OpenClaw provides a powerful interface for automating web deployments via the Netlify CLI. It acts as an orchestrator for managing static sites, configuring continuous integration (CI/CD) pipelines, and handling environment variables. This skill is particularly optimized for complex monorepo structures, where multiple domain-specific sites live within a single repository, by utilizing specific base directories and localized netlify.toml configurations. It handles the full lifecycle of a site, from initial creation and linking to remote GitHub repositories, to production deployment and environmental management.

Installation

To integrate this skill into your OpenClaw agent, run the following command in your terminal: clawhub install openclaw/skills/skills/ajmwagar/netlify

Ensure that you have the Netlify CLI installed globally (npm install -g netlify-cli) and that your environment is authenticated either through an interactive netlify login session or by providing a NETLIFY_AUTH_TOKEN environment variable, which is highly recommended for automated agent workflows.

Use Cases

This skill is ideal for developers managing multiple project sites from one codebase. Common use cases include:

• Automating the creation of new site projects under a specific Netlify team slug.
• Configuring CI/CD pipelines to trigger builds directly from GitHub push events.
• Managing site-specific environment variables for secure API key injection.
• Deploying quick site previews without manual dashboard interaction.
• Standardizing site configurations across multiple subfolders using localized netlify.toml files.

Example Prompts

1. "Avery, please set up the new project at sites/marketing-landing-page. Make sure it's connected to our GitHub repo and configured for auto-deploys."
2. "Update the environment variables for our Seattle site; set CONTACT_EMAIL to [email protected] and trigger a new production build."
3. "List all active Netlify sites and tell me which ones are currently linked to local subfolders in our monorepo."

Tips & Limitations

For monorepos, always ensure you have a netlify.toml file within the site’s specific subfolder to avoid build misconfigurations. If your build uses Hugo, ensure you specify the correct HUGO_VERSION in your configuration to prevent dependency mismatches during CI/CD. Note that some operations may require manual intervention if the GitHub authentication has expired or if the repository permissions are restricted. When running in a non-interactive environment, always use the --auth flag or pre-set the NETLIFY_AUTH_TOKEN to prevent the skill from hanging on login prompts.