product-price-monitor

Monitor product, flight, and listing prices on a schedule and alert on threshold conditions.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill product-price-monitor-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-price-monitor
Source: https://github.com/loteiron/ZeusAgent/tree/main/skills/productivity/product-price-monitor
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill product-price-monitor-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually re-checking prices for products, flights, hotels, or tickets is repetitive and easy to forget, and naive alerts often fire on the wrong variant, pre-tax prices, or duplicate offers. This Skill sets up a recurring price watch that normalizes all-in pricing and only alerts when a real, deterministic condition is met. ## Core Features & Use Cases - Precise Watch Contracts: Pins the exact item, variant, dates, travelers, seller, and alert condition in a state file under ~/.zeus/price-watches/ so two variants cannot be confused. - Scheduled Ticks via Cronjob: Runs recurring checks with the cronjob tool, normalizing currency, fees, taxes, shipping, and availability into comparable observations. - Duplicate Suppression and Failure Safety: Stores last-good observations and alert fingerprints so replays send no second alert, and failed fetches never overwrite known-good state. - Use Case: Ask the agent to alert you when a specific laptop drops below $1,000 all-in; it fetches a live baseline, schedules a 6-hour check, and notifies you only when the threshold is genuinely crossed. ## Quick Start Set up a price watch that alerts me when the flight from SFO to Tokyo on my dates drops below $500 all-in.

Frequently Asked Questions about product-price-monitor

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

FAQPage Schema
How do I set up a price alert for a product or flight?▼

Define the exact item with URL, variant, dates, and alert condition, then run one successful foreground fetch with web_extract to establish a baseline. After that, a cronjob is created to re-check on a schedule such as every 6 hours and alert only when the condition is met.

How does price monitoring avoid duplicate alerts?▼

The watch stores the last good observation and last alert fingerprint in a state file under ~/.zeus/price-watches/. Replaying the same offer sends no second alert, and a configurable cooldown controls how often notifications can fire.

Can it track hotel rooms or ticket availability, not just prices?▼

Yes, the alert condition can be an availability or stock rule, such as a refundable hotel room or ticket listing appearing. The same normalization and duplicate-suppression logic applies to availability changes as to price thresholds.

What happens when a price check fetch fails?▼

A failed fetch is treated as unknown state: the run is reported or skipped, but the error page never overwrites the last good observation in the state file. This prevents false alerts caused by blocked requests or broken pages.

When should I not use a scheduled price monitor?▼

Do not use it for one-off price lookups; a direct web_search or web_extract call answers those immediately. It is designed for ongoing watches where a recurring cron tick compares normalized prices against a stored baseline.