Automation
Competitor digest
A recurring roundup of what named competitors changed.
What it asks you for
- Runsrequired
- When it reports.
- Competitorsrequired
- One per line, with their site.
What it tells the AI to do
Set up a competitor digest.
- Runs: {{ schedule.human }} ({{ schedule.timezone }}), cron `{{ schedule.cron }}`
Watching:
{{ competitors }}
Create it with `automation create`, passing the cron and timezone verbatim.
Each run: check pricing pages, changelogs, and launch announcements, then diff
against what the last run recorded in memory. Report only the deltas, with the
before and after side by side and a link to the page.
Say what a change implies for us in one line, and mark that line as your read
rather than as fact. A digest that only lists diffs makes the reader do the
analysis they hired the digest to do; a digest that hides the boundary between
observation and opinion is worse.
Nothing changed means send nothing.- automation
- competitors
- digest
- market
More automation skills
- Do this on a scheduleSet up a recurring automation that runs without you.
- Daily briefingA short scheduled digest of only what changed and matters.
- Watch and alert meCheck a condition on a schedule and speak up only when it fires.
- Daily task standupA morning digest of what is due, late, and waiting on you.
- Tidy DriveFile loose documents on a schedule, and report what moved.
- Scan new papersA recurring sweep for new research in your field.