Track web page changes, detect availability issues, and preserve content with multiple monitoring strategies.
Works with
Supports four major monitoring services (Visualping, ChangeTower, Distill.io, UptimeRobot) with different strengths: visual change detection, compliance archiving, element-level tracking, and uptime monitoring
Includes ready-to-use Python implementations for local page monitoring with hash-based change detection, element selectors, and automatic archiving
Covers RSS feed gene
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpage-monitoringExecute the skills CLI command in your project's root directory to begin installation:
Fetches page-monitoring from jamditis/claude-skills-journalism and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate page-monitoring. Access via /page-monitoring in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
103
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
103
stars
Patterns for tracking web page changes, detecting content removal, and preserving important pages before they disappear.
| Service | Free Tier | Best For | Storage | Alert Speed |
|---|---|---|---|---|
| Visualping | 5 pages | Visual changes | Standard | Minutes |
| ChangeTower | Yes | Compliance, archiving | 12 years | Minutes |
| Distill.io | 25 pages | Element-level tracking | 12 months | Seconds |
| Wachete | Limited | Login-protected pages | 12 months | Minutes |
| UptimeRobot | 50 monitors | Uptime only | 2 months | Minutes |
// Distill.io allows CSS/XPath selectors for precise monitoring
// Example selectors for common use cases:
// Monitor news article headlines
const newsSelector = '.article-headline, h1.title, .story-title';
// Monitor price changes
const priceSelector = '.price, .product-price, [data-price]';
// Monitor stock/availability
const availabilitySelector = '.in-stock, .availability, .stock-status';
// Monitor specific paragraph or section
const sectionSelector = '#main-content p:first-child';
// Monitor table data
const tableSelector = 'table.data-table tbody tr';
import requests
import hashlib
import json
import smtplib
from email.mime.text import MIMEText
from datetime import datetime
from pathlib import Path
from typing import Optional
from bs4 import BeautifulSoup
class PageMonitor:
"""Simple page change monitor with local storage."""
def __init__(self, storage_dir: Path):
self.storage_dir = storage_dir
self.storage_dir.mkdir(parents=True, exist_ok=True)
self.state_file = storage_dir / 'monitor_state.json'
self.state = self._load_state()
def _load_state(self) -> dict:
if self.state_file.exists():
return json.loads(self.state_file.read_text())
return {'pages': {}}
def _save_state(self):
self.state_file.write_text(json.dumps(self.state, indent=2))
def _get_page_hash(self, url: str, selector: str = None) -> tuple[str, str]:
"""Get content hash and content for a page or element."""
response = requests.get(url, timeout=30, headers={
'User-Agent': 'Mozilla/5.0 (PageMonitor/1.0)'
})
response.raise_for_status()
if selector:
soup = BeautifulSoup(response.text, 'html.parser')
element = soup.select_one(selector)
content = element.get_text(strip=True) if element else ''
else:
content = response.text
content_hash = hashlib.sha256(content.encode()).hexdigest()
return content_hash, content
def add_page(self, url: str, name: str, selector: str = None):
"""Add a page to monitor."""
content_hash, content = self._get_page_hash(url, selector)
self.state['pages'][url] = {
'name': name,
'selector': selector,
'last_hash': content_hash,
'last_check': datetime.now().isoformat(),
'last_content': content[:1000], # Store preview
'change_count': 0
}
self._save_state()
print(f"Added: {name} ({url})")
def check_page(self, url: str) -> Optional[dict]:
"""Check single page for changes."""
if url not in self.state['pages']:
return None
page = self.state['pages'][url]
selector = page.get('selector')
try:
new_hash, new_content = self._get_page_hash(url, selector)
except Exception as e:
return {
'url': url,
'name': page['name'],
'status': 'error',
'error': str(e)
}
changed = new_hash != page['last_hash']
result = {
'url': url,
'name': page['name'],
'status': 'changed' if changed else 'unchanged',
'previous_content': page['last_content'],
'new_content': new_content[:1000] if changed else None
}
if changed:
page['last_hash'] = new_hash
page['last_content'] = new_content[:1000]
page['change_count'] += 1
# Archive the change
archive_file = self.storage_dir / f"{hashlib.md5(url.encode()).hexdigestMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Useful defaults in page-monitoring — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in page-monitoring — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend page-monitoring for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
page-monitoring is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
page-monitoring reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: page-monitoring is the kind of skill you can hand to a new teammate without a long onboarding doc.
page-monitoring is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: page-monitoring is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: page-monitoring is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for page-monitoring matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 30