competitor-radarlisted

# competitor-radar Weekly competitive intelligence skill. Batch operation: define competitors once, run a snapshot weekly, read the synthesis report. No external subscriptions or monitoring services required. ## When to use this skill - Weekly competitive intelligence sweep: run on Mondays or before the Friday `weekly-review-coach` session. - Before a pricing change: verify your anchor analysis is still current. - Before a fundraise: investors will ask "who else is doing this?" - When a prospect mentions a competitor you haven't tracked before: add it to the config and run a fresh snapshot. ## When NOT to use this skill - Real-time monitoring: this is a batch skill. For real-time alerts, use Google Alerts or a dedicated monitoring service. - Legal intelligence (M&A signals, patent filings): use a proper CI firm. - Login-gated pages: WebFetch cannot authenticate. Public pages only. ## Phase A — Setup Define your competitor list in: ``` ~/.config/walter-os/state/competitors.yml ``` **This file is operator-private and must never be committed to any repo.** Schema: ```yaml competitors: - name: Competitor Name changelog_url: https://competitor.com/changelog pricing_url: https://competitor.com/pricing careers_url: https://competitor.com/jobs blog_url: https://competitor.com/blog ``` See `references/sample-competitors.yml` for a filled example with three fictional companies. **All four URL fields are optional**: include only pages that exist and