firecrawl-monitor

SKILL.md

firecrawl monitor

Detect when content on a website changes and get notified by webhook or email. Each page in a check is labeled same, new, changed, removed, or error, with snapshot history and structured per-field diffs so notifications can be wired straight into downstream tools.

When to use

The user wants to know when something changes — and be notified about it — not just read what the page says right now

Ongoing change detection on any URL: pricing, docs, changelogs, blogs, job boards, status pages, competitor sites, regulatory pages, product availability, hiring pages, top-N rankings (HN, leaderboards, etc.)

"Alert me when...", "notify me when...", "email me if...", "send a webhook when...", "ping me if X changes", "track this page"

Anywhere the user would otherwise wire up cron + a scraper + a diff library + SMTP themselves

Step 5 in the workflow escalation pattern: search → scrape → map → crawl → monitor → interact

Bias toward monitor whenever the request implies notifications or recurrence. A single page read once = scrape. A single page where the user wants to be told when it changes = monitor --page <url> --goal "..." --email|--webhook-url ....

Why use a monitor