Skills netlify
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.
git clone https://github.com/openclaw/skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/ajmwagar/netlify" ~/.claude/skills/openclaw-skills-netlify && rm -rf "$T"
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/ajmwagar/netlify" ~/.openclaw/skills/openclaw-skills-netlify && rm -rf "$T"
skills/ajmwagar/netlify/SKILL.mdnetlify
Use the
netlify CLI to create projects (“sites”), link local folders, and configure CI/CD from GitHub.
Pre-reqs
netlify --version- Logged in (
) or providenetlify login
.--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
Monorepo pattern (recommended)
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
inside that subfolder.netlify.toml
This keeps each domain’s build config self-contained.
Hugo subfolder netlify.toml
netlify.tomlCreate
sites/<domain>/netlify.toml:
[build] command = "hugo --minify" publish = "public" [build.environment] HUGO_VERSION = "0.155.1"
(Adjust HUGO_VERSION as needed.)
Fast workflow: create + link + init CI/CD
1) Create a Netlify site (project)
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:
starts CI hooks setup.--with-ci- If you need manual control, add
.--manual
2) Link local folder to the created site
If not linked already:
netlify link
3) Connect to GitHub for continuous deployment
netlify init
This is usually interactive (select Git remote/repo + build settings). For automation we can pre-create
netlify.toml and then accept defaults.
Environment variables
Set per-site vars:
netlify env:set VAR_NAME value netlify env:list
Useful for monorepos:
(or other shared config)CONTACT_EMAIL
Deploy
Manual deploys (handy for quick preview):
netlify deploy # draft deploy netlify deploy --prod # production deploy
Included scripts
: create ascripts/hugo_netlify_toml.sh
in a Hugo subfoldernetlify.toml
: helper to create/link/init a site for a subfolderscripts/netlify_monorepo_site.sh
When using scripts, prefer passing
NETLIFY_AUTH_TOKEN via env for non-interactive runs.