watch

Watch — Feed Source Registry

Lists, adds, and removes feed sources that Distillery monitors for ambient intelligence. Changes are persisted to the database and survive server restarts. Sources defined in distillery.yaml are seeded into the database on first startup.

When to Use

• See registered feed sources (/watch list)
• Add a new feed source (/watch add <url>)
• Remove a feed source (/watch remove <url>)
• Natural language: "list my sources", "add a feed", "stop watching X", "remove source"

Process

Step 1: Check MCP

See CONVENTIONS.md — skip if already confirmed this conversation.

Step 2: Parse Arguments

Invocation pattern	Action	Extra args
/watch or /watch list	list	none
/watch add <url> [--type TYPE] [--label LABEL]	add	url, optional source_type, label
/watch remove <url> [--purge]	remove	url, optional purge (requires explicit confirmation before purge)

Default to list if no subcommand is recognizable.

For add, parse:

• First non-flag argument: source URL (required)
• --type TYPE: adapter type (default: rss). Valid: rss, github, hackernews, webhook
• --label LABEL: human-readable label (optional)
• --interval N: poll interval in minutes (default: 60)
• --trust N: trust weight in [0.0, 1.0] (default: 1.0)

If add is requested without a URL, ask the user before proceeding.

Step 3: Execute Action

Call distillery_watch with the parsed arguments:

• list: distillery_watch(action="list")

• add: distillery_watch(action="add", url=..., source_type=..., label=..., poll_interval_minutes=..., trust_weight=...)

• remove (no purge): distillery_watch(action="remove", url="<url>")

• remove --purge (requires explicit confirmation):

  1. Explain to the user that --purge will archive all historic entries previously ingested from <url>. This skill's allowlist only includes mcp__*__distillery_watch, so the exact count cannot be fetched here — describe the impact in-prompt instead of issuing a distillery_list call.
  2. Ask for explicit confirmation (e.g., "Archive all historic entries from <url>? This cannot be undone without re-ingesting. [yes/no]").
  3. Only after the user replies with an unambiguous affirmative (e.g., yes), call distillery_watch(action="remove", url="<url>", purge=true). Report the archived count returned by the tool when confirming to the user.

• On MCP errors, see CONVENTIONS.md error handling — display and stop

Step 4: Auto-Poll Schedule (after add only)

After a successful add, remind the user about routine-based polling.

If no feed poll routine is configured, display:

No feed poll routine found. Run /setup to configure scheduled routines.

If the user already has routines configured (they confirm when asked), skip to Step 5.

Step 5: Confirm

Source table format (used for list and after add/remove):

Feed Sources (N configured)

| # | URL | Type | Label | Poll (min) | Trust |
|---|-----|------|-------|-----------|-------|
| 1 | https://example.com/rss | rss | Example | 60 | 1.0 |

If no sources: show "No feed sources configured." with usage hint.

• After add: show added source details, updated table, and auto-poll status
• After remove: confirm removal, show updated table. If --purge was used, also report the number of archived entries
• After remove --purge: "Removed source and archived N historic entries."

Changes are persisted to the database automatically — no manual YAML editing required.

Rules

• Default subcommand is list when no arguments are provided
• Validate source_type is one of: rss, github, hackernews, webhook
• Do not proceed with add without a URL
• Always show the updated source table after add or remove
• After add, remind the user to run /setup if no feed poll routine is configured
• Scheduling uses Claude Code routines for all transport modes — CronCreate and webhook scheduling are deprecated
• On MCP errors, see CONVENTIONS.md error handling — display and stop
• Trust weight: 0.0–1.0 (default 1.0); poll interval: positive integer minutes (default 60)