cron-healthcheck

Detect failing Hermes cron jobs and escalate remediation tasks hourly.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/TechNickAI/hermes-config --skill cron-healthcheck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cron-healthcheck
Source: https://github.com/TechNickAI/hermes-config/tree/main/skills/cron-healthcheck
Command: npx skills add https://github.com/TechNickAI/hermes-config --skill cron-healthcheck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects broken Hermes cron jobs and escalates remediation to a dedicated sub-agent. The system triages issues on a cheap model and delegates diagnosis and fixes to an expensive sub-agent, reducing downtime and manual triage effort.

Core Features & Use Cases

  • Two-tier cron health monitoring: cheap hourly triage flags problems and delegates remediation to an expensive sub-agent.
  • Silent healthy state: when all cron jobs are healthy, there are no notifications or noisy alerts.
  • Fleet-wide reliability: efficient monitoring across many cron jobs with minimal resource usage and clear escalation paths.

Quick Start

Install the cron-healthcheck skill and schedule it to run hourly to monitor cron jobs.

Frequently Asked Questions about cron-healthcheck

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

FAQPage Schema
How do I automate monitoring for failing Hermes cron jobs?

Monitor Hermes cron jobs by deploying an hourly two-tier health check that triages failures on a cheap model. It escalates diagnosis and remediation to an expensive sub-agent, reducing manual triage effort and downtime.

How does two-tier self-healing cron monitoring work?

Two-tier cron monitoring works by running hourly triage on a cheap model to flag problems. When issues are detected, it escalates diagnosis and fixes to an expensive sub-agent, keeping run state locally in the Hermes environment.

Do I need specific tools to run cron health checks with delegated remediation?

Yes, cron health checks with delegated remediation require cron tooling, delegation capabilities, and a notification channel for escalations. Run state is maintained in the local Hermes environment while operating across a fleet of jobs.

What is the best way to monitor a large fleet of cron jobs without noisy alerts?

The best way to monitor a cron fleet without noisy alerts is using a silent healthy state monitor. Notifications only trigger when broken jobs are detected, ensuring efficient fleet-wide reliability with minimal resource usage.

Why does my automated cron remediation require a sub-agent?

Automated cron remediation requires a sub-agent to handle complex diagnosis and fixes. The system uses a cheap model for initial hourly triage to save resources, delegating only actual failures to an expensive sub-agent for resolution.