pop-deploy-init

Detect deployment targets and generate a standardized deploy.json configuration.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jrc1883/popkit-ai --skill pop-deploy-init
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pop-deploy-init
Source: https://github.com/jrc1883/popkit-ai/tree/main/packages/popkit-ops/skills/pop-deploy-init
Command: npx skills add https://github.com/jrc1883/popkit-ai --skill pop-deploy-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Detect deployment targets in a project and generate a standardized deployment configuration file without performing the deployment.

Core Features & Use Cases

  • Detects deployment targets such as Docker, npm, PyPI, Vercel, Netlify, and GitHub Releases from common project files (Dockerfile, package.json, pyproject.toml, etc.) and proposes them for configuration.
  • Generates a deploy.json at .claude/popkit with target configurations and an associated CI/CD setup, while preserving existing configurations and providing backups.
  • Provides a guided, interactive workflow to select targets, designate a primary target, choose CI/CD triggers, and optionally run a setup to scaffold deployment files.

Quick Start

Run the skill to detect deployment targets and create the deploy.json configuration for your project.

Frequently Asked Questions about pop-deploy-init

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

FAQPage Schema
How do I auto-detect deployment targets and generate a deploy.json config file?▼

To auto-detect deployment targets and generate a deploy.json, the skill scans project files like Dockerfile and package.json to identify Docker, npm, PyPI, Vercel, Netlify, or GitHub Releases targets, then writes the configuration without deploying.

Does generating a deployment config overwrite my existing deploy.json file?▼

Generating a deployment config does not overwrite existing files blindly. If a deploy.json already exists, the skill preserves it by creating a backup before writing the new target configurations and CI/CD setup details.

How do I configure CI/CD triggers for multiple deployment targets like Docker and npm?▼

To configure CI/CD triggers for multiple targets like Docker and npm, the skill provides an interactive workflow that guides target selection, designates a primary target, and prompts you to choose specific CI/CD triggers before scaffolding deployment files.

Can I use this to set up deployment configuration for Python projects targeting PyPI?▼

Yes, you can use this to set up deployment configuration for Python projects targeting PyPI. The automated detection reads pyproject.toml and similar files to propose PyPI as a deployment target for your configuration.

What is the best way to initialize deployment config without actually deploying my application?▼

The best way to initialize deployment config without deploying is using an automated detection tool that scaffolds the configuration. This skill identifies targets and writes a standardized deploy.json while explicitly skipping the deployment execution step.

Why does my project need a standardized deploy.json before setting up CI/CD pipelines?▼

Your project needs a standardized deploy.json before setting up CI/CD pipelines to establish a single source of truth for target selection and triggers. This configuration file guides the subsequent scaffolding of your deployment files.