competitor-watch

Featured

Use when an already-named set of rivals is watched on a cadence — pricing, features, positioning and changelog diffed into a maintained tracker plus an append-only, classified change log. NOT sizing the market or choosing who the rivals are (that is `market-research`), NOT one-off page extraction (that is `data-scraper`).

AI & Automation 116 stars 9 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
69
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# competitor-watch You run a **standing watch**, not a one-shot study. You take an *already-named* set of rivals and keep them under dated observation along four axes — positioning, pricing, features, and change-over-time. The deliverable is not a snapshot of the market; it is the **time series** of what each rival moved, when, and what you do about it. Competitive intelligence is a **repeating cycle**, not a report you write and file: the taught cycle runs **Orient → Gather → Analyze → Report → Act**, then loops with a fresh orientation informed by the last pass (competitiveintelligencealliance.io, accessed 2026-06-02). Two near-misses decide the routing (the rest are in **Handoffs**, below). `../market-research/SKILL.md` answers *"what is the market and who is in it"* once, and often **produces the list you watch** — you are the downstream loop that watches that list forever. `../data-scraper/SKILL.md` owns the generic mechanics of pulling data off a page on demand; you *use* change detection as a means, but your identity is the maintained tracker + classified change log + cadence. "Extract this one table once" → data-scraper. "Keep watching these five companies" → you. ## Ethics gate — runs FIRST, before any capture Legitimate CI is **legal + ethical collection from public, observable sources** with your identity disclosed. SCIP's Code of Ethics is the industry line (scip.org, accessed 2026-06-02). The practical gate is the **front-page test**: would you be comfortable...

Details

Author
ericrisco
Repository
ericrisco/rsc-harness
Created
3 months ago
Last Updated
2 days ago
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

competitor-monitoring

Keep watch on competitors (and, where sources allow, industry people) on a schedule and report only real changes. Use when someone wants a competitor monitored, asks what a watched company has been doing, wants to change or stop a watch — and always when a scheduled run tells you to. Triggers include "watch", "keep an eye on", "monitor competitor", "what is the competition doing", "what changed at X", "stop watching", and their German equivalents ("beobachte", "behalte im Auge", "was macht der Wettbewerb").

156 Updated yesterday
HybridAIOne
AI & Automation Featured

competitive-intel-watch

Scheduled delta monitoring against a prior competitive snapshot. Use when tracking competitors on a cadence: material shifts only, cited evidence, battle-card update flags, runs unattended.

7,083 Updated 3 weeks ago
deanpeters
AI & Automation Listed

competitive-intelligence

Continuous competitive intelligence and competitor change detection. Use when the user asks to monitor competitors over time, refresh existing competitor profiles, detect what changed since a prior scan, track pricing/product/positioning/SEO/ads/reviews/company changes, maintain a competitor watchlist, produce recurring competitor digests, verify competitor claims, analyze cross-competitor trends, or turn observed deltas into product/GTM/sales implications. Prefer competitor-profiling for a one-time initial deep profile; use this skill when temporal state, snapshots, deltas, alerts, freshness, evidence provenance, or recurring intelligence operations matter.

1 Updated today
CometWeb-io