competitor-diff

Fetches competitor pages, diffs them against stored snapshots, and posts meaningful changes to Slack.

20.2k|3.4k|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/kortix-ai/suna --skill competitor-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competitor-diff
Source: https://github.com/kortix-ai/suna/tree/main/packages/starter/templates/marketplace/runtime/skills/competitor-diff
Command: npx skills add https://github.com/kortix-ai/suna --skill competitor-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually checking competitor websites, changelogs, and pricing pages every day is tedious, and naive change-detection tools flood channels with noise from cosmetic edits. This Skill runs a daily watch loop that fetches each tracked page, diffs it against the previous run's snapshot, filters out cosmetic changes, and posts only meaningful updates to a Slack channel.

Core Features & Use Cases

  • Scheduled page diffing: A daily cron re-prompts a persistent session that fetches every URL on the watch list over plain HTTP GET and compares normalized content against the last stored snapshot.
  • Cosmetic noise filtering: Typo fixes, timestamps, layout reflows, and reordering are dropped, while pricing changes, new changelog entries, and rewritten positioning are reported.
  • Persistent ledger: Snapshots and a dated run log are maintained in .kortix/memory/competitor-watch-log.md so each run has something to diff against and fetch failures are retried.
  • Use Case: A product marketing team tracks five competitor pricing pages; each morning the Skill posts a short Slack summary only when a price, plan, or feature actually changed, staying silent on quiet days.

Quick Start

Ask the agent to run a manual competitor watch check against the current watch list and post any meaningful changes to the configured Slack channel.

Frequently Asked Questions about competitor-diff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor competitor website changes automatically?

Maintain a watch list of competitor URLs, fetch each page on a daily schedule with plain HTTP GET, normalize the content, and diff it against the previous snapshot. This Skill posts a short Slack summary only when pricing, features, or messaging actually changed.

How to filter cosmetic changes from website diff alerts?

Normalize pages before comparing by stripping nav, footers, ads, timestamps, and whitespace, then drop diffs that are typo fixes, reflowed layouts, or reordered content. Only report pricing tier changes, new changelog entries, and rewritten headlines or positioning.

Does competitor page monitoring require authentication or credentials?

No. This Skill is read-only against the public web and uses plain HTTP GET with no login or credentials. If a future tracked page requires auth, the credential must be stored encrypted in a secrets manager and injected at runtime, scoped to this agent.

What happens when a competitor page fetch fails or times out?

A failed fetch, such as a timeout, 404, or moved page, does not fail the whole sweep. The Skill notes it in the ledger as a blocker so it can be retried on the next run while the remaining pages are processed normally.

Where are competitor page snapshots stored between runs?

Snapshots live in `.kortix/memory/competitor-watch-log.md`, which records each tracked URL's normalized snapshot or hash, fetch timestamp, and a dated run log of what was reported to Slack or skipped. On the first run there is nothing to diff, so pages are fetched and stored without reporting.