setup-deploy

Detects hosting platform and writes deployment config to CLAUDE.md.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/FxHollow/100000mrr-landing --skill setup-deploy-fxhollow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/FxHollow/100000mrr-landing/tree/main/.agents/skills/gstack/setup-deploy
Command: npx skills add https://github.com/FxHollow/100000mrr-landing --skill setup-deploy-fxhollow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure deployment settings for /land-and-deploy. Detects platforms (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic.

Core Features & Use Cases

  • Platform detection and automatic generation of deploy configuration.
  • Supports multiple hosting platforms and CI workflows to streamline deployment.
  • Use case: Set up a new project with a single command and have CLAUDE.md drive future deploys automatically.

Quick Start

Run the /setup-deploy command to generate CLAUDE.md deployment config.

Frequently Asked Questions about setup-deploy

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

FAQPage Schema
How do I automate deployment pipeline configuration for multiple hosting platforms?

Automate deployment pipeline configuration by detecting your hosting platform, production URL, and health check endpoints, then writing the results to CLAUDE.md to drive future deploys automatically.

Does deployment configuration support Fly.io, Render, Vercel, and Heroku?

Yes, deployment configuration supports Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, and custom deployments, automatically detecting the platform and generating the appropriate deploy configuration.

How do I set up health check endpoints for automated deploys?

Set up health check endpoints by running the configuration command, which detects your health check URLs and deploy status commands, then writes them to CLAUDE.md for future automated deployments.

Can I re-run deployment setup safely without overwriting existing configuration?

Yes, the deployment setup is idempotent, meaning you can re-run it safely without risking your existing configuration or causing conflicts in your CLAUDE.md file.

Why do I need to write deploy configuration to CLAUDE.md?

Writing deploy configuration to CLAUDE.md ensures all future deploys are automatic, storing platform detection, production URLs, and health checks in a single file that drives the deployment workflow.