All skills
deanpeters avatar

/competitive-intel-watch

@eb7a51e

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.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/competitive-intel-watch

This session only. Nothing lands on disk.

template.md

≈605 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Competitive Watch Report Template

Copy this for each watch run. A watch reports change, not state — the reader's question is "what changed since last time?", and "no material shifts this cycle" is a valid, useful answer. Diff against the prior snapshot; never regenerate it. Section order is stable so runs can be diffed against each other.

Every claimed change carries a URL and a date — the date is half the evidence.

Template

# Competitive Watch Report

## 1. Run Header
**Scope (from prior snapshot):** [copy it — if the scope itself changed, re-baseline instead and say so]
**Prior snapshot date:** [YYYY-MM-DD]
**This run date:** [YYYY-MM-DD]
**Competitors checked:** [list]

## 2. Changelog (Material Shifts Only)
_The materiality bar: report a change only if a sales rep, pricing owner, or roadmap owner would
plausibly act on it. Below the bar: cosmetic site changes, routine content marketing, minor releases._

### [Competitor] — [4 to 8 word change summary]
- **What changed:** [1-2 bullets, labeled Fact/Inference]
- **Evidence:** [URL, date — archive/diff link where possible]
- **So what:** [why it clears the materiality bar — who acts on it]
- **Confidence:** [high / medium / low]

_If nothing cleared the bar:_ "No material shifts this cycle." _Then list anything on the
watchlist for next run — a quiet cycle is reported, not padded._

## 3. Update Flags
_Only rows with real updates; omit the rest. A changelog with no flags usually means the shift
didn't actually clear the bar._

| Downstream artifact | Sections needing update | Driven by |
|---|---|---|
| Battle card | | |
| Positioning statement | | |
| Pricing/packaging analysis | | |
| Roadmap assumptions | | |

## 4. Watchlist for Next Run
- [Signals below the bar but trending]
- [Open questions this run could not resolve]

### Assumptions to Validate
- [Assumption 1]
- [Assumption 2]
- [Assumption 3]

Quality checks before you call it done

  • Every changelog entry has URL and date — undated evidence can't be verified or diffed next run
  • Every entry's "So what" names who would act (rep, pricing owner, roadmap owner) — if nobody would, it's watchlist material
  • The prior snapshot was read fully before searching — the diff target is the document, not your memory of the market
  • If the cycle was quiet, the report says so plainly instead of promoting below-bar noise

Source: SKILL.md on GitHub

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill is a competitive intelligence workflow designed to monitor market shifts by comparing new web data against previous research snapshots. It identifies changes in competitor pricing, positioning, and roadmaps. The skill includes built-in safety features such as requiring cited evidence for all claims and establishing human-review checkpoints for scheduled or unattended executions. No security issues were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

Signed by skilld at eb7a51e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 3 months ago
argument-hint
[prior snapshot (pasted/attached), and anything specific to watch]
type
workflow
theme
market-intelligence
Other metadata
intent
A competitive intelligence delta monitor: given a previous Competitive Research Snapshot, sweep for material shifts since the last run and report only what changed — a cited changelog plus flags naming which battle card or positioning sections now need updating. Designed to run unattended on a loop or schedule; an empty changelog is a valid, useful result.
best_for
[
  "Keeping battle cards and positioning current without regenerating research weekly",
  "Running unattended on a schedule and reporting only changes a rep or roadmap owner would act on",
  "Turning competitive research from a one-off deliverable into a standing capability"
]
scenarios
[
  "Run this against last quarter's snapshot and tell me what actually changed",
  "Set up a monthly competitor watch that flags when our battle card goes stale"
]
estimated_time
10-25 min per run (after the baseline exists)

README badge

README badge for deanpeters/product-manager-skills/competitive-intel-watch