Website Change Watcher

v1.0.0

Monitor website/docs/pricing changes, diff meaningful updates, and summarize business impact with alert-ready reports.

0· 108·0 current·0 all-time
byASP@anugotta
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name, description, and the workflow (capture snapshots, diff, classify, alert) are internally consistent. The skill does not request unrelated binaries, environment variables, or config paths.
Instruction Scope
SKILL.md describes monitoring, diffing, classification, and publishing alerts but remains high-level; it does not instruct the agent to read unrelated files or secrets. It also omits operational specifics (how to schedule periodic checks, how alerts are delivered, how to handle authenticated/protected pages or robots.txt).
Install Mechanism
No install spec or code files — instruction-only, so nothing will be written to disk or downloaded during install.
Credentials
The skill declares no required environment variables or credentials. In practice, delivering alerts to Slack/email/issue trackers will require user-supplied credentials or webhooks; the SKILL.md does not request or document those, which is an operational omission but not a coherence/privilege problem.
Persistence & Privilege
always is false and there is no install-time persistence. The skill does not request elevated or cross-skill privileges.
Assessment
This is an instruction-only skill that appears to do what it says and doesn't request secrets or install code. Before installing or using it: (1) decide where alerts will be sent — you will need to supply webhooks/credentials for Slack, email, or issue trackers and verify the agent's access to them; (2) confirm whether you will monitor only public pages (respect robots.txt and legal/scrape policies) or authenticated pages (you'll need to provide credentials securely); (3) clarify retention and storage of snapshots (sensitive content could be collected); and (4) ask the skill author (or inspect any runtime integration) for details about scheduling and where diffs/archives are stored. If you want, I can list specific credentials/webhooks the skill would need to integrate with common alert channels or produce a safer operational checklist.

Like a lobster shell, security has layers — review code before you run it.

latestvk972w88wy4rvjg1xynzpsnrv5n836b8w

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🛰️ Clawdis

Comments