netlify-deploy

Deploy static HTML directories to Netlify via CLI and verify with Playwright screenshots.

6|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/thensls/nsls-builder-toolkit --skill netlify-deploy-thensls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: netlify-deploy
Source: https://github.com/thensls/nsls-builder-toolkit/tree/main/skills/netlify-deploy
Command: npx skills add https://github.com/thensls/nsls-builder-toolkit --skill netlify-deploy-thensls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying single-file presentations or small static sites to Netlify can silently serve HTML as plain text, mis-handle MIME types, and produce visual regressions that are hard to catch without repeatable checks. This Skill consolidates the CLI-based deploy process, authentication retrieval, content-type safeguards, and an automated Playwright visual review so you can publish reliably and catch rendering issues quickly.

Core Features & Use Cases

  • CLI-safe deploys: Use netlify-cli to deploy directories (not zip API) and avoid content-type pitfalls.
  • Auth and site guidance: Locate and export NETLIFY_AUTH_TOKEN and NETLIFY_SITE_ID to enable non-interactive deploys.
  • Automated visual QA: Run Playwright screenshots at a 1440×900 viewport with deliberate waits for scroll-snap animations to validate slide decks and static pages before and after fixes.
  • Use Case: Publish an HTML slide deck, verify each slide for wrapping, overflow, and styling inconsistencies, fix the source, and re-deploy until visuals are correct.

Quick Start

Deploy your presentation to Netlify production with NETLIFY_AUTH_TOKEN and NETLIFY_SITE_ID set, then run the Playwright review loop to capture and inspect screenshots.

Frequently Asked Questions about netlify-deploy

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

FAQPage Schema
How do I deploy a static site to Netlify and verify it renders correctly?

Use netlify-cli to deploy static HTML directories to Netlify, then verify rendered output with Playwright screenshots at a 1440×900 viewport to catch visual regressions and content-type issues before publishing.

Why does Netlify serve my HTML presentation as plain text after deploying?

Static HTML presentations may serve as plain text due to zip-based API deploys mishandling MIME types. Using netlify-cli for directory-based deploys enforces correct content-type headers and prevents this issue.

What credentials do I need to automate Netlify deployments non-interactively?

Non-interactive Netlify deployments require setting the NETLIFY_AUTH_TOKEN and NETLIFY_SITE_ID environment variables. These credentials enable netlify-cli to authenticate and publish static site directories without interactive login prompts.

Can I use Playwright to visually test scroll-snap slide decks before deploying?

Yes, Playwright captures screenshots at a 1440×900 viewport with deliberate wait timing for scroll-snap animations, validating slide decks for wrapping, overflow, and styling inconsistencies before deploying to Netlify.

Does this deployment approach work for single-file HTML presentations?

Yes, this approach works for single-file HTML presentations and small static sites requiring an index.html entrypoint. It uses netlify-cli directory deploys alongside Playwright visual QA to ensure scroll-snap slides render correctly.

What are the limitations of using netlify-cli for static site deploys?

Netlify-cli directory deploys are limited to static HTML directories with an index.html entrypoint and require NETLIFY_AUTH_TOKEN and NETLIFY_SITE_ID. This approach targets single-file presentations and small static sites rather than complex applications.