agentleFS
hebertzhuhebertzhu/agent-foundry/skills/netlify-deploy/SKILL.md

netlify-deploy

Skill0 starsChanged 8 months agoMITView on GitHub

Use when the user wants to deploy, publish, preview, or link a web project on Netlify; prefer the Netlify CLI, verify auth and site linkage first, and default to preview deploys unless production is explicitly requested.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use changelog-generator.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArogyaReddySkill

    changelog-generator

    Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use for Netlify site linking, preview deploys, production deploys, and netlify.toml-aware deployment setup.

    line 9
  2. Very specific:

    Check npx netlify status first to confirm CLI access, login state, and whether the current repo is already linked.

    line 12
  3. Very specific:

    If the repo is not linked, inspect the Git remote before choosing between npx netlify link --git-remote-url <remote> and npx netlify init.

    line 13
  4. Very specific:

    Default to npx netlify deploy for a preview URL.

    line 15
  5. Distinctive:

    Keep instructions CLI-first, host-agnostic, and reusable across modern web projects.

    line 20
  6. Distinctive:

    Do not claim the deploy succeeded unless the CLI returns a success result or URL.

    line 23
  7. Distinctive:

    Do not invent build commands, publish directories, or site settings when the project config is ambiguous.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Netlify Deploy

Intent

  • Use for Netlify site linking, preview deploys, production deploys, and netlify.toml-aware deployment setup.

Default operating pattern

  1. Check npx netlify status first to confirm CLI access, login state, and whether the current repo is already linked.
  2. If the repo is not linked, inspect the Git remote before choosing between npx netlify link --git-remote-url <remote> and npx netlify init.
  3. Inspect package.json, netlify.toml, and the detected package manager before installing dependencies or guessing build settings.
  4. Default to npx netlify deploy for a preview URL; only use npx netlify deploy --prod when the user explicitly asks for production.
  5. Return the deploy URL, the site URL if available, and any remaining manual steps such as setting environment variables in the Netlify dashboard.

Pack fit

  • Included in: deploy-ops
  • Keep instructions CLI-first, host-agnostic, and reusable across modern web projects.

Boundary

  • Do not claim the deploy succeeded unless the CLI returns a success result or URL.
  • Do not invent build commands, publish directories, or site settings when the project config is ambiguous.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.