system-diagnostics

Name: system-diagnostics
Availability: InStock
Author: mrwest3

Inspect fleet heartbeats, task states, goals, and human task timers to surface system issues.

Updated Aug 27, 2026

Search Tags:#metrics #orchestrator #health-check #system-diagnostics #fleet-health #stale-tasks #goal-staleness

Ready to run

npx skills add https://github.com/MrWest3/west-command-center --skill system-diagnostics-mrwest3

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: system-diagnostics
Source: https://github.com/MrWest3/west-command-center/tree/main/templates/analyst/.claude/skills/system-diagnostics
Command: npx skills add https://github.com/MrWest3/west-command-center --skill system-diagnostics-mrwest3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

System diagnostics identify and surface system issues that disrupt agent productivity, such as tasks that are stuck, goals not updating, or fleet health problems, enabling proactive remediation.

Core Features & Use Cases

Stale Task Detection: identify in-progress or pending tasks that have not progressed for defined thresholds.
Goal Staleness & Human Task Monitoring: surface goals not updated and overdue human tasks, sending reminders.
Fleet Health & Metrics: summarize agent heartbeats and collect key system metrics for health monitoring.
Use Case: During a heartbeat, automatically generate a health report and surface critical blockers to the orchestrator.

Quick Start

Run a system health diagnostic on the next orchestrator heartbeat to surface stale tasks, overdue goals, and fleet health insights.

Frequently Asked Questions about system-diagnostics

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

FAQPage Schema

How do I detect stale tasks and monitor fleet health during an orchestrator heartbeat?▼

To detect stale tasks and monitor fleet health, run a system diagnostic during the orchestrator heartbeat to inspect agent heartbeats, task states, and goals, surfacing critical blockers for remediation.

What is goal staleness and how do I surface overdue human tasks in my system?▼

Goal staleness occurs when system goals are not updated within expected thresholds, and you can surface overdue human tasks by running diagnostics that inspect human task timers and send reminders.

How do I set up automated health checks to surface stuck in-progress tasks?▼

Automated health checks surface stuck in-progress tasks by inspecting fleet heartbeats and task states against defined progression thresholds, requiring access to agent heartbeats, task status, and metrics.

Can I use system diagnostics to collect fleet health metrics and generate automated reports?▼

Yes, system diagnostics summarize agent heartbeats and collect key fleet health metrics, supporting automated reporting to surface findings and critical blockers directly to the orchestrator and user.

What data access is required to identify system issues and detect goal staleness?▼

Identifying system issues and detecting goal staleness requires access to agent heartbeats, task status, goals, and metrics to evaluate progression thresholds and human task timers.

When should I run system diagnostics to prevent agent productivity blockers?▼

You should run system diagnostics during every heartbeat or when the orchestrator flags a potential problem to proactively detect stale tasks, goal staleness, and fleet health issues before they disrupt productivity.