Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nousresearch/competitor-news-monitor
Watch named companies for material news; cited digests.
Passed 12 of 20 test cases with the skill, and 8 of 20 without it.
and 6 more in the full report
7 fixed8 passed either way8 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are configuring a new competitor watch slugged `fintech-rivals` for PayFlow. Where precisely must the watch contract state file be stored on disk, and what extension must it use?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies writing the contract file to ~/.hermes/competitor-watches/fintech-rivals.json. | Missed | Passed |
The instructions your model reads when the skill loads.
Track a declared company set and report only material, new developments with primary-source evidence. This is not a generic page-diff watcher: it applies company-news categories, source hierarchy, event deduplication, and business significance. Setup runs once in the foreground; the recurring check runs as a cronjob tick (the competitor-watch automation blueprint scaffolds this).
Don't use for: one-off company research (use web_search/web_extract directly) or plain feed reading (blogwatcher).
Record canonical company names, domains, products, aliases, geography/language, event categories, cadence, audience, and materiality threshold. Done when a candidate article can be accepted or rejected consistently.
For each company include, where available:
Use blogwatcher for feeds and web_search/web_extract for pages. Write the watch contract (watchlist, categories, materiality threshold, last cutoff) to a state file under ~/.hermes/competitor-watches/<watch-slug>.json, then create the job:
cronjob(action="create",
schedule="every monday 9am",
prompt="Load the competitor-news-monitor skill and run the tick for the watch contract at ~/.hermes/competitor-watches/<watch-slug>.json.",
deliver=<user's destination>)
test cases passed, vs 8 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.