Source Watch
The generic watcher. Fetch a source, decide whether anything matches, suppress
what was already reported, and say something only when there is news. Every
other watcher in this pack is a fork of this one.
Configure
The user supplies these; ask for a missing source or match before the first
run. Never ask for the memory key — derive it from the source.
| Setting |
Meaning |
Example |
| Source |
The URL to fetch |
https://example.com/releases |
| Match |
What counts as interesting |
"any version above 3.0" |
| Memory key |
Optional. Where seen items are recorded, only when the user asks you to keep track across chats |
watch:example-releases |
Procedure
- Recall what was already reported.
recall(query="<memory key>", limit=50). Add every item you already
reported earlier in this conversation — those count as seen even when
memory holds nothing. This is what stops the watcher telling the user the
same thing every run.
- Fetch the source.
fetch_page(url). If the fetch fails, report the
failure and stop — an empty page is not "no news", and treating it as such is
how a watcher silently dies.
- Extract the candidate items. Titles, versions, prices, listings —
whatever the source is a list of. Keep a stable identifier per item so step 4
can compare across runs.
- Apply the match, then drop every item whose identifier already appeared in
step 1.
- Report or stay quiet. If nothing new matched, say "nothing new" in one
line. Do not pad a quiet run into a paragraph. When something did match,
give each item as a link to its page (
[title](url)), falling back to the
source URL when the item has no page of its own. Report before any memory
write.
- Record what you reported — only if the user asked you to remember or
keep track of it. Memory refuses page text the user did not ask to save,
and "watch" or "check" alone is not that ask, so otherwise skip this step;
step 1 still dedupes within this conversation. When they did ask, save only
the identifier, never a summary copied from the page:
remember(fact="<memory key>: <identifier>", category="fact") for each new
item.
A refused or failed remember never replaces the report. Give the report
anyway and say in one line that it was not saved. Do not retry the save or
stop to ask about it.
Honest limits
- This runs when you ask it to. GAIA's scheduler can run a recurring
prompt (
gaia schedule add --cron ... --prompt ...), but it cannot yet run a
skill on a schedule — --skill is rejected at creation time. Until that is
wired, "watching" means you invoke the skill and it checks.
- Remembering across conversations needs memory enabled and the user's ask to
keep track. Without both, the watcher dedupes only within this
conversation and repeats itself in a new one — say so rather than pretending
it de-duplicated.
- Fetch only pages you are allowed to poll, and do not hammer a source.
Fork this
Copy the directory, rename it and its name field, then specialize step 3
(what an item is) and step 4 (what counts as interesting). price-watch in this
pack is exactly that fork.
1---2name: source-watch3description: Check a web page or feed for something worth telling the user about, remembering what was already reported so nothing repeats. Use when the user asks to watch, monitor, or check a URL for changes, new items, or a condition being met.4license: MIT5version: 1.1.16metadata:7 gaia:8 security_tier: community9 permissions:10 - network:read11 tools_required:12 - fetch_page13 - recall14 - remember15 provenance:16 source: https://skillmd.com/skills/amd/source-watch17 upstream: starter-pack18---1920# Source Watch2122The generic watcher. Fetch a source, decide whether anything matches, suppress23what was already reported, and say something only when there is news. Every24other watcher in this pack is a fork of this one.2526## Configure2728The user supplies these; ask for a missing source or match before the first29run. Never ask for the memory key — derive it from the source.3031| Setting | Meaning | Example |32|---|---|---|33| Source | The URL to fetch | `https://example.com/releases` |34| Match | What counts as interesting | "any version above 3.0" |35| Memory key | Optional. Where seen items are recorded, only when the user asks you to keep track across chats | `watch:example-releases` |3637## Procedure38391. **Recall what was already reported.**40 `recall(query="<memory key>", limit=50)`. Add every item you already41 reported earlier in this conversation — those count as seen even when42 memory holds nothing. This is what stops the watcher telling the user the43 same thing every run.442. **Fetch the source.** `fetch_page(url)`. If the fetch fails, report the45 failure and stop — an empty page is not "no news", and treating it as such is46 how a watcher silently dies.473. **Extract the candidate items.** Titles, versions, prices, listings —48 whatever the source is a list of. Keep a stable identifier per item so step 449 can compare across runs.504. **Apply the match**, then drop every item whose identifier already appeared in51 step 1.525. **Report or stay quiet.** If nothing new matched, say "nothing new" in one53 line. Do not pad a quiet run into a paragraph. When something did match,54 give each item as a link to its page (`[title](url)`), falling back to the55 source URL when the item has no page of its own. Report before any memory56 write.576. **Record what you reported — only if the user asked you to remember or58 keep track of it.** Memory refuses page text the user did not ask to save,59 and "watch" or "check" alone is not that ask, so otherwise skip this step;60 step 1 still dedupes within this conversation. When they did ask, save only61 the identifier, never a summary copied from the page:62 `remember(fact="<memory key>: <identifier>", category="fact")` for each new63 item.6465A refused or failed `remember` never replaces the report. Give the report66anyway and say in one line that it was not saved. Do not retry the save or67stop to ask about it.6869## Honest limits7071- **This runs when you ask it to.** GAIA's scheduler can run a recurring72 *prompt* (`gaia schedule add --cron ... --prompt ...`), but it cannot yet run a73 *skill* on a schedule — `--skill` is rejected at creation time. Until that is74 wired, "watching" means you invoke the skill and it checks.75- Remembering across conversations needs memory enabled and the user's ask to76 keep track. Without both, the watcher dedupes only within this77 conversation and repeats itself in a new one — say so rather than pretending78 it de-duplicated.79- Fetch only pages you are allowed to poll, and do not hammer a source.8081## Fork this8283Copy the directory, rename it and its `name` field, then specialize step 384(what an item is) and step 4 (what counts as interesting). `price-watch` in this85pack is exactly that fork.