monitor-system

Monitor system health across watchers and MCP servers with automatic recovery.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/HafizFasih/Autonomous-FTEs --skill monitor-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-system
Source: https://github.com/HafizFasih/Autonomous-FTEs/tree/main/.claude/skills/monitor-system
Command: npx skills add https://github.com/HafizFasih/Autonomous-FTEs --skill monitor-system

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires psutil, requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Monitor system health to detect errors and trigger auto-recovery for continuous operation, reducing downtime and manual intervention.

Core Features & Use Cases

  • Continuous health monitoring across Watchers and MCP servers
  • Automatic error recovery with exponential backoff and escalation
  • Comprehensive audit logging and system status reporting

Quick Start

Instruct the AI to start continuous system health monitoring and automatic recovery.

Frequently Asked Questions about monitor-system

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

FAQPage Schema
How do I automate system health monitoring and trigger recovery for continuous operation?

Automated system health monitoring detects errors and triggers auto-recovery to maintain continuous operation. It monitors across multiple watchers and MCP servers, applying health scoring and automated restarts with exponential backoff to reduce downtime and manual intervention.

How does automatic error recovery with exponential backoff handle persistent issues?

Automatic error recovery uses exponential backoff for automated restarts and triggers escalation when issues persist. This mechanism ensures that failing system components are not flooded with restart attempts, preserving system stability while escalating unresolved health errors.

Can I monitor system health across multiple MCP servers simultaneously?

Continuous health monitoring applies to multiple watchers and MCP servers simultaneously to maintain uptime. It tracks system health scores across your infrastructure, generating comprehensive audit logs and system status reports for your entire operational scope.

Do I need psutil and requests installed to run continuous system health monitoring?

Yes, continuous system health monitoring requires the psutil and requests dependencies to function. These libraries enable the Skill to accurately gauge system health metrics and execute automated recovery requests across your operational environment.

What is the best way to maintain uptime and reduce manual intervention for failing services?

The best way to maintain uptime is continuous health monitoring combined with automated recovery and audit logging. This approach automatically detects system errors, applies backoff restart strategies, and escalates persistent issues, drastically reducing manual intervention.

Why does the system recovery process include audit logging and status reporting?

System recovery includes audit logging and status reporting to provide a comprehensive record of health monitoring and automated actions. This ensures full visibility into when errors were detected, how exponential backoff was applied, and when escalations were triggered.