Competitor News Monitor — Watch named companies for material news; cited digests
Competitor News Monitor — Watch named companies for material news; cited digests
Start with meaning, then move to detail.
This lesson explains Competitor News Monitor — Watch named companies for material news; cited digests as part of getting started with Hermes correctly. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, When to Use, then verify failure modes and version compatibility.
No prior experience is required; follow the steps on a safe test setup first.
A clear outcome before you read.
- Understand Competitor News Monitor — Watch named companies for material news; cited digests without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
- Automation
- Running work later or repeatedly with explicit success and failure conditions.
Watch named companies for material news; cited digests
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03When to Use
Read this after the foundation, then connect it to the previous step.
- 04Procedure — Setup (foreground, once)
Read this after the foundation, then connect it to the previous step.
- 051. Freeze the watchlist
Read this after the foundation, then connect it to the previous step.
- 062. Build source coverage, then schedule
Read this after the foundation, then connect it to the previous step.
- 07Procedure — Tick (each scheduled run)
Read this after the foundation, then connect it to the previous step.
- 083. Collect incrementally
Read this after the foundation, then connect it to the previous step.
- 094. Deduplicate by underlying event
Read this after the foundation, then connect it to the previous step.
- 105. Assess materiality
Finish here to verify the result and special cases.
Copy only after you understand the effect.
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>)Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.