competitor-news-monitor

Monitors named companies for material news and delivers cited digests on a schedule.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Chia1104/agent-air --skill competitor-news-monitor-chia1104
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: competitor-news-monitor
Source: https://github.com/Chia1104/agent-air/tree/main/skills/hermes/research/competitor-news-monitor
Command: npx skills add https://github.com/Chia1104/agent-air --skill competitor-news-monitor-chia1104

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping up with competitor developments manually means scanning dozens of sources and wading through duplicate coverage, making it easy to miss pricing changes, product launches, or executive moves that actually matter. ## Core Features & Use Cases - Structured Watch Contracts: Freeze a watchlist of companies with domains, aliases, event categories, and a materiality threshold stored as a state file under ~/.hermes/competitor-watches/. - Scheduled Cron Ticks: Run recurring checks via a cronjob that collects incrementally from the last cutoff, deduplicates syndicated coverage into single events, and scores materiality. - Cited Digests: Deliver per-event reports with primary-source evidence, confidence levels, and follow-up items, staying silent when nothing material occurs. - Use Case: Ask the agent to monitor five competitors weekly; it builds source coverage from newsrooms, changelogs, regulatory filings, and trade press, then sends a digest only when a funding round, launch, or pricing change crosses your threshold. ## Quick Start Set up a weekly competitor watch for Acme Corp and Globex covering product launches, pricing changes, and executive moves, and deliver a cited digest to me every Monday morning.

Frequently Asked Questions about competitor-news-monitor

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

FAQPage Schema
How do I monitor competitor news automatically on a schedule?▼

Define a watchlist of companies with event categories and a materiality threshold, then create a cronjob that runs the tick procedure on a recurring schedule. Each run collects news since the last cutoff, deduplicates events, and delivers a digest only when material developments occur.

How to set up a competitor intelligence digest with cited sources?▼

Build source coverage per company from official newsrooms, changelogs, pricing pages, regulatory filings, and trade press, then record the watch contract in a state file. The digest reports each event with evidence links, what changed, why it matters, and a confidence level.

What sources does competitor news monitoring cover?▼

Coverage includes official newsrooms and blogs, changelogs, pricing and product pages, regulatory filings, investor relations, status and security pages, reputable trade and financial press, and job postings as weak supporting evidence. Optional feed tools like rss-feeds or blogwatcher can supplement collection.

How does the monitor avoid duplicate news stories?▼

It deduplicates by underlying event, collapsing syndicated stories, rewrites, URL variants, and revised filings into a single event. Independently sourced corroboration stays attached, so one announcement appears exactly once regardless of article count.

When should I not use a scheduled competitor news monitor?▼

Avoid it for one-off company research, where direct web search and extraction are faster, and for plain feed reading, which blogwatcher handles. It is designed for ongoing, threshold-based monitoring of a fixed company set, not ad-hoc lookups.

What happens when a news source fails during a monitoring run?▼

A source failure is recorded as unknown coverage, never treated as no news. The cutoff advances only for successfully covered sources, and failures are reported as coverage gaps in the state file so nothing is silently lost.