cyberneticlibrary

Monitor competitors weekly for changes

competitor-monitorskillsetup L30
fivebucksventures/fiveagents-marketplace
What it does

Track competitor website changes, pricing updates, and exec movements weekly

Best for

Competitive intelligence teams running weekly monitoring on 5-15 competitors to surface material product, pricing, and leadership changes.

Inputs
  • · brands/{brand}/competitors.md (competitor roster with monitor URLs)
  • · brands/{brand}/brand.md (locale, voice, signal thresholds)
  • · Weekly scan window (default: prior 7 days Monday-Sunday)
  • · Prior week's HTML snapshots (implied from persistent storage)
Outputs
  • · Weekly diff report with classified changes
  • · Archived snapshots in Notion
  • · Slack alerts for high-signal events (pricing changes, executive moves, product launches)
  • · Searchable changelog of competitor activity
Requires
  • · HTML scraping and diff tools (not specified)
  • · Notion archive integration
  • · Slack notification service
  • · WebSearch or web scraper for competitor URL monitoring
  • · LinkedIn scraping for exec movement detection
Preconditions
  • · brands/{brand}/competitors.md configured with monitor_urls, track_pages, exec_team, signal_thresholds
  • · Notion and Slack integrations connected
  • · Prior week snapshots stored for diffing
Failure modes
  • · Requires HTML snapshot persistence — breaks if storage fails
  • · Competitor URL monitoring assumes stable URLs — site redesigns may require re-configuration
  • · Exec movement detection via LinkedIn limited by public profile visibility
  • · False positives in change classification if signal thresholds not tuned
Trust signals
  • · Named configuration structure (monitor_urls, track_pages, exec_team, signal_thresholds)
  • · Degraded mode fallback (homepage-only scan if competitors.md incomplete)
  • · Per-URL focus rules documented (pricing → plan changes; careers → exec roles; blog → launches; changelog → any entry)
  • · Weekly cron-triggered execution model specified