batch-health

Audit scheduled skills against aeon.yml and classify batch runs as OK, WARN, or OUTAGE.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill batch-health
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: batch-health
Source: https://github.com/aaronjmars/aeon/tree/main/skills/batch-health
Command: npx skills add https://github.com/aaronjmars/aeon --skill batch-health

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Prevents silent failures in scheduled skills by auditing whether all enabled batch-running skills actually triggered during their expected morning window.

Core Features & Use Cases

  • Expected vs. Actual Run Auditing: Builds an expected list from aeon.yml by evaluating cron-like schedules against the 06:00–07:30 UTC audit window.
  • Severity Classification: Produces OK, WARN (1–2 isolated misses), or OUTAGE (3+ missing skills) outcomes based on what actually ran.
  • Issue Filing & Notification: Files or skips a batch outage issue in memory/issues on OUTAGE and sends notifications on WARN or OUTAGE, then logs results to memory/logs for traceability.
  • Fallback Logging: Uses a best-effort memory/logs/${today}.md parse if skill-run telemetry fails.

Quick Start

Ask an AI operator to run the batch-health audit for today and alert you if any scheduled skills failed to trigger in the 06:00–07:30 UTC window.

Frequently Asked Questions about batch-health

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

FAQPage Schema
How do I detect silent cron job failures in scheduled tasks?▼

Detect silent cron job failures by auditing expected versus actual skill runs during a specific morning batch window. It cross-references scheduled tasks against execution logs to classify missing runs as OK, WARN, or OUTAGE.

What is the best way to monitor unattended daily scheduled jobs for outages?▼

Monitor unattended daily scheduled jobs by evaluating cron-like schedules against the 06:00–07:30 UTC audit window. The mechanism checks actual runs and files memory issues when silent outages occur.

How do I automate issue triage for missing scheduled skill runs?▼

Automate issue triage by classifying missing runs into OK, WARN (1–2 isolated misses), or OUTAGE (3+ missing skills). It conditionally files batch outage issues in memory and sends notifications.

Does batch monitoring work when skill-run telemetry is unavailable?▼

Batch monitoring works without standard telemetry by using a best-effort fallback. It parses memory logs to cross-reference actual runs when standard skill-run tracking fails.

How do I classify the severity of a missed scheduled task execution?▼

Classify missed scheduled task severity by counting missing skills during the expected window. Isolated misses trigger a WARN, while three or more missing skills indicate an OUTAGE requiring notification.

When do I need automated daily batch monitoring for cron-driven skills?▼

Automated daily batch monitoring is needed when running unattended cron-driven skills where silent outages can occur. It ensures reliability by verifying that all enabled tasks triggered successfully.