watchers

Poll RSS feeds, JSON APIs, and GitHub activity with watermark deduplication.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/devMoez/titan --skill watchers-devmoez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: watchers
Source: https://github.com/devMoez/titan/tree/main/optional-skills/devops/watchers
Command: npx skills add https://github.com/devMoez/titan --skill watchers-devmoez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the hassle of manually checking feeds and APIs by automatically polling external sources and only reporting brand-new items.

Core Features & Use Cases

  • RSS/Atom watching: Polls an RSS 2.0 or Atom feed and emits only entries whose ID/guid has not been seen before.
  • JSON endpoint polling: Polls any JSON API and emits only new objects based on a configurable ID field and dotted items path.
  • GitHub activity watching: Watches GitHub issues, pulls, releases, or commits and deduplicates by stable identifiers (issue id or commit sha).
  • Stateful watermark deduplication: Maintains a per-watcher watermark file so the skill stays silent on no-change and avoids replays.
  • Ideal use cases: “Notify me when something changes,” scheduled monitoring, and cron-style automations for regular updates.

Quick Start

Run the RSS watcher to check for new items every 15 minutes and only output changes, for example: Watchers polls the RSS feed https://news.ycombinator.com/rss and prints up to 5 new headlines using state name hn.

Frequently Asked Questions about watchers

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

FAQPage Schema
How do I poll an RSS feed for new items without getting duplicate notifications?

RSS feed polling uses persistent watermark deduplication to store seen item IDs and only emit newly observed entries. It maintains a per-watcher state file to stay silent on empty deltas and avoid repeated notifications.

Can I monitor a JSON API endpoint and only output newly added objects?

JSON API monitoring polls any endpoint and emits only new objects based on a configurable ID field and dotted items path. It stores observed IDs to deduplicate outputs and prevent replays of existing data.

What is the best way to watch GitHub repository activity like issues, pulls, and releases?

GitHub activity watching monitors issues, pulls, releases, or commits and deduplicates by stable identifiers like issue IDs or commit SHAs. It compares new activity against a stored bounded set to output only new changes.

Does this deduplication watcher work with scheduled cron-driven automations?

The watcher works with scheduled monitoring, cron-driven automations, and terminal ad-hoc checks. It updates state atomically after each fetch and outputs Markdown for new items, making it suitable for regular cron execution.

Why does my RSS watcher stay silent and output nothing on subsequent runs?

The watcher stays silent when no new items are found, meaning all current feed entries match the stored watermark of previously seen IDs. This prevents duplicate notifications and is the expected behavior for empty deltas.

Do I need any external dependencies to run scheduled feed monitoring?

Scheduled feed monitoring requires no external dependencies and runs as standalone scripts. It fetches external data, compares item IDs against a stored bounded set, updates state atomically, and outputs Markdown for new items.