Watchers — Poll RSS, JSON APIs, and GitHub with watermark dedup: Hermes Agent lesson

The idea in one minute

Start with meaning, then move to detail.

This lesson explains Watchers — Poll RSS, JSON APIs, and GitHub with watermark dedup as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?

For hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect Skill metadata, Reference: full SKILL.md, When to Use, then verify failure modes and version compatibility.

What do you need first?

Know Python, Git, and basic project structure before changing code.

What will you know?

A clear outcome before you read.

Understand Watchers — Poll RSS, JSON APIs, and GitHub with watermark dedup without assumed prior knowledge.
Separate the source description from what still needs testing in your environment.
Read the first command and identify its inputs and outputs before copying it.

Lesson terms

Short definitions before the details.

Provider: The service that runs or provides access and authentication to a model.
Skill: An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Automation: Running work later or repeatedly with explicit success and failure conditions.

Official page description

Poll RSS, JSON APIs, and GitHub with watermark dedup

Topic map

What does the source say, and in what order?

01
Skill metadata
Start here to understand the core idea or structure.
02
Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
03
When to Use
Read this after the foundation, then connect it to the previous step.
04
Mental model
Read this after the foundation, then connect it to the previous step.
05
Ready-made scripts
Read this after the foundation, then connect it to the previous step.
06
Usage
Read this after the foundation, then connect it to the previous step.
07
Wiring into cron
Read this after the foundation, then connect it to the previous step.
08
State files
Read this after the foundation, then connect it to the previous step.
09
Writing your own
Read this after the foundation, then connect it to the previous step.
10
Common Pitfalls
Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

python $HERMES_HOME/skills/devops/watchers/scripts/watch_rss.py \
  --name hn --url https://news.ycombinator.com/rss --max 5

python $HERMES_HOME/skills/devops/watchers/scripts/watch_github.py \
  --name hermes-issues --repo NousResearch/hermes-agent --scope issues

python $HERMES_HOME/skills/devops/watchers/scripts/watch_http_json.py \
  --name api --url https://api.example.com/events \
  --id-field event_id --items-path data.events

Try it now

Read the first command and identify its inputs and outputs before copying it.

Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Watchers — Poll RSS, JSON APIs, and GitHub with watermark dedup” changes?An undated postThe official Hermes docs and repositoryAn unsourced search result

2. What is the best way to apply this lesson?Copy every command at onceRun a small step and verify the resultGrant every permission to save time

3. What should happen before a step can modify files or an external account?Review scope, permissions, and recoveryDisable isolationPaste the key into chat