pm2

Manage Node.js processes with startup, monitoring, and automatic restarts.

7|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/LvcidPsyche/polymarket-arbitrage-bot --skill pm2-lvcidpsyche
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm2
Source: https://github.com/LvcidPsyche/polymarket-arbitrage-bot/tree/main/skills/pm2
Command: npx skills add https://github.com/LvcidPsyche/polymarket-arbitrage-bot --skill pm2-lvcidpsyche

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PM2 provides a reliable, centralized way to run and manage Node.js applications in production, replacing ad-hoc scripts and manual restarts.

Core Features & Use Cases

  • Deploy and manage Node.js applications with PM2
  • Monitor real-time logs, perform zero-downtime reloads, and configure auto-start on boot
  • Manage multiple processes and simple clustering for load distribution

Quick Start

Start by installing PM2 globally and using it to start your Node.js app.

Frequently Asked Questions about pm2

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

FAQPage Schema
How do I manage Node.js applications in production without manual restarts?

Process management for Node.js applications uses a centralized daemon to handle startup, monitoring, and auto-restarts, replacing ad-hoc scripts and manual restarts in production deployments.

Can I configure Node.js apps to auto-start on boot with zero-downtime reloads?

Yes, process management tools support boot-time auto-start generation and zero-downtime reloads, ensuring Node.js applications remain available across single or multiple servers.

How do I monitor real-time logs for multiple Node.js processes?

You can monitor real-time logs through log aggregation features, managing multiple processes and simple clustering for load distribution from a centralized daemon interface.

What is the best way to distribute load across multiple Node.js processes?

Simple clustering manages multiple processes to distribute load, meeting requirements for global installation and commands like start, stop, restart, logs, and list.

Do I need an ecosystem configuration for advanced Node.js deployments?

Optional ecosystem configuration is available for advanced deployments, while basic global installation and standard commands handle standard production workflows.

Why does my Node.js app crash without auto-restart in production?

Without a centralized process management daemon, Node.js applications lack automatic restarts and monitoring, requiring manual intervention or ad-hoc scripts to recover from crashes.