Evan
28ea31b073
These 11 templates are the general-purpose ones that don't depend on any particular model at the primary level (`[model] provider = "default"`). They also ship a secondary `[[fallback_models]]` block pointing at `gemini-2.0-flash` with `api_key_env = "GEMINI_API_KEY"`. That default hurts everyone who doesn't happen to have `$GEMINI_API_KEY` set — every agent boot logs `WARN Fallback driver 'gemini' failed to init: Missing API key`, once per turn per agent. The templates that actually intend to use Gemini as their primary model (analyst, coder, researcher, code-reviewer, debugger, legal-assistant, data-scientist, academic-researcher, test-engineer) are left untouched — those declare Gemini in `[model]`, which is an intentional design choice, not a hidden fallback. Users who want a Gemini fallback chain for generic agents can add `[[fallback_models]]` themselves in `~/.librefang/workspaces/agents/...` once they've set `$GEMINI_API_KEY`. Removed from: assistant, customer-support, devops-lead, doc-writer, email-assistant, meeting-assistant, planner, recruiter, sales-assistant, social-media, writer
Email Assistant
Email triage, drafting, scheduling, and inbox management agent.
Configuration
| Field | Value |
|---|---|
| Module | builtin:chat |
| Model | default |
| Provider | default |
System prompt instructs email classification by urgency, professional drafting with tone adaptation, scheduling, template management, and thread summarization.
Skills
file_read,file_write,file_list,memory_store,memory_recall,web_fetch
Usage
librefang agent run email-assistant