Menu

Individual skill

competitor-monitoring

0upvotes

Use this skill when you need to know what rival companies are doing — "what are my competitors doing", "competitor update", "competitor news", "competitive landscape", "market intel", "what's new with [company]", "track [company]", "competitor briefing", "who's making moves", "we keep losing deals to [company]" — or before a board meeting, battlecard refresh, or strategy session that needs competitive context. Produces a structured intelligence briefing — funding, M&A, leadership moves, product launches, hiring waves, partnerships — with every signal date-verified against its primary source and deduped against a running memory file per competitor, so each run surfaces only what is new.

skills/alon-goldenberg/competitor-monitoring/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Competitor monitoring

Runs whenever someone needs a current read on the competitive landscape — on a cadence, before a strategy conversation, or the moment a rival's name comes up in a lost deal. Produces a dated, source-linked intelligence briefing of genuinely new competitor moves, plus an updated running memory per competitor so the next run starts where this one ended.

The failure mode this skill exists to prevent: a briefing that confidently reports last quarter's funding round as this week's news because a recap article was published yesterday. Everything below is built around one distinction — **when a page was published vs. when the event actually happened** — and a memory that remembers what you already reported.

## Set up the profile (first run only)

1. Ask for the company's website domain, then search the live web for the domain to confirm you have the right company. Confirm with the user before proceeding.
2. Build the competitor list one of two ways: the user names them, or you propose them — run three parallel searches ("[Company] competitors", "[Company] vs", "[Company] alternatives"), synthesize a candidate list, and get explicit confirmation. Never research a competitor list the user hasn't approved.
3. For each confirmed competitor, capture name, domain, and category (direct, adjacent, incumbent). Also capture 2–3 industry keywords for trend searches.
4. Save all of this to a profile file in your workspace, alongside a `competitors/` directory that will hold one running memory file per competitor and a `briefings/` directory for saved runs.

## Pick the run mode
Back to top