create-pm2-clj-config

Generate PM2-clj ecosystem configuration files with EDN DSL and environment blocks.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill create-pm2-clj-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pm2-clj-config
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/create-pm2-clj-config
Command: npx skills add https://github.com/open-hax/opencode-skills --skill create-pm2-clj-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of pm2-clj ecosystem configuration files to manage PM2-based services across systems, orgs, and packages.

Core Features & Use Cases

  • Create new ecosystem configs from scratch or templates.
  • Place generated files in system/daemons, orgs, or packages directories.
  • Support EDN DSL for pm2-clj with env blocks, per-environment settings, and logging options.
  • Validate and test configurations using clobber render and clobber start workflows.

Quick Start

Provide the required details (name, script, env, ports) and run the assistant to generate the new ecosystem.pm2.clj at the appropriate location.

Frequently Asked Questions about create-pm2-clj-config

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

FAQPage Schema
How do I generate a PM2 ecosystem configuration file for a new application?

You can create pm2-clj ecosystem configs from scratch or templates by providing details like name, script, env, and ports. The generated ecosystem.pm2.clj file uses an EDN DSL and is placed in system/daemons, orgs, or packages directories to manage PM2-based services.

What is the pm2-clj DSL used for when managing PM2 services?

The pm2-clj DSL is used to define ecosystem configurations for PM2-based services within an EDN format. It supports environment blocks, per-environment settings, and logging options to manage applications across system daemons, org services, or package-level deployments.

Does pm2-clj support environment-specific configuration blocks for different deployments?

Yes, pm2-clj supports environment blocks and per-location configuration settings. You can define per-environment settings and logging options within the EDN DSL to manage services across different system, org, or package deployments.

How do I validate and test a pm2-clj configuration before deploying?

You can validate and test pm2-clj configurations using clobber render and clobber start workflows. These workflows provide test-start guidance to ensure your generated ecosystem configuration file works correctly before actual deployment.

Can I use a template to create a new ecosystem.pm2.clj file instead of starting from scratch?

Yes, you can create new ecosystem configs from scratch or by using templates. Providing the required details such as the application name, script, environment, and ports allows the assistant to generate the configuration file at the appropriate location.