Monthly Update Detector
Nightly detection of skills stale past 25 days with a weekly Telegram digest so a solo maintainer refreshes high-value skills deliberately, not via auto-timestamp bumps.
Overview
Monthly Update Detector is a MCP server for the Operate phase that lists skills stale after 25 days and notifies you weekly without auto-changing file dates.
What is this MCP server?
- Nightly 03:00 CT scan of newest file mtime per skill
- Flags skills whose newest file crossed 25 days stale
- Writes data/curator/stale-skills-<date>.md stale lists
- Never auto-bumps timestamps; only Cooper decides refreshes
- Sunday 09:30 CT weekly Telegram digest sorted by quality_score (high-value first)
- 25-day staleness threshold on newest file mtime
- Nightly scan at 03:00 CT
- Weekly Telegram digest Sunday 09:30 CT
What problem does it solve?
Skill repos go stale silently and you cannot tell which high-value skills need a human refresh versus safe neglect.
Who is it for?
Solo maintainers of large agent skill folders who want scheduled staleness reports and human-in-the-loop refresh only.
Skip if: Teams wanting automatic skill updates, version bumps, or CI that rewrites mtimes without review.
What do I get? / Deliverables
You receive dated stale-skill markdown and a Sunday Telegram digest prioritized by quality_score while timestamps stay honest.
- data/curator/stale-skills-<date>.md per scan
- Weekly Telegram digest of stale skills sorted by quality_score
Recommended MCP Servers
Journey fit
How it compares
MCP catalog staleness monitor, not a dependency updater or semantic version bot.
Common Questions / FAQ
Who is monthly-update-detector for?
Builders curating many skills in dailyai-os-style repos who need nightly staleness lists and a weekly prioritized Telegram summary.
When should I use monthly-update-detector?
Use it once your skill count makes manual freshness checks impractical and you commit to Cooper-only refresh decisions.
How do I add monthly-update-detector to my agent?
Register io.github.dailyaiagents-cpu/monthly-update-detector, ensure skill paths are scannable, configure Telegram for the Sunday 09:30 CT digest, and read outputs from data/curator/stale-skills-<date>.md.