competitor-intellisted

# Competitor Intel Scans competitor websites (and, at the deep tier, LinkedIn ad libraries), diffs the result against the last scan, and writes a briefing a person actually reads. Everything the skill learns about a company lives in a `competitor-intel/` folder inside the current project — never in this skill folder, never in any repo this skill ships from. **Paths in this file.** `scripts/…` and `references/…` are relative to **this skill's folder**. `competitor-intel/…` is relative to the **current working directory** — the user's project. This skill deliberately works in two roots at once, so every script invocation below needs the skill folder's own path in front of it (written `<skill>/scripts/…`), while `competitor-intel/…` arguments stay relative to the project. ## Routing Check for `competitor-intel/company.md` in the current working directory. - Missing → run **Intake**. - Present, user said `scan` or gave no argument → run **Scan**. - Present, user said `setup` → re-run **Intake** against the existing files (confirm before overwriting). - Present, user said `report [run-id]` → run **Report** (no re-scraping — read the existing `runs/<run-id>/snapshot.json` and `changes.json`, or the latest run if `run-id` is omitted, and regenerate `briefing.md` from them per `references/briefing-format.md`). ## Intake **Always ask the intake question, even when the project looks pre-loaded and the setup seems obvious.** Do not infer company or competitor details from t