GPT-5 finding
Non‑standard cron expressions in aeon.yml (likely never fire)
mediumbughigh
- aeon.yml
- aeon.yml
Standard 5‑field cron typically supports steps only as */N or RANGES like 1-31/2, not bare 1/2 or 1/7 in the day‑of‑month field. These expressions are out of convention with the rest of the file and will be rejected or misinterpreted by common cron parsers. This risks these skills never running when enabled.
Recommendation
Change to portable expressions: - self-improve: use "0 18 */2 * *" (every 2 days) or "0 18 1-31/2 * *" if your parser requires a range - smithery-manifest: use "0 6 */7 * *" (every 7 days) or a weekly day-of-week schedule like "0 6 * * 0" if Sunday is intended. Also add schedule validation in your scheduler to fail fast on invalid cron strings.