setup-deploy

Detect deployment targets and write a reusable CLAUDE.md deployment configuration.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill setup-deploy-jm199seo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-deploy
Source: https://github.com/jm199seo/lostark-accessory-viewer/tree/main/.claude/skills/gstack/setup-deploy
Command: npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill setup-deploy-jm199seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatic detection of deployment targets across Fly.io, Render, Vercel, Netlify, Heroku, and GitHub Actions, followed by writing a reusable CLAUDE.md deployment configuration to enable future deployments to run without reconfiguration.

Core Features & Use Cases

  • Platform detection from common configuration files (fly.toml, render.yaml, vercel.json, netlify.toml, Procfile, railway.*) and actions workflows.
  • Idempotent CLAUDE.md config generation that captures platform, production URL, deploy status commands, and health checks.
  • Guided platform-specific steps (Fly.io, Render, Vercel, Netlify, GitHub Actions) with optional CLI checks and URL confirmation.
  • Custom/manual deployments support, with an AskUserQuestion flow to gather missing data.

Quick Start

Run /setup-deploy to begin configuring automatic deployment for your project.

Frequently Asked Questions about setup-deploy

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

FAQPage Schema
How do I auto-detect deployment targets across multiple hosting platforms?

Multi-platform deployment configuration captures your production URL, deploy status commands, and health checks in an idempotent CLAUDE.md file. This enables future deployments to run automatically without manual reconfiguration across detected platforms.

How do I set up automatic deployment for Fly.io, Render, or Vercel?

Manual deployments are supported through an AskUserQuestion flow that gathers missing data when standard configuration files are absent. This ensures your custom deployment workflow still generates a valid CLAUDE.md configuration.

Does GitHub Actions deployment workflow detection support writing reusable config?

GitHub Actions deployment workflow detection supports writing reusable config by validating actions workflows alongside standard platform files. It produces an idempotent configuration ready for verification of your deployment status commands and health checks.

Why does my deployment configuration need to be idempotent?

An idempotent deployment configuration needs to be written so repeated setup runs do not duplicate or corrupt existing settings. This ensures your CLAUDE.md config remains stable and ready for verification across multiple deployment cycles.