Automations
GAIA can act without being asked again, through gaia automation run with
run_shell_command. Listing never asks; every change shows the user the exact
command and waits for them to approve it. Results reach the user through
Discord today, so if add says nothing delivers it yet, tell them to connect
Discord under Settings → Messaging in the GAIA app.
Pick the kind by when GAIA should speak
| The user says |
Kind |
How |
| "remind me in 10 minutes / at 5pm / tomorrow 9am to …" |
reminder, once |
--at with --say (exact text, no AI) or --prompt (something to look up then) |
| "summarize … every morning at 8 / every 3 hours / every weekday" |
summary, always speaks |
--every with --prompt; --at 8am sets the time of day, --days mon-fri the days |
| "alert me if CI breaks", "tell me when PR 12 is approved" — a GitHub fact |
trigger: a cheap check, speaks only when its output changes |
--every with --check and --prompt |
| "let me know when a good weather window opens", "if anything urgent lands in my inbox" — needs judgment |
alert: GAIA checks and stays silent unless something needs the user |
--every with --alert and --prompt |
| "check in on things every 30 minutes", "keep an eye on my day" |
heartbeat: an alert named Heartbeat whose prompt is their checklist |
--every 30m --alert --quiet 22:00-07:00 |
| "tell me right away when someone opens a PR or issue or comments on owner/repo" |
watch: a plain GitHub poller, instant and never repeating |
gaia discord watch --repo owner/repo --mine <their accounts> |
Never answer "alert me if …" with a summary: a summary speaks every time, even
when nothing happened. Prefer a trigger when one GitHub read shows the state;
use an alert when it takes reading the web, mail or files and judging.
Commands
| Do this |
Command |
| List everything |
gaia automation list |
| One-time reminder |
gaia automation add --name "Stretch" --at 10m --say "Time to stretch" |
| Summary |
gaia automation add --name "Morning inbox" --every 1d --at 8am --prompt "..." |
| Trigger |
gaia automation add --name "main CI" --every 10m --check "gaia automation ci-status --repo amd/gaia --branch main" --prompt "..." |
| Alert |
gaia automation add --name "Rainier window" --every 6h --alert --prompt "..." |
| Change one |
gaia automation edit "main CI" --every 30m (also --prompt, --say, --at, --check, --quiet, --days, --rename) |
| Pause / resume / run now |
gaia automation pause "Heartbeat" (or resume, run) |
| Remove one / all |
gaia automation remove "Stretch" / gaia automation remove --all |
| Instant GitHub activity alerts |
gaia discord watch --repo amd/gaia --mine kovtcharov,kovtcharov-amd (again with a new --mine to change the accounts) |
| Stop those |
gaia discord unwatch --repo amd/gaia |
Run each as its own run_shell_command call, with double quotes only. Refer to
an automation by its name (or the id from list). list shows GitHub watches
too, each with the command that changes or removes it. A waiting: row is not
an automation: it is a message that already ran and reaches Discord when the
bridge is back. Removing its automation drops it; to drop only the message,
gaia automation remove "waiting:<id>".
For a watch, pin down which GitHub accounts are the user's own: their activity
is not news to them. Use the ones they named; if none, ask once ("Which GitHub
accounts are yours?"). Never guess.
Writing them well
- Name it in a few words the user would use: "main CI", "Rainier window",
"Heartbeat". That is how they will ask to change it.
- Write the prompt so it stands alone. It runs later with no memory of this
chat: name the repository, mailbox, place or accounts; what counts as worth
telling; and to link everything it cites.
- Alerts: say exactly what qualifies ("both weekend days: precipitation
under 1 mm, summit wind under 25 mph"), and how far ahead to look. GAIA is
told to reply with nothing when nothing qualifies, and not to repeat news it
already sent.
- Triggers: the check is one GitHub read that prints only the state that
matters —
gaia automation ci-status --repo OWNER/REPO --branch main, or a
gh read naming the repo, like gh pr view 12 --repo OWNER/REPO --json reviewDecision --jq .reviewDecision. Write flags and values apart (-L 5).
Anything that could change something, pipes and --paginate are refused.
Adding one runs the check once and prints what it shows: tell the user that.
- Intervals: what the user said; else
10m for CI and reviews, 6h for
weather and slow news, 30m for a heartbeat. The shortest is 5m. Quiet
hours (--quiet 22:00-07:00) hold a run until they end; use them for
heartbeats and anything that would wake someone. --days mon-fri (or
weekends, mon,wed,fri) skips other days — never ask the prompt to "reply
with nothing on weekends".
- Before adding, list what exists. If something already covers part of the
request, say so and offer to change it instead of adding a duplicate.
After a change
- Say what will happen, in plain words, and when it next runs: "Done — I'll
check every 6 hours and message you only when a weekend with good weather
shows up." Show the exact command or prompt only if they ask.
- To change or stop something, list first, then edit or remove by name.
"Stop the updates" with more than one candidate means asking which.
- When asked what is set up, list and answer in a short bullet list: name,
kind, how often, next run, paused or not.
1---2name: automations3description: Reminders, alerts, triggers, summaries and the heartbeat — work GAIA does on its own and reports later. "Remind me at 5pm", "alert me if main breaks", "tell me when a good weather window opens", "summarize my inbox every morning", "check in every 30 minutes", "what are you watching?", "pause that", "stop those updates". Use whenever the user wants something done later, repeatedly, or only when something changes, or wants to see or change what is set up.4license: MIT5version: 2.0.06metadata:7 gaia:8 security_tier: community9 permissions:10 - shell:execute:gaia11 tools_required:12 - run_shell_command13 provenance:14 source: https://skillmd.com/skills/amd/automations15 upstream: starter-pack16---1718# Automations1920GAIA can act without being asked again, through `gaia automation` run with21`run_shell_command`. Listing never asks; every change shows the user the exact22command and waits for them to approve it. Results reach the user through23Discord today, so if `add` says nothing delivers it yet, tell them to connect24Discord under Settings → Messaging in the GAIA app.2526## Pick the kind by when GAIA should speak2728| The user says | Kind | How |29|---|---|---|30| "remind me in 10 minutes / at 5pm / tomorrow 9am to …" | **reminder**, once | `--at` with `--say` (exact text, no AI) or `--prompt` (something to look up then) |31| "summarize … every morning at 8 / every 3 hours / every weekday" | **summary**, always speaks | `--every` with `--prompt`; `--at 8am` sets the time of day, `--days mon-fri` the days |32| "alert me if CI breaks", "tell me when PR 12 is approved" — a GitHub fact | **trigger**: a cheap check, speaks only when its output changes | `--every` with `--check` and `--prompt` |33| "let me know when a good weather window opens", "if anything urgent lands in my inbox" — needs judgment | **alert**: GAIA checks and stays silent unless something needs the user | `--every` with `--alert` and `--prompt` |34| "check in on things every 30 minutes", "keep an eye on my day" | **heartbeat**: an alert named `Heartbeat` whose prompt is their checklist | `--every 30m --alert --quiet 22:00-07:00` |35| "tell me right away when someone opens a PR or issue or comments on owner/repo" | **watch**: a plain GitHub poller, instant and never repeating | `gaia discord watch --repo owner/repo --mine <their accounts>` |3637Never answer "alert me if …" with a summary: a summary speaks every time, even38when nothing happened. Prefer a trigger when one GitHub read shows the state;39use an alert when it takes reading the web, mail or files and judging.4041## Commands4243| Do this | Command |44|---|---|45| List everything | `gaia automation list` |46| One-time reminder | `gaia automation add --name "Stretch" --at 10m --say "Time to stretch"` |47| Summary | `gaia automation add --name "Morning inbox" --every 1d --at 8am --prompt "..."` |48| Trigger | `gaia automation add --name "main CI" --every 10m --check "gaia automation ci-status --repo amd/gaia --branch main" --prompt "..."` |49| Alert | `gaia automation add --name "Rainier window" --every 6h --alert --prompt "..."` |50| Change one | `gaia automation edit "main CI" --every 30m` (also `--prompt`, `--say`, `--at`, `--check`, `--quiet`, `--days`, `--rename`) |51| Pause / resume / run now | `gaia automation pause "Heartbeat"` (or `resume`, `run`) |52| Remove one / all | `gaia automation remove "Stretch"` / `gaia automation remove --all` |53| Instant GitHub activity alerts | `gaia discord watch --repo amd/gaia --mine kovtcharov,kovtcharov-amd` (again with a new `--mine` to change the accounts) |54| Stop those | `gaia discord unwatch --repo amd/gaia` |5556Run each as its own `run_shell_command` call, with double quotes only. Refer to57an automation by its name (or the id from `list`). `list` shows GitHub watches58too, each with the command that changes or removes it. A `waiting:` row is not59an automation: it is a message that already ran and reaches Discord when the60bridge is back. Removing its automation drops it; to drop only the message,61`gaia automation remove "waiting:<id>"`.6263For a watch, pin down which GitHub accounts are the user's own: their activity64is not news to them. Use the ones they named; if none, ask once ("Which GitHub65accounts are yours?"). Never guess.6667## Writing them well6869- **Name it in a few words** the user would use: "main CI", "Rainier window",70 "Heartbeat". That is how they will ask to change it.71- **Write the prompt so it stands alone.** It runs later with no memory of this72 chat: name the repository, mailbox, place or accounts; what counts as worth73 telling; and to link everything it cites.74- **Alerts:** say exactly what qualifies ("both weekend days: precipitation75 under 1 mm, summit wind under 25 mph"), and how far ahead to look. GAIA is76 told to reply with nothing when nothing qualifies, and not to repeat news it77 already sent.78- **Triggers:** the check is one GitHub read that prints only the state that79 matters — `gaia automation ci-status --repo OWNER/REPO --branch main`, or a80 gh read naming the repo, like `gh pr view 12 --repo OWNER/REPO --json81 reviewDecision --jq .reviewDecision`. Write flags and values apart (`-L 5`).82 Anything that could change something, pipes and `--paginate` are refused.83 Adding one runs the check once and prints what it shows: tell the user that.84- **Intervals:** what the user said; else `10m` for CI and reviews, `6h` for85 weather and slow news, `30m` for a heartbeat. The shortest is `5m`. Quiet86 hours (`--quiet 22:00-07:00`) hold a run until they end; use them for87 heartbeats and anything that would wake someone. `--days mon-fri` (or88 `weekends`, `mon,wed,fri`) skips other days — never ask the prompt to "reply89 with nothing on weekends".90- **Before adding, list what exists.** If something already covers part of the91 request, say so and offer to change it instead of adding a duplicate.9293## After a change9495- **Say what will happen, in plain words**, and when it next runs: "Done — I'll96 check every 6 hours and message you only when a weekend with good weather97 shows up." Show the exact command or prompt only if they ask.98- **To change or stop something,** list first, then edit or remove by name.99 "Stop the updates" with more than one candidate means asking which.100- **When asked what is set up,** list and answer in a short bullet list: name,101 kind, how often, next run, paused or not.