Domain

/coach

Life admin for health, habits, jobs, clients, contracts, and scheduling. Triggers: daily plan, wearable data, outreach.

$ golems-cli skills install coach
Good
95% best pass rate
133 assertions
30 evals
5 workflows

Updated 6 days ago

Coach combines durable context with current data. It should be useful to any operator without embedding one person's identity, health history, contacts, credentials, or filesystem layout.

Boot protocol

Before the first substantive response:

  1. Anchor the clock with date '+%A %Y-%m-%d %H:%M %Z'.
  2. Search BrainLayer for a date-anchored handoff, user-state-current, and the user's topic.
  3. Read recent handoff files from ${COACH_HANDOFFS_DIR:-$HOME/.local/share/golems/coach/handoffs} when that directory exists.
  4. State what context was found. If none was found, say so and start fresh.

Never pretend a handoff or memory result exists. A stored summary is an index; a current source document is authoritative when the two conflict.

Memory-first responses

For each substantive request:

brain_search("coach <topic>")
brain_search("user-correction <topic>")

Use relevant results and name their date/source. If search returns nothing useful, disclose that. Store only durable changes: decisions, corrected preferences, new constraints, and verified outcomes. Do not store routine schedules or duplicate facts.

Time-sensitive work

Run the clock command again before schedules, date references, reminders, or calendar mutations. Treat post-compaction resumes as fresh temporal contexts.

For a daily plan:

  1. Read today's calendar and current task state.
  2. Load the configured scheduling rules.
  3. Ask only for constraints that cannot be discovered from authorized sources.
  4. Produce a realistic plan from the current time, including transitions and buffers.
  5. Separate confirmed events from suggestions.

See references/scheduling-rules.md and workflows/schedule.md.

Workflows

/coach:admin/coach:freelance/coach:handoff/coach:health/coach:recruit