personal memory agent
routines: document suggest-respond, suggest-state + reframe description
Two user-facing commands existed in think/tools/routines.py (lines 395-442)
but were absent from the skill: suggest-respond (record accept/decline on
a routine suggestion) and suggest-state (print raw suggestion state).
Add both to the command table and a short "Responding to suggestions"
section. Also add a Gotchas block (IANA timezone requirement, suggestion
idempotency). Reframe description from infrastructure framing
("create, manage, and inspect") to task framing ("set up recurring
routines — daily briefings, weekly reviews..."). Expand TRIGGER with
literal command names.
Part of skills audit req_loq3e2lk pass 1+2.
+31
-6
+31
-6
talent/routines/SKILL.md
+31
-6
talent/routines/SKILL.md
···
1
1
---
2
2
name: routines
3
3
description: >
4
-
Create, manage, and inspect scheduled routines. List available templates,
5
-
create routines from templates or custom instructions, edit timing and scope,
6
-
pause/resume, delete, run immediately, and read output history.
7
-
TRIGGER: routine, routines, schedule, recurring, automate, morning briefing setup,
8
-
weekly review setup, domain watch, meeting prep, commitment audit.
4
+
Set up recurring routines — daily briefings, weekly reviews, domain
5
+
watches, commitment audits, meeting prep — or custom automations.
6
+
Create from templates with sensible defaults or from custom
7
+
instructions, adjust timing and scope, pause/resume, delete, run
8
+
immediately to test, respond to routine suggestions, and read past
9
+
output.
10
+
TRIGGER: routine, routines, schedule, recurring, automate, daily brief,
11
+
morning briefing, weekly review, domain watch, meeting prep,
12
+
commitment audit, routine output, pause routine, run immediately,
13
+
routine suggestions, sol call routines create, sol call routines list,
14
+
sol call routines edit, sol call routines run, sol call routines output,
15
+
sol call routines suggest-respond, sol call routines suggest-state.
9
16
---
10
17
11
18
# Routines CLI Skill
12
19
13
-
Use these commands to manage routines. Never expose cron syntax, UUIDs, or CLI internals to the owner.
20
+
Manage recurring routines. Invoke via Bash: `sol call routines <command> [args...]`. Never expose cron syntax, UUIDs, or CLI internals to the owner.
14
21
15
22
## Template guidance
16
23
···
44
51
| Run immediately | `sol call routines run {name}` |
45
52
| Read output | `sol call routines output {name}` (add `--date YYYY-MM-DD` for a specific day) |
46
53
| Toggle suggestions | `sol call routines suggestions --enable` or `sol call routines suggestions --disable` |
54
+
| Record response to a suggestion | `sol call routines suggest-respond {template} --accepted` or `--declined` |
55
+
| Show suggestion state | `sol call routines suggest-state` |
47
56
48
57
Use the routine's name for identification, never UUIDs.
58
+
59
+
## Responding to suggestions
60
+
61
+
When the system surfaces a routine suggestion and the owner accepts or declines it, record their response so the suggestion engine doesn't re-surface the same template prematurely:
62
+
63
+
```bash
64
+
sol call routines suggest-respond morning-briefing --accepted
65
+
sol call routines suggest-respond weekly-review --declined
66
+
```
67
+
68
+
Exactly one of `--accepted` or `--declined` is required. `suggest-state` prints the full JSON state for all templates if you need to inspect what the engine already knows.
69
+
70
+
## Gotchas
71
+
72
+
- **Timezone must be an IANA name.** `--timezone America/Denver` works; `--timezone MDT` does not. The CLI rejects the latter with a terse error.
73
+
- **Suggestion responses are idempotent within a day.** Calling `suggest-respond` twice in the same day overwrites the previous response. Don't loop on it.