Cron Self Heal
Surface scheduled jobs that are failing so your agent can triage cron health before users or revenue workflows break.
Overview
cron-self-heal is an MCP server for the Operate phase that reports cron jobs in error and flags RED when over 33% are failing.
What is this MCP server?
- Watcher MCP skill that surfaces crons currently in an error state
- RED health when more than 33% of crons are failing; YELLOW otherwise
- MIT-licensed DailyAI Agents federation skill (spec_version 1.0)
- Capability tags: cron, heal, self, skill—oriented to self-healing operations loops
- Roadmap note: glob-match per-skill expected_output_glob frontmatter for richer health checks
- RED threshold when greater than 33% of crons are failing
- MIT license; federation spec_version 1.0
- Server version 0.1.0; subfolder skills/cron-self-heal in dailyai-os repo
What problem does it solve?
Silent cron failures pile up until billing, emails, or backups stop, and solo operators lack a single agent-visible health signal.
Who is it for?
Builders running DailyAI-style agent OS with many scheduled skills who want automated cron health surfacing.
Skip if: Teams without cron-based automation or those needing full Grafana-style metrics and SLO dashboards from this server alone.
What do I get? / Deliverables
After install, your agent can read cron error state and a RED/YELLOW summary so you fix or heal jobs before cascading outages.
- List of crons in error state exposed to the agent
- Aggregate health label RED (>33% failing) or YELLOW
- Foundation for follow-on self-heal or rerun workflows
Recommended MCP Servers
Journey fit
Operate is where recurring jobs run in production; this MCP watcher belongs on the monitoring shelf for live cron reliability. Monitoring subphase matches a RED/YELLOW health signal based on failing cron share, not feature development.
How it compares
Cron health watcher MCP skill, not a general log aggregator or PaaS cron scheduler.
Common Questions / FAQ
Who is cron-self-heal for?
Solo builders and small teams using DailyAI Agents cron automation who want MCP-visible job failure rates.
When should I use cron-self-heal?
Use it in Operate when you run recurring agent or bash crons and need RED/YELLOW triage before implementing self-heal fixes.
How do I add cron-self-heal to my agent?
Add the MCP server from the dailyai-os skills/cron-self-heal subfolder per registry metadata, connect your MCP client, and ensure your cron definitions are visible to the watcher.