watchdog

Monitor the genspark-agent server on port 8766 and restart it via HTTP or file trigger.

1|1|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/Birdywen/genspark-agent --skill watchdog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: watchdog
Source: https://github.com/Birdywen/genspark-agent/tree/main/skills/watchdog
Command: npx skills add https://github.com/Birdywen/genspark-agent --skill watchdog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a watchdog service that monitors the main genspark-agent server and automatically restarts it when needed, ensuring high availability and minimizing downtime.

Core Features & Use Cases

  • Automatic restart: Periodically checks the main server and triggers a restart when issues are detected or after configuration changes.
  • Safe restart workflow: Includes a cooldown period to prevent rapid restarts and data loss.
  • Use Case: Maintain uptime for a local server setup during development or production runs, especially after config updates or error conditions.

Quick Start

To enable and start the watchdog, run the provided scripts to launch both the watchdog on port 8766 and the main server on port 8765, then verify status with the health endpoint.

Frequently Asked Questions about watchdog

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

FAQPage Schema
How do I automatically restart a local server when it crashes or after a config update?

To automatically restart a local server, a watchdog service monitors port 8766 and coordinates with the main server on port 8765, triggering a restart via HTTP or file trigger to ensure continuous uptime.

What is a watchdog service and how does it monitor server uptime?

A watchdog service monitors server uptime by periodically checking the main server and triggering a restart when issues are detected or after configuration changes, enforcing a 5-second cooldown to prevent data loss.

Can I use an automatic restart watchdog in a production environment?

Yes, the automatic restart watchdog is applicable in production environments to maintain high availability and minimize downtime, safely recovering the server after runtime failures or configuration updates.

How do I start the watchdog and verify the main server health status?

Start the watchdog by running the provided scripts to launch the watchdog on port 8766 and the main server on 8765, then verify the main server health status using the /health or /status HTTP endpoints.

Why does my server watchdog enforce a cooldown period before restarting?

The server watchdog enforces a 5-second cooldown period to prevent rapid restarts and data loss, ensuring a safe restart workflow when issues are detected or after configuration changes.