Subagents

​

Overview

​

ollim-bot-guide

• Searches the documentation site using the approach that fits the question — targeted lookup for specific fields and settings, full-page fetch for broader topics
• Includes the actual docs text in its response — never rewrites or summarizes
• Cross-references your config files (routines, reminders, webhooks) against the docs when diagnosing setup issues
• Reports explicitly when docs don’t cover a topic, listing what it searched

• Setup and configuration: “How do I set up…”, “What’s the YAML format for…”
• Usage questions: “How does X work?”
• Config validation: “Is my routine configured correctly?”
• NOT runtime debugging (“what happened last night?”, “why did the bot miss my ping?”) — those require session transcripts the ollim-bot-guide doesn’t have access to

​

gmail-reader

• Emails from real people expecting a response
• Security alerts (password changes, login attempts, account changes)
• Financial items (bills due, payment failures)
• Time-sensitive items (deadlines, meeting changes, approvals)
• Packages requiring action (pickup, signature)

• Newsletters, marketing, promos
• Delivery/shipping confirmations
• Social media notifications
• Service agreement updates, routine notices

Action items:
- [sender] [date time] subject -- what needs to be done

Skipped: N emails (all noise/automated)

​

history-reviewer

• Tasks or TODOs mentioned but never tracked
• Work started but not finished (“I’ll do this after lunch” with no follow-up)
• Commitments to other people (“I’ll send that to X”)
• Questions asked that went unanswered
• Errors or failures deferred for later
• Ideas or plans discussed but not captured

• Completed work with successful commits
• Casual conversation with no action items
• Finished, resolved sessions
• Bot development/debugging sessions (unless they mention deployments or broken production state)

Follow-ups from recent sessions:
- [session ID] <what needs attention> -- <suggested action>

​

responsiveness-reviewer

• Foreground firings are prompts inside the main session. Engagement is measured by whether a user message follows before the next firing.
• Background firings run in their own forked sessions. Engagement is measured by checking for user activity in the main session shortly after the firing.
• One-shot reminders are deleted after firing, so they only appear in session history, not in ollim-bot reminder list.

Responsiveness (past 7 days):

| Routine/Reminder | Firings | Engaged | Ignored | Notes |
|------------------|---------|---------|---------|-------|
| morning-tasks    | 7       | 5       | 2       | ignored both Sat firings |
| email-digest     | 7       | 7       | 0       | always engaged |

Patterns:
- <observation tied to data>

Suggestions:
- <actionable recommendation with rationale>

​

user-proxy

1. Searches for preference and identity files in your data directory, including routines and reminders
2. Reads the most relevant files (max 3-4) related to the question
3. Searches conversation history via claude-history for past decisions, corrections, and stated preferences
4. Returns a structured answer with calibrated confidence

• Preference files — maintained by automated routines that infer from conversation. Treated as educated guesses, not certainties.
• Conversation transcripts — records of what the user actually said and did. Treated as reliable evidence.

Answer: <one sentence — what the user would most likely do or prefer>

Reasoning: <evidence — cites specific files or search results>

Confidence: HIGH | MEDIUM | LOW — <why this level>

​

Subagent binding for jobs

---
id: "e1f2a3b4"
cron: "0 9 * * 1"
description: "Weekly email digest"
background: true
subagent: "gmail-reader"
---
Triage the inbox and surface anything that needs attention this week.

​

Developer reference

---
name: ollim-bot-guide
description: >-
  Delegate to this subagent when the answer depends on ollim-bot
  documentation — including when YOU need docs knowledge (building a
  routine, checking webhook format, verifying feature behavior). Covers:
  setup and configuration (YAML format, fields, syntax), feature behavior
  (routines, reminders, webhooks, forks, permissions, ping budget), and
  config validation (is my routine/reminder/webhook correct?). Also use
  for 'how does X work' questions about ollim-bot architecture.
model: haiku
tools:
  - mcp__docs__*
  - WebFetch
  - Read(**.md)
  - Glob(**.md)
  - Bash(ollim-bot help)
  - Bash(ollim-bot routine list)
  - Bash(ollim-bot reminder list)
---
You are {USER_NAME}'s ollim-bot guide. Your goal: answer questions about
ollim-bot setup, configuration, and usage by surfacing relevant documentation
verbatim...

from ollim_bot.subagents import install_agents, load_agent_tool_sets

install_agents()                    # copy bundled specs to .claude/agents/
tool_sets = load_agent_tool_sets()  # dict[str, list[str]]

​

Next steps