Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    automation health monitoring

    1

    Deploy zero-dependency watchdogs to catch and alert on automation failures in real-time.

    $5

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    automation health monitoring

    automation health monitoring

    Example session with this skill installed

    My content pipeline stopped working three days ago and I just realized it today. Set up a watchdog so this never happens again.

    • Read your context and instructions
    • Compiled the automation health monitoring

    I have implemented a high-frequency watchdog to monitor your content pipeline. I migrated the monitoring logic to a standard-library Python script to ensure it remains functional even if your pipeline's virtual environment breaks, and configured it to alert your Telegram channel immediately upon failure.

    Automation Monitoring Implementation

    ComponentAction TakenConfiguration
    Watchdog ScriptCreated unified_health_watchdog.pyPython stdlib, no external deps
    Cron ScheduleInitialized no_agent cron*/20 * * * * (Every 20 mins)
    AlertingLinked to TELEGRAM_HOME_CHANNELImmediate paging, 1/day dedupe
    Failure DetectionLog scanning + Cron state checkSearches for exit status 1 and FAIL
    Legacy CleanupPaused daily_summary_botPrevents redundant alerts
    
# Unified Watchdog Wrapper (~/.agent-home/scripts/unified_health_watchdog.sh)
#!/bin/bash
export $(grep -v '^#' ~/.agent-home/.env | xargs)
python3 ~/.agent-home/scripts/unified_health_watchdog.py --check content-pipeline

    Next steps

    1. Send a test message via the Telegram bot to verify the connection.
    2. Intentionally trigger a script error in a staging task to confirm the 20-minute alert cycle.
    3. Review ~/.agent-home/scripts/.unified_watchdog_state.json tomorrow to ensure deduplication is working.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Eliminate silent multi-day failures in unattended pipelines.Implement stdlib-only monitors that survive environment crashes.Detect and restart dead dashboard serving processes.Integrate real-time Telegram alerts for cron job errors.

    About this skill

    The problem

    Unattended automation jobs like crons, content pipelines, and signal daemons often fail silently. Relying on once-daily scans or manual checks results in blind spots where critical services stay down for hours or days before being noticed, breaking user trust.

    What it does

    • Deploys a stdlib-only watchdog that runs every 10 to 30 minutes to catch failures in near real-time.
    • Monitors actual failure signals including cron error states, log exit statuses, and process age rather than weak proxies.
    • Implements immediate Telegram paging with per-day deduplication to prevent alert fatigue.
    • Validates serving endpoints by probing live URLs instead of assuming service health based on file freshness.
    • Automates recovery for orphaned background processes using tracked terminal sessions.

    Frameworks & tools

    Python (Standard Library), Bash, Telegram Bot API, Hermes cron systems, and WSL/Linux process management.

    Why this beats prompting it yourself

    Standard LLM prompts often suggest complex monitoring stacks that fail when the system environment breaks. This skill enforces a "zero-dependency" architecture, ensuring the monitor survives even when your main application environment or virtualenv crashes.

    Use cases

    • Wrapping a trading bot cron to ensure it never misses a signal due to an unhandled exception.
    • Monitoring a TikTok content pipeline to catch 404 model errors before the daily upload window closes.
    • Keeping long-running dashboard HTTP servers alive across reboots and OOM events.

    Known limitations

    Requires an existing Telegram bot token and channel ID for alerting. Designed specifically for local or server-based automation rather than distributed cloud-native clusters.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 6 days ago

    • Passed all security checks, Safe to install

    Listed6 days ago

    What's inside

    Frequently Asked Questions