Help us improve
Share bugs, ideas, or general feedback.
Generates a monitoring plan for tracking web page changes using change-detection tools, RSS feeds, or custom scripts with webhook alerts.
npx claudepluginhub ur-grue/autopunk-media-skills --plugin autopunk-media-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/autopunk-media-skills:page-monitoringThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produces a monitoring plan for tracking changes to a target web page over time — covering change-detection tools, RSS-based monitoring, webhook alerts, and a structured process for logging and archiving each detected change.
Detects website content changes and sends notifications via webhook or email. Uses AI to filter out noise so only meaningful changes trigger alerts. Good for monitoring pricing, docs, job postings, and status pages.
Creates and manages long-running web monitors that track page changes on a recurring cadence (hourly/daily/weekly). Use to monitor pricing, filings, competitor pages, or any web content that changes over time.
Sets up Yutori Scouts for continuous web monitoring to track news, competitors, product updates, funding rounds, price changes, or recurring web information.
Share bugs, ideas, or general feedback.
Produces a monitoring plan for tracking changes to a target web page over time — covering change-detection tools, RSS-based monitoring, webhook alerts, and a structured process for logging and archiving each detected change.
Required: The URL(s) to monitor; what kind of change you are watching for (any change, text changes only, specific sections, new documents added, deletion of content) Optional: How often you need to check (hourly, daily, weekly); how long the monitoring needs to run; whether you need historical diff records or just an alert when something changes; the number of pages you are monitoring (affects tool choice)
Selects the right monitoring method based on the page and the need. Three main approaches, chosen by fit:
Dedicated change-detection tools (Visualping, ChangeTower, Distill.io): Best for monitoring specific sections of a page (a data table, a press-release list, a paragraph of text). These tools take periodic snapshots and compare them, alerting you by email or webhook when a difference is detected. Suitable when you need visual or text-level diff records.
RSS-based monitoring: Some government and institutional sites publish RSS feeds for press releases, document libraries, or news sections. If an RSS feed exists, it is the most reliable and least resource-intensive way to track new publications. The skill checks whether the target page has an associated RSS feed and guides the user to subscribe via a feed reader (Feedly, Inoreader, or a self-hosted reader like FreshRSS).
Custom scripting with webhook alerts: For advanced users or newsrooms with technical support. A lightweight script (using a tool like Huginn, changedetection.io, or a cron job with curl and diff) can poll a page at set intervals, compare the response to the previous version, and send an alert via email, Slack, or webhook. Best for monitoring multiple pages at scale or for pages that change-detection services cannot handle (dynamic content, API endpoints, authenticated pages).
Configures the monitoring. Walks through setup step by step for the chosen method: what to monitor (full page vs. specific CSS selector or section), how often to check, what threshold of change triggers an alert (any change, or only changes above a certain character count — to filter out ad rotation and timestamp updates), and where to send alerts.
Sets up archiving for each detected change. Every time a change is detected, the old version and the new version should both be preserved. Guides the user to configure automatic archiving (some tools support this natively) or to set up a manual workflow: receive alert, immediately archive the current page (see web-archiving skill), save the diff, and log the change in a monitoring log.
Creates a monitoring log template. A structured log the reporter maintains, recording: date of change, what changed (summary), archive URLs for before/after versions, and any editorial notes on the significance of the change.
Three sections. First: a recommended monitoring method with setup instructions (200–400 words, step-by-step). Second: an archiving workflow for detected changes (100–200 words). Third: a monitoring log template. Total length: 400–700 words. Procedural register — instructions, not description.
URL: https://www.national-energy-authority.example.gov/data/emissions-quarterly-report Context: This page publishes quarterly emissions data from the national energy authority. Last quarter, the authority quietly revised downward two figures in the Q1 report after publication without issuing a correction notice. We want to catch any future revisions to the Q2 data, which was published last week. Monitoring should run for at least three months. I am not technical — I need a tool I can set up without writing code.
Recommended method: Visualping (change-detection tool)
Visualping is a web-based service that takes periodic screenshots of a page and alerts you when the visual content changes. It requires no coding. Free tier allows monitoring up to 2 pages with daily checks; paid plans ($14/month) allow hourly checks and more pages.
Setup:
https://www.national-energy-authority.example.gov/data/emissions-quarterly-report.Alternative check: RSS. Before relying solely on Visualping, check whether the authority publishes an RSS feed for data updates. Look for an RSS icon on the page, or try appending /feed or /rss to the domain. Government data portals sometimes offer notification feeds for updated datasets. If an RSS feed exists, subscribe in a feed reader (Feedly is free) as a redundant alert channel.
Archiving workflow for detected changes
When Visualping sends an alert:
If the authority deletes the page entirely, Visualping will report "page not found." In that case, your most recent archive becomes the last known version. Archive.today snapshots are more resilient than Wayback Machine for this purpose — prioritise checking that archive.
Monitoring log
| Date | Change detected | Summary of change | Before archive URL | After archive URL | Notes |
|---|---|---|---|---|---|
| [date] | [yes/no alert] | [e.g., "Q2 SO₂ figure revised from 14,200 to 12,800 tonnes"] | [Wayback/Archive.today URL of previous version] | [Wayback/Archive.today URL of current version] | [editorial note: significance, whether correction notice was issued] |