Skip to content

ericrisco/rsc-harness / skills/competitor-watch

competitor-watch

Verified

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`).

FileKindSize
SKILL.mdskill md12.3 KB
evals/README.mdmarkdown1.5 KB
evals/cases.yamlconfig4.0 KB
references/monitoring-config.mdmarkdown5.1 KB
references/tracker-schema.mdmarkdown5.2 KB
scripts/verify.shexecutablescript10.3 KB

references/monitoring-config.md

View on GitHub
# Monitoring config: the runnable stack

The default you can actually run is **`changedetection.io`** — open-source, self-hosted, no
vendor lock-in. It does text/visual, **XPath/CSS-selector**, and **JSON-API (JSONPath / jq)**
change detection; checks as often as ~1 minute; notifies via Slack/Discord/Telegram/email/API;
and ships AI change summaries like "Price dropped from \$89.99 to \$67.00"
(github.com/dgtlmoon/changedetection.io, accessed 2026-06-02).

## Self-host: docker-compose

```yaml
# docker-compose.yml — changedetection.io + a Playwright fetcher for JS-heavy pages
services:
  changedetection:
    image: ghcr.io/dgtlmoon/changedetection.io
    container_name: changedetection
    ports:
      - "5000:5000"
    volumes:
      - ./datastore:/datastore
    environment:
      - PLAYWRIGHT_DRIVER_URL=ws://playwright-chrome:3000
      - BASE_URL=https://watch.internal.example.com
    restart: unless-stopped
  playwright-chrome:
    image: dgtlmoon/sockpuppetbrowser:latest
    container_name: playwright-chrome
    restart: unless-stopped
```

Bring it up with `docker compose up -d`, open `http://localhost:5000`, and add one watch per
watched URL from the competitor profile.

## Per-axis watch definitions

Each watch = URL + selector + cadence. Map straight from the watch-list table in `SKILL.md`.

```text
# Pricing (time-sensitive → 5–15 min)
URL:       https://acme.com/pricing
Filter:    css:.price-amount          # CSS selector for the price node only
Cadence:   00:10:00                   # 10 minutes
Notify:    tgram://<token>/<chat_id>  # Telegram on change

# Features / changelog (daily)
URL:       https://acme.com/changelog
Filter:    css:.changelog li:nth-child(-n+5)   # first 5 release items
Cadence:   1 day

# Positioning / homepage (weekly)
URL:       https://acme.com
Filter:    css:h1.hero-title, css:.hero-subtitle
Cadence:   7 days
```

### JSON-API pricing (when price comes from an endpoint, not HTML)

If the pricing page hydrates from an API, watch the API and pin the exact field with JSONPath
— far more stable than scraping rendered HTML.

```text
URL:       https://acme.com/api/v2/plans
Filter:    json:$.plans[?(@.id=='pro')].monthly_price
Cadence:   00:10:00
```

### AI change summary (optional)

changedetection.io can attach an LLM that turns a raw diff into one line ("Pro monthly went
from \$49 to \$59"). Enable it per-watch when the page is noisy and you want the classification
pre-chewed — but you still own the axis + materiality call; the summary is an input, not the log.

## Notification wiring

Point the notify URL at where your team already lives. Common targets:

```text
tgram://<bot_token>/<chat_id>          # Telegram
slack://<token_a>/<token_b>/<token_c>  # Slack
discord://<webhook_id>/<webhook_token> # Discord
post://watch.internal.example.com/hook # your own webhook → automation-flows
```

The *scheduling and downstream routing* of those webhooks (cron, retries, fan-out into a
tracker write) is automation wiring → `../automation-flows/SKILL.md`. This skill defines the
watches; that skill makes them run reliably on a schedule.

## Wayback Machine — historical reconstruction ONLY

The Wayback Machine is a **passive archive, not a monitor**. It captures *some* snapshots (a
pricing page may be archived once in months, or never) and **does not tell you when something
changed**. Use it to reconstruct what a rival's page said in the past — never as the live
alerting layer.

Its "Changes" diff compares two existing captures (added = blue, deleted = yellow):

```text
# Compare two captured timestamps of the same URL
https://web.archive.org/web/diff/<TS1>/<TS2>/https://acme.com/pricing
# e.g. TS = 20260101000000 (YYYYMMDDhhmmss)
https://web.archive.org/web/diff/20260101000000/20260501000000/https://acme.com/pricing
```

(archive.org "Compare two versions", accessed 2026-06-02.) Good for "how did their positioning
read 6 months ago"; useless for "alert me when it changes."

## Self-host vs paid SaaS — when each is the right call

| Option | Price (accessed 2026-06-02) | Right call when |
|---|---|---|
| **changedetection.io** (self-host) | free / infra cost only | Default. You want a config you run, full selector control, no vendor. |
| Visualping | from ~\$10/mo | A few pages, want zero ops, visual diffs. |
| ChangeTower | from ~\$9/mo | Same — lightweight page monitor, hosted. |
| Kompyte | ~\$20K avg ARR (entry ~\$300/yr, 1–2wk setup) | You need site+social+filings 24/7 and a dedicated CI owner. |
| Crayon | median ≈\$28.7K/yr (~\$12K–\$47K, 7–8wk setup) | Many rivals, auto-updated battlecards, priced by # competitors. |
| Klue | ~\$16K–\$42.7K/yr (Basic/Standard/Premium, by seats) | Large CI team splitting "curators" vs "consumers." |

(vendr.com/marketplace/crayon, autobound.ai "Top 15 CI tools 2026", kompyte.com comparison,
visualping.io — accessed 2026-06-02.)

The paid suites also auto-update **battlecards** — but the battlecard itself is a sales
artifact owned by `../sales-pipeline/SKILL.md`, not this skill. A self-host config covers most
teams; reach for a suite only when breadth (many rivals, many surfaces, 24/7) outgrows what one
config + one owner can maintain.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall