Netlify — 技能 — openclaw中文资讯站

技能详情（站内镜像，无评论）

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, con…

开发与 DevOps

许可证：MIT-0

MIT-0 ·免费使用、修改和重新分发。无需归因。

版本：v1.0.0

统计：⭐ 2 · 2.3k · 6 current installs · 6 all-time installs

⭐ 2

安装量（当前） 6

🛡 VirusTotal ：良性 · OpenClaw ：可疑

Package：ajmwagar/netlify

安全扫描（ClawHub）

VirusTotal ：良性
OpenClaw ：可疑

OpenClaw 评估

The skill mostly does what it says (wraps the Netlify CLI for monorepos) but the metadata omits required runtime dependencies and credential interactions (Netlify CLI, NETLIFY_AUTH_TOKEN, and GitHub linking), so the package is internally inconsistent and requires caution before use.

目的

The skill's name/description match the included scripts and SKILL.md: it automates creating/linking Netlify sites and adding netlify.toml for Hugo subfolders. However, the metadata declares no required binaries or credentials even though the instructions and scripts clearly rely on the Netlify CLI and suggest using NETLIFY_AUTH_TOKEN for non-interactive runs. This omission is an inconsistency (not necessarily malicious) that reduces transparency.

说明范围

The SKILL.md and scripts limit actions to creating a netlify.toml in the target folder, running netlify sites:create, netlify link, and netlify init (interactive GitHub connection). There are no instructions to read unrelated system files or exfiltrate data. Note: netlify init will connect to GitHub and may initiate OAuth/permissions on your repositories, which is in-scope for deploying to Netlify but worth user awareness.

安装机制

There is no install spec (instruction-only plus two small helper scripts). No remote downloads or package installs are invoked by the skill itself, so there is low installation risk. The included scripts are small, readable bash scripts that create a netlify.toml and shell out to the netlify CLI.

证书

The skill metadata lists no required environment variables or primary credential, but the SKILL.md and scripts recommend or expect NETLIFY_AUTH_TOKEN (and implicitly will trigger a GitHub OAuth/connection via netlify init). The skill therefore asks for or uses credentials (Netlify token and GitHub account access) without declaring them, which is a transparency and proportionality concern.

持久

The skill does not request always:true and does not modify other skills or system-wide settings. Its actions are limited to the repo/site directory (writing netlify.toml) and invoking the Netlify CLI—normal for deployment tooling.

安装（复制给龙虾 AI）

将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Netlify」。简介：Use the Netlify CLI (netlify) to create/link Netlify sites and set up CI/CD (co…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/ajmwagar/netlify/SKILL.md
（来源：yingzhi8.cn 技能库）

SKILL.md

打开原始 SKILL.md（GitHub raw）

---
name: netlify
description: 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.
---

# netlify

Use the `netlify` CLI to create projects (“sites”), link local folders, and configure CI/CD from GitHub.

## Pre-reqs

- `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:

```bash
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 `netlify.toml` *inside that subfolder*.

This keeps each domain’s build config self-contained.

### Hugo subfolder `netlify.toml`

Create `sites/<domain>/netlify.toml`:

```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):

```bash
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`.

### 2) Link local folder to the created site
If not linked already:

```bash
netlify link
```

### 3) Connect to GitHub for continuous deployment

```bash
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:

```bash
netlify env:set VAR_NAME value
netlify env:list
```

Useful for monorepos:
- `CONTACT_EMAIL` (or other shared config)

## Deploy

Manual deploys (handy for quick preview):

```bash
netlify deploy            # draft deploy
netlify deploy --prod     # production deploy
```

## Included scripts

- `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.