setup-deploy

Detect hosting platforms and save deploy configuration to AGENTS.md.

Updated Jul 21, 2025
One-click install
npx skills add https://github.com/robertzengcn/aiFetchly --skill setup-deploy-robertzengcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/robertzengcn/aiFetchly/tree/main/.agents/skills/gstack/setup-deploy
Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill setup-deploy-robertzengcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually configuring deployment settings for different hosting platforms is time-consuming and error-prone, especially when switching between services like Fly.io, Render, or Vercel. This Skill eliminates that repetitive work by automatically detecting your deploy platform and capturing all required configuration in one persistent location.

Core Features & Use Cases

  • Multi-Platform Detection: Automatically identifies your deployment target from Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, or custom platforms.
  • Persistent Config Storage: Saves production URLs, health check endpoints, and deploy status commands directly to your project's AGENTS.md file for reuse across all future deploys.
  • Use Case: If you just set up a new app on Render, run this Skill once to pull your Render production URL and health check path, and never re-enter that information for subsequent deployments.

Quick Start

Use the setup-deploy skill to automatically detect your deployment platform and save all required deploy configuration to your project's AGENTS.md file.

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 configuration for multiple hosting platforms like Vercel and Render?

Automate deployment configuration by using a skill that detects your target platform—such as Vercel, Render, or Fly.io—and automatically captures production URLs and health check endpoints into a persistent file for reuse.

Where should I store persistent deploy settings to enable repeatable app launches?

Store persistent deploy settings in your project's AGENTS.md file. This ensures production URLs, health check endpoints, and deploy status commands are saved for fully automated future deployments.

Does automated platform detection work with GitHub Actions and Heroku?

Automated platform detection works with GitHub Actions, Heroku, Fly.io, Render, Vercel, Netlify, and custom targets, identifying your deployment platform and extracting required configuration automatically.

What's the best way to configure health check endpoints for land-and-deploy workflows?

Configure health check endpoints by running an automated setup skill that detects your hosting platform and saves the health check paths alongside production URLs directly into your project configuration.

Can I use this deployment setup for custom hosting targets outside of standard PaaS providers?

Yes, the deployment setup supports custom targets alongside standard platforms like Netlify and Fly.io, automatically capturing deploy status commands and configuration for any specified custom deployment environment.

Why does my deployment configuration keep breaking when switching between different hosting platforms?

Deployment configuration breaks due to manual errors when switching platforms. Automating the detection of platform-specific settings and storing them persistently eliminates repetitive manual configuration across services.