name: Netlify Deploy slug: netlify-deploy version: 1.0.0 homepage: https://clawic.com/skills/netlify-deploy description: Deploy and manage Netlify sites with npx netlify, including auth, linking, preview deploys, production releases, and config checks. changelog: Initial release with authentication checks, link-or-create flow, and safer preview-to-production deployment guidance. metadata: {"clawdbot":{"emoji":"NET","requires":{"bins":["npx","git"],"config":["~/netlify-deploy/"]},"os":["linux","darwin","win32"]}}
On first use, read setup.md for integration and environment checks.
User needs to deploy, host, publish, or relink a web project on Netlify from the terminal. Use this skill for first deploys, preview deploys, production pushes, monorepo paths, and netlify.toml fixes.
Memory lives in ~/netlify-deploy/.
Use this local memory only for operational defaults so future deploy requests can start with the right safety assumptions.
~/netlify-deploy/
`- memory.md # Preferred deploy mode, default project path, and common build settings
See memory-template.md for setup.
Load only the file needed for the current task to keep command decisions fast and avoid irrelevant context.
| Topic | File |
|---|---|
| Setup and integration flow | setup.md |
| Memory template | memory-template.md |
| CLI command map | cli-commands.md |
| Deployment scenarios | deployment-patterns.md |
| Configuration examples | netlify-toml.md |
npx netlify status
If not authenticated, run npx netlify login and re-check status. If authenticated but not linked, resolve linking before deploy.
git remote get-url origin
npx netlify link --git-remote-url <remote-url>
If the repository is not linked or no matching site exists, fall back to npx netlify init.
npx netlify deploy
Use npx netlify deploy --prod only when the user explicitly requests production or confirms readiness.
Never force production deploys as a shortcut when validation is still pending.
npm run build
npx netlify deploy --dir=dist
Use framework defaults only as a starting point. Validate the actual output folder in the current project.
For monorepos, deploy from the correct subdirectory or set build.base in netlify.toml before linking/deploying.
After each deploy, return deploy URL, environment (preview or production), and one concrete next step.
These traps are prioritized by how often they cause failed or risky deploys in terminal-first workflows.
7w4.net收录了海量优质技能插件。
| Trap | Consequence | Fix |
|---|---|---|
| Running deploy before login check | Command fails with auth errors | Always run npx netlify status first |
Running --prod by default |
Unreviewed changes go live | Start with preview deploy unless user confirms production |
| Wrong publish directory | Site deploys blank or outdated build | Run local build and verify output folder |
| Linking from wrong monorepo folder | Deploys wrong app | Confirm current path and base directory before link/deploy |
Treating netlify.toml as optional on complex projects |
Inconsistent builds between environments | Commit a minimal, explicit netlify.toml |
Only Netlify service endpoints and Netlify documentation endpoints are expected in normal usage of this skill.
| Endpoint | Data Sent | Purpose |
|---|---|---|
| https://api.netlify.com | Deploy metadata, site/project identifiers, build outputs via CLI | Authentication, linking, and deployments |
| https://app.netlify.com | Browser session data when login opens OAuth flow | Interactive authentication and dashboard access |
| https://docs.netlify.com | Documentation requests only | Reference for command and config behavior |
No other data is sent externally.
Data that leaves your machine:
- Project deploy artifacts and metadata are sent to Netlify when running deploy commands.
- Auth/session data is exchanged with Netlify during npx netlify login.
Data that stays local:
- Local source files and build scripts remain in your project unless you deploy.
- Skill preferences stay in ~/netlify-deploy/memory.md.
This skill does NOT: - Store secrets inside skill files. - Run undeclared external services beyond Netlify endpoints. - Modify unrelated repositories or directories.
By using this skill, deployment data is sent to Netlify services. Only install if you trust Netlify with your project artifacts and deployment metadata.
Install with clawhub install <slug> if user confirms:
- ci-cd - delivery pipeline design and release automation practices
- git - branch hygiene and release-safe commit workflow
- deploy - generic deployment planning across environments
- devops - infrastructure and operational guardrails
clawhub star netlify-deployclawhub sync这个 Skill 质量较好,文档清晰易读,能有效指导 Netlify 部署操作。它的安全设计做得很到位——强调先检查登录状态、先用预览版确认没问题再上生产,避免了很多新手容易犯的错误。陷阱总结也很实用。不足是高级功能覆盖不全,有些复杂场景可能找不到答案。适合需要常规部署的用户使用。