Netlify

**Judgement:** This skill is a solid, focused wrapper around the Netlify CLI for setting up and managing Netlify sites, particularly in monorepos and for Hugo-based static sites. It is well-suited when you already use Netlify and want to standardize or automate site provisioning and CI/CD wiring. **Strengths:** - Handles the full “new site” workflow: create Netlify site, link local folder, connect GitHub, configure builds, and manage env vars. - Optimized for monorepos where each site lives in its own subfolder with its own netlify.toml. - Provides concrete patterns and scripts for Hugo deployments. **Key Risks / Limitations:** - Requires a working Netlify CLI environment, valid authentication (`netlify login` or `NETLIFY_AUTH_TOKEN`), and knowledge of the correct team/account slug; misconfiguration here will cause failures. - Operations affect live deployment pipelines: incorrect base directory, wrong netlify.toml, or mistaken `env:set` can break production builds or expose misconfigs. - Interactive flows (`netlify init`) can be brittle in fully automated contexts if prompts change or are not properly bypassed. **Recommended Scenarios:** - You manage multiple static sites in a single repo (e.g., `sites/<domain>`) and want a consistent, repeatable Netlify setup process. - You are adding new domains or Hugo sites regularly and want to avoid one-off manual Netlify configuration via the UI. - You need scripted control over Netlify environment variables and deploy commands as part of a CI/CD or infrastructure-as-code style workflow. Use this skill when the goal is **Netlify-centric deployment automation** for monorepos; avoid it if you are not on Netlify, lack needed credentials, or require very fine-grained, non-CLI-specific infrastructure control beyond Netlify’s scope.