PM2 Process Manager

**Quick judgement** This skill is a focused integration around the PM2 process manager, suitable for managing Node.js production services (including Next.js) via standard PM2 commands. It appears mature and practical for environments where PM2 is already installed and used as the primary process manager. **What it’s good for** - Managing the lifecycle of Node.js apps: start, stop, restart, reload, delete, list. - Viewing and tailing logs, including targeted log inspection for specific apps. - Setting up auto-start on boot and persisting the process list. - Running clustered Node.js services across multiple CPU cores and handling memory-based restarts. - Operating production builds (e.g., Next.js) using PM2 with ecosystem files. **Risks / limitations** - Commands like `pm2 delete`, `pm2 kill`, and `pm2 unstartup` can disrupt production services if misused. - Log access (`pm2 logs`) may expose sensitive information (env vars, tokens, user data) in logs. - No explicit safeguards or guardrails are evident against stopping critical services or altering startup behavior. - Assumes a working PM2 installation and correct system-level permissions; misconfiguration can lead to startup scripts that don’t behave as expected. **Recommended scenarios** Use this skill on servers where PM2 is the established process manager and you need automated or AI-assisted control of Node.js services: zero-downtime deployments, log inspection, and boot persistence. Avoid granting it uncontrolled use on highly sensitive or mission-critical systems unless you layer additional policy checks or human review over destructive commands (e.g., `delete`, `kill`, `unstartup`).