Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use the Netlify CLI (netlify) to create/link Netlify sites and set up CI/CD (continuous deployment) from GitHub, especially for monorepos (multiple sites in one repo like Hugo sites under sites/<domain>). Use when Avery asks to deploy a new site, connect a repo to Netlify, configure build/publish settings, set environment variables, enable deploy previews, or automate Netlify site creation.
Use the Netlify CLI (netlify) to create/link Netlify sites and set up CI/CD (continuous deployment) from GitHub, especially for monorepos (multiple sites in one repo like Hugo sites under sites/<domain>). Use when Avery asks to deploy a new site, connect a repo to Netlify, configure build/publish settings, set environment variables, enable deploy previews, or automate Netlify site creation.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use the netlify CLI to create projects (βsitesβ), link local folders, and configure CI/CD from GitHub.
netlify --version Logged in (netlify login) or provide --auth $NETLIFY_AUTH_TOKEN. Know the Netlify team/account slug you want to create sites under (optional but recommended). Helpful checks: netlify status netlify sites:list
For one repo with multiple sites (e.g. sites/seattlecustomboatparts.com, sites/floridacustomerboatparts.com): Create one Netlify site per domain. Set the siteβs Base directory to that subfolder. Put a netlify.toml inside that subfolder. This keeps each domainβs build config self-contained.
Create sites/<domain>/netlify.toml: [build] command = "hugo --minify" publish = "public" [build.environment] HUGO_VERSION = "0.155.1" (Adjust HUGO_VERSION as needed.)
Run inside the site folder you want to deploy (base dir): cd sites/<domain> netlify sites:create --name <netlify-site-name> --account-slug <team> --with-ci Notes: --with-ci starts CI hooks setup. If you need manual control, add --manual.
If not linked already: netlify link
netlify init This is usually interactive (select Git remote/repo + build settings). For automation we can pre-create netlify.toml and then accept defaults.
Set per-site vars: netlify env:set VAR_NAME value netlify env:list Useful for monorepos: CONTACT_EMAIL (or other shared config)
Manual deploys (handy for quick preview): netlify deploy # draft deploy netlify deploy --prod # production deploy
scripts/hugo_netlify_toml.sh: create a netlify.toml in a Hugo subfolder scripts/netlify_monorepo_site.sh: helper to create/link/init a site for a subfolder When using scripts, prefer passing NETLIFY_AUTH_TOKEN via env for non-interactive runs.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.