CamelCamelCamel Alerts

**Judgement:** Reasonable, narrowly scoped price-alert monitor that broadly matches its description, but with underspecified wiring to Telegram and some technical rough edges. Best suited for users comfortable editing cron jobs and shell/Python scripts. **What it does well:** - Polls a CamelCamelCamel RSS feed for price-drop alerts and outputs structured information about new items. - Uses a simple JSON cache file under `/tmp/camelcamelcamel/cache.json` to avoid repeat alerts in principle. - Keeps Telegram integration indirect: it emits formatted `ALERT|...` lines for an external Clawdbot/host messaging tool to deliver, so this skill doesn’t manage tokens. **Key risks / limitations:** - **Dependency mismatch:** Manifest doesn’t declare required tools (at least `python3`, `jq`, `cron`, and a Clawdbot/host messaging mechanism). Missing deps will cause runtime failures that aren’t obvious from the manifest. - **Documentation inconsistencies:** SKILL.md’s Quick Start cron example calls only `fetch_rss.py`, while SETUP.md pipes `fetch_rss.py` through `jq '.alerts'` into `notify.sh`. The latter is needed for notifications to actually be produced. - **Unreliable deduplication:** The cache uses Python’s built-in `hash()` for keys, which is randomized between processes. This likely breaks stable deduplication and can cause duplicate notifications across runs unless the script is patched (e.g., to use `hashlib.sha256`). - **Delivery pipeline under-specified:** `notify.sh` assumes something else reads its `ALERT|title|message|link` lines and forwards them to Telegram. If your environment doesn’t have that wired up, nothing will be delivered. - **Transient cache location:** Using `/tmp` means the cache may be cleared on reboot, which can trigger a burst of re-notifications unless relocated to a persistent directory. **Recommended scenarios:** - You already run Clawdbot or a similar host that: - has Telegram configured and - can consume `ALERT|...` lines and send chat messages accordingly. - You’re comfortable adjusting cron jobs and, if needed, editing `fetch_rss.py` to use a stable hash and changing the cache path. - You want a small, auditable component to fetch and filter CamelCamelCamel alerts and prefer to keep credential handling outside this skill. If you expect a plug-and-play Telegram integration or don’t want to touch the code/cron setup, this skill will likely require more manual work and may not be ideal without improvements to its dependency declarations, documentation, and cache logic.