status

Display an orchestrator system status dashboard with agent, skill, and memory counts.

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/eroslifestyle/Claude-Orchestrator-Plugin --skill status-eroslifestyle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/eroslifestyle/Claude-Orchestrator-Plugin/tree/main/github-package/skills/status
Command: npx skills add https://github.com/eroslifestyle/Claude-Orchestrator-Plugin --skill status-eroslifestyle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, consolidated view of the orchestrator's operational health and resource utilization, helping users quickly assess system readiness.

Core Features & Use Cases

  • System Overview: Displays counts for agents, skills, rules, memory, learnings, plugins, and sessions.
  • Health Indicators: Flags potential issues with warnings if critical components are missing or underutilized.
  • Use Case: Before initiating a complex task, a user can run /status to ensure all necessary agents and skills are available and that the system is not overloaded.

Quick Start

Run /status to see the current orchestrator system status dashboard.

Frequently Asked Questions about status

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

FAQPage Schema
How do I display my orchestrator system status dashboard?

To display the orchestrator system status dashboard, run the /status command to generate a comprehensive overview of agents, skills, rules, memory, plugins, and sessions. This dashboard provides a consolidated view of operational health and resource utilization.

What system health metrics are included in a status overview?

The system status overview includes counts of agents by tier, loaded skills, active rules, memory status and size, learning instincts, connected MCP plugins, and saved sessions. It also features health indicators that flag potential issues with warnings for missing or underutilized components.

Why should I check system health before running complex tasks?

You should check system health before running complex tasks to ensure all necessary agents and skills are available and the system is not overloaded. Verifying operational readiness prevents task failures caused by missing resources or critical components.

Does the status dashboard show connected MCP plugins and active rules?

Yes, the status dashboard explicitly shows connected MCP plugins and active rules. It details these components alongside agents, memory status, and saved sessions to provide a clear picture of the orchestrator's current configuration.

What do the health indicators flag when checking orchestrator resource utilization?

The health indicators flag potential issues by displaying warnings if critical components are missing or underutilized. This helps you quickly identify and resolve resource bottlenecks before initiating workflows.

Can I see memory status and agent counts by tier in the system overview?

Yes, you can see memory status and size alongside detailed counts of agents by tier in the system overview. This breakdown helps you assess whether the orchestrator has sufficient capacity and memory for upcoming operations.