setup-deploy

Detect deployment platforms and persist configuration to AGENTS.md.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/yckkkk/reo --skill setup-deploy-yckkkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/yckkkk/reo/tree/main/.agents/skills/setup-deploy
Command: npx skills add https://github.com/yckkkk/reo --skill setup-deploy-yckkkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill configures deployment settings for /land-and-deploy by detecting the target platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, or custom) and writing the configuration to AGENTS.md so all future deploys are automatic.

Core Features & Use Cases

  • Platform detection and automatic platform-specific setup for deployment pipelines.
  • Writes production URL, health check endpoints, and deploy status commands into a single AGENTS.md entry for consistent, repeatable deployments.
  • Use Case: A team wants a one-command setup that configures CI/CD across multiple platforms and ensures new deploys follow a standardized workflow.

Quick Start

Run /setup-deploy to detect your deployment platform and persist the configuration to AGENTS.md.

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 across multiple platforms like Vercel and Heroku?

Automate deployment configuration by running a detection script that identifies your target platform and writes platform-specific settings, URLs, and commands to AGENTS.md. This ensures consistent, repeatable CI/CD setups across supported platforms like Vercel, Heroku, or Fly.io.

What is the best way to persist CI/CD settings for repeatable deployments?

Persist CI/CD settings by capturing platform details, health check endpoints, and deploy commands into a single AGENTS.md entry. This centralizes configuration so all future deployments follow a standardized, automatic workflow without manual reconfiguration.

Does automatic platform detection work for GitHub Actions and custom deployment setups?

Yes, automatic platform detection works for GitHub Actions and custom setups. The script reads your project files to identify the deployment platform and persists the detected configuration to AGENTS.md for standardized automated deployments.

How do I configure health check endpoints and production URLs for automatic deployments?

Configure health check endpoints and production URLs by running the setup command, which detects your deployment platform and writes these specific details into AGENTS.md. This ensures your deployment pipeline has the necessary monitoring and routing configurations.

Can I use this deployment setup for any project using land-and-deploy?

Yes, you can use this setup for any project using the land-and-deploy workflow. It requires script-driven platform detection and a stable AGENTS.md writer to automatically capture and persist your deployment configuration across various supported platforms.

Why does my deployment configuration need to be written to AGENTS.md?

Deployment configuration is written to AGENTS.md to create a persistent, standardized entry for your platform, URLs, and deploy commands. This ensures all future automated deployments are repeatable and consistent across your team's workflow.