deploy-netlify

Deploy prebuilt sites to Netlify with environment variables and custom domains.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill deploy-netlify-jedmamosto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-netlify
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/deploy-netlify
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill deploy-netlify-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you reliably ship a built funnel or static site to Netlify with the correct environment variables, domain setup, and post-deploy verification.

Core Features & Use Cases

  • Netlify deploy workflow: Handles preview and production deployments, including proper use of the --prod flag.
  • Environment variable setup: Ensures required keys (GHL API token, Stripe keys, GA4 measurement ID, Meta Pixel ID, webhook secrets) are set via Netlify environment contexts without committing secrets.
  • Custom domain and redirects: Guides safe subdomain vs apex decisions, redirect/SPA fallbacks, and SSL verification using dig and curl.

Quick Start

Tell the AI: "Set up my Netlify deployment for this project, apply the required production environment variables, deploy a preview first to verify forms and tracking, then promote to production and add the custom domain as a subdomain."

Frequently Asked Questions about deploy-netlify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a prebuilt static site to Netlify with environment variables?

This Skill automates deploying a prebuilt site to Netlify by handling environment variable configuration for required keys like Stripe and GA4, ensuring secrets are set securely without committing them to your repository.

Can I configure a custom domain and SSL verification when deploying to Netlify?

Yes, you can configure a custom domain and verify SSL when deploying to Netlify. The process guides safe subdomain versus apex domain decisions and uses dig and curl commands to verify SSL and ensure your domain wiring is functional.

What is the difference between a preview and production deployment on Netlify?

A Netlify preview deployment publishes to a temporary URL to test forms and tracking, while a production deployment uses the --prod flag to publish to your live site. Promoting from preview to production ensures a verified release.

How do I set up Netlify Forms and SPA redirects for my deployment?

Setting up Netlify Forms and SPA redirects requires configuring redirect rules and SPA fallbacks during your deployment workflow. This ensures client-side routing functions correctly and forms are properly tracked on your live Netlify site.

Do I need the Netlify CLI initialized to automate my site deployment?

Yes, you need the Netlify CLI correctly initialized and authenticated to automate your site deployment. Proper CLI authentication is a prerequisite for executing explicit preview and production deployments from your environment.

Why does my Netlify deployment require branch deploy workflows?

Your Netlify deployment may require branch deploy workflows if your project relies on Netlify Forms, existing Netlify project integrations, or specific client domain constraints that dictate using Netlify's branch-based publishing infrastructure.