agent-management

Manage West Command Center agent lifecycles via CLI and PM2.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MrWest3/west-command-center --skill agent-management-mrwest3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-management
Source: https://github.com/MrWest3/west-command-center/tree/main/templates/analyst/.claude/skills/agent-management
Command: npx skills add https://github.com/MrWest3/west-command-center --skill agent-management-mrwest3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently manage the entire lifecycle of West Command Center agents—from creation and configuration to restarts and credential handling—ensuring reliable, auditable operations.

Core Features & Use Cases

  • Centralized agent lifecycle management: create, restart, enable/disable, update models/configs, and manage credentials.
  • Cross-organizational workflows: spawn or administer agents for other users and orgs with guardrails and auditability.
  • Safe credential handling: guidance on .env creation and secure token management to prevent credential leakage and the Becky bug.
  • Reliable operations: integration with PM2, bus-based restarts, and health checks to keep agents healthy and responsive.

Quick Start

Create a new agent via the CLI, prepare the .env with bot token and chat credentials, then enable the agent within the appropriate org.

Frequently Asked Questions about agent-management

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

FAQPage Schema
How do I manage agent lifecycles including restarts and config updates via CLI?

Agent lifecycle management via CLI lets you create, restart, enable, disable, and update models or configurations for agents. It uses PM2 process management and bus-based restarts to keep operations reliable and responsive.

What is the safest way to handle Telegram bot tokens and credentials in .env files?

Safe credential handling requires validating your .env files to securely manage bot tokens and chat credentials. This prevents credential leakage and avoids the Becky bug, ensuring reliable cross-organizational operations.

Can I spawn and administer agents for other users across different organizations?

Cross-organizational workflows allow you to spawn, enable, or disable agents for other users and organizations. These actions include guardrails and auditability to ensure safe and reliable administration.

Does PM2 process management work with bus-based restarts for agent orchestration?

PM2 process management integrates with bus-based restarts and health checks to orchestrate agents. This combination keeps your agents healthy, responsive, and ensures reliable operations across organizations.

What are the limitations or precautions when changing agent models and configurations?

When changing agent models and configurations, you must follow safe restart workflows and validate .env credentials. Precautions include preventing credential leakage and maintaining guardrails for cross-user agent administration.

Why do I need .env validation for CLI-based agent orchestration?

.env validation is required for CLI-based agent orchestration to securely handle tokens and chat credentials. It safeguards against credential leakage and ensures agents spawn and operate with the correct configuration.