Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Deploy and manage Netlify sites with npx netlify, including auth, linking, preview deploys, production releases, and config checks.
Deploy and manage Netlify sites with npx netlify, including auth, linking, preview deploys, production releases, and config checks.
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.
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. TopicFileSetup and integration flowsetup.mdMemory templatememory-template.mdCLI command mapcli-commands.mdDeployment scenariosdeployment-patterns.mdConfiguration examplesnetlify-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. TrapConsequenceFixRunning deploy before login checkCommand fails with auth errorsAlways run npx netlify status firstRunning --prod by defaultUnreviewed changes go liveStart with preview deploy unless user confirms productionWrong publish directorySite deploys blank or outdated buildRun local build and verify output folderLinking from wrong monorepo folderDeploys wrong appConfirm current path and base directory before link/deployTreating netlify.toml as optional on complex projectsInconsistent builds between environmentsCommit a minimal, explicit netlify.toml
Only Netlify service endpoints and Netlify documentation endpoints are expected in normal usage of this skill. EndpointData SentPurposehttps://api.netlify.comDeploy metadata, site/project identifiers, build outputs via CLIAuthentication, linking, and deploymentshttps://app.netlify.comBrowser session data when login opens OAuth flowInteractive authentication and dashboard accesshttps://docs.netlify.comDocumentation requests onlyReference 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
If useful: clawhub star netlify-deploy Stay updated: clawhub sync
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.