Claude
Skill
website-monitor
Detect changes in price, content, tenders, or availability and alert only on meaningful deltas. Use with cron or .navin/HEARTBEAT.md for recurring checks.
Virus-scanned
Reviewed automatically before listing.
Download
navinspire-ia-navin-navin_skills_website-monitor-e9c73a3.zip · 0 KB
Install
skills CLI
npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/website-monitor
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git
git clone https://github.com/Navinspire-ia/navin.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Website Monitor
Overview
Periodic watch with quiet success. Store a baseline fingerprint; notify on delta.
Workflow
- Define URL, CSS/text target, and what counts as a change.
- Fetch current content with
web_fetch, or thebrowsertool when the page renders client-side. - Normalize (strip volatile bits: dates, CSRF tokens, ads).
- Compare to baseline file e.g.
monitoring/<slug>.jsonin the workspace:- hash or extracted fields (price, status, headline)
- If changed: update baseline + notify with old → new.
- Schedule via:
cronwhen the user wants reports in chat.navin/HEARTBEAT.mdwhen silence is preferred unless changed
Baseline schema
{
"url": "...",
"extracted": {"price": "12.00", "status": "in_stock"},
"hash": "...",
"checked_at": "..."
}
Rules
- Do not spam on every HTML churn - compare extracted fields.
- Include the URL and timestamp in alerts.
Files (navin)
-
SKILL.md 1.2 KB
--- name: website-monitor description: Detect changes in price, content, tenders, or availability and alert only on meaningful deltas. Use with cron or .navin/HEARTBEAT.md for recurring checks. metadata: {"navin":{"emoji":"📡","category":"navigation"}} --- # Website Monitor ## Overview Periodic watch with quiet success. Store a baseline fingerprint; notify on delta. ## Workflow 1. Define URL, CSS/text target, and what counts as a change. 2. Fetch current content with `web_fetch`, or the `browser` tool when the page renders client-side. 3. Normalize (strip volatile bits: dates, CSRF tokens, ads). 4. Compare to baseline file e.g. `monitoring/<slug>.json` in the workspace: - hash or extracted fields (price, status, headline) 5. If changed: update baseline + notify with **old → new**. 6. Schedule via: - `cron` when the user wants reports in chat - `.navin/HEARTBEAT.md` when silence is preferred unless changed ## Baseline schema ```json { "url": "...", "extracted": {"price": "12.00", "status": "in_stock"}, "hash": "...", "checked_at": "..." } ``` ## Rules - Do not spam on every HTML churn - compare extracted fields. - Include the URL and timestamp in alerts.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.