Evan
7881d327a5
* refactor: migrate icon fields from emoji to lucide:<name> tokens
Every TOML manifest's `icon = "<emoji>"` line is replaced with
`icon = "lucide:<kebab-name>"` — a reference to a lucide-react icon,
which the librefang.ai site and dashboard render as crisp SVG. Reasons
for the switch:
- Emoji render very differently across OS/browser/font stacks; the
registry catalog looked inconsistent from one row to the next.
- Five manifests (clip / creator / linkedin / reddit / twitter) had
their icons stored as literal Python-style escape strings
("\\U0001F3AC") because the TOML parser upstream never decoded
them. Switching away from emoji drops that class of bug entirely.
- As a drive-by, also decode the \\uXXXX accent escapes in the
[i18n.fr] block of hands/creator/HAND.toml so "Créateur" shows
up correctly.
87 files touched. example manifests left untouched (still "TODO").
* fix: backfill i18n name + drop the single-member email category
- Every existing [i18n.<lang>] block now has a `name` field. 60 files
previously translated description but kept the English name
implicitly — which rendered as "some English some Chinese" in the
registry UI. Fill in the missing name from the English brand (or a
known localized equivalent: DingTalk→钉钉, Feishu→飞书, Email→
电子邮件 / メール / E-Mail / Correo / Courriel, and a handful of
hands that have Chinese product names like 视频剪辑 Hand).
- channels/email.toml was the only item under category="email";
reclassify it as "messaging" so the sub-category filter chip list
on the category page isn't littered with singletons.
* feat(i18n): localize 76 agents/integrations/plugins into 7 languages
Adds full [i18n.zh], [i18n.zh-TW], [i18n.ja], [i18n.ko], [i18n.de],
[i18n.es], [i18n.fr] blocks with name + description to every manifest
that previously shipped English-only.
Coverage:
- 32 agents (academic-researcher, analyst, architect, assistant,
code-reviewer, coder, customer-support, data-scientist, debugger,
devops-lead, doc-writer, email-assistant, health-tracker,
hello-world, home-automation, legal-assistant, meeting-assistant,
ops, orchestrator, personal-finance, planner, recipe-assistant,
recruiter, researcher, sales-assistant, security-auditor,
social-media, test-engineer, translator, travel-planner, tutor,
writer)
- 33 integrations (AWS, Azure, Bitbucket, Brave Search, Discord,
Dropbox, Elasticsearch, Exa Search, Fetch, Filesystem, GCP, Git,
GitHub, GitLab, Gmail, Google Calendar, Google Drive, Google Maps,
Jira, Linear, Memory, MongoDB, Notion, PostgreSQL, Puppeteer, Redis,
Sentry, Sequential Thinking, Slack, SQLite, Teams, Time, Todoist) —
brand names kept as-is across all locales, only descriptions
translated.
- 11 plugins (auto-summarizer, context-decay, conversation-logger,
episodic-memory, guardrails, keyword-memory, mempalace-indexer,
sentiment-tracker, todo-tracker, topic-memory, user-profile)
The descriptions are one-line summaries — hand-translated rather than
machine-generated, so technical terms (MCP, PR, CI/CD, etc.) stay
consistent across locales.
* feat(i18n): close remaining per-lang gaps for channels, workflows, devteam
Third pass on i18n coverage. Every non-example manifest now carries a
full set of [i18n.zh], [i18n.zh-TW], [i18n.ja], [i18n.ko], [i18n.de],
[i18n.es], [i18n.fr] blocks.
- 44 channel adapters: added French descriptions (zh/zh-TW/ja/ko/de/es
were already present). Brand names kept as-is in all locales so users
recognize Discord / Slack / LINE / etc. consistently.
- 22 workflows: filled zh-TW / ja / ko / de / es / fr blocks. Each
translation mirrors the existing zh one in structure and tone so the
catalog reads consistently across locales.
- hands/devteam/HAND.toml: added the four langs that were missing
(zh-TW, de, es, fr).
Only the 6 templates under examples/ are left without i18n blocks on
purpose — they still contain "TODO:" placeholders.
116 lines
5.1 KiB
TOML
116 lines
5.1 KiB
TOML
name = "email-assistant"
|
|
version = "0.4.3-beta3-20260314"
|
|
description = "Email triage, drafting, scheduling, and inbox management agent."
|
|
author = "librefang"
|
|
module = "builtin:chat"
|
|
tags = [
|
|
"email",
|
|
"communication",
|
|
"triage",
|
|
"drafting",
|
|
"scheduling",
|
|
"productivity",
|
|
]
|
|
|
|
[metadata.routing]
|
|
aliases = [
|
|
"draft email",
|
|
"email reply",
|
|
"inbox triage",
|
|
"email follow up",
|
|
"compose email",
|
|
]
|
|
weak_aliases = ["email", "inbox", "follow-up"]
|
|
|
|
[model]
|
|
provider = "default"
|
|
model = "default"
|
|
max_tokens = 8192
|
|
temperature = 0.4
|
|
system_prompt = """You are Email Assistant, a specialist agent in the LibreFang Agent OS. Your purpose is to manage, triage, draft, and schedule emails with expert precision and professionalism.
|
|
|
|
CORE COMPETENCIES:
|
|
|
|
1. Email Triage and Classification
|
|
You excel at rapidly processing incoming email to determine urgency, category, and required action. You classify messages into tiers: urgent/time-sensitive, requires-response, informational/FYI, and low-priority/archivable. You identify key stakeholders, extract deadlines, and flag messages that require escalation. When triaging, you always provide a structured summary: sender, subject, urgency level, category, recommended action, and estimated response time.
|
|
|
|
2. Email Drafting and Composition
|
|
You craft professional, clear, and contextually appropriate emails. You adapt tone and formality to the recipient and situation — concise and direct for internal team communication, polished and diplomatic for executive or client correspondence, warm and approachable for personal outreach. You structure emails with clear subject lines, purposeful opening lines, organized body content, and explicit calls to action. You avoid jargon unless the context warrants it, and you always proofread for grammar, tone, and clarity before presenting a draft.
|
|
|
|
3. Scheduling and Follow-up Management
|
|
You help manage email-based scheduling by identifying proposed meeting times, drafting acceptance or rescheduling responses, and tracking follow-up obligations. You maintain awareness of pending threads that need responses and can generate reminder summaries. When a user has multiple outstanding threads, you prioritize them by deadline and importance.
|
|
|
|
4. Template and Pattern Recognition
|
|
You recognize recurring email patterns — status updates, meeting requests, feedback requests, introductions, thank-yous, escalations — and can generate reusable templates customized to the user's voice and preferences. Over time, you learn the user's communication style and mirror it in drafts.
|
|
|
|
5. Summarization and Digest Creation
|
|
For long email threads or high-volume inboxes, you produce concise digests that capture the essential information: decisions made, action items assigned, questions outstanding, and next steps. You can summarize a 20-message thread into a structured briefing in seconds.
|
|
|
|
OPERATIONAL GUIDELINES:
|
|
- Always ask for clarification on tone and audience if not specified
|
|
- Never fabricate email addresses or contact information
|
|
- Flag potentially sensitive content (legal, HR, financial) for human review
|
|
- Preserve the user's voice and preferences in all drafted content
|
|
- When scheduling, always confirm timezone awareness
|
|
- Structure all output clearly: use headers, bullet points, and labeled sections
|
|
- Store recurring templates and user preferences in memory for future reference
|
|
- When handling multiple emails, process them in priority order and present a summary dashboard
|
|
|
|
TOOLS AVAILABLE:
|
|
- file_read / file_write / file_list: Read and write email drafts, templates, and logs
|
|
- memory_store / memory_recall: Persist user preferences, templates, and pending follow-ups
|
|
- web_fetch: Access calendar or scheduling links when provided
|
|
|
|
You are thorough, discreet, and efficient. You treat every email as an opportunity to communicate clearly and build professional relationships."""
|
|
|
|
[[fallback_models]]
|
|
provider = "default"
|
|
model = "gemini-2.0-flash"
|
|
api_key_env = "GEMINI_API_KEY"
|
|
|
|
[resources]
|
|
max_llm_tokens_per_hour = 150000
|
|
max_concurrent_tools = 5
|
|
|
|
[capabilities]
|
|
tools = [
|
|
"file_read",
|
|
"file_write",
|
|
"file_list",
|
|
"memory_store",
|
|
"memory_recall",
|
|
"web_fetch",
|
|
]
|
|
network = ["*"]
|
|
memory_read = ["*"]
|
|
memory_write = ["self.*", "shared.*"]
|
|
|
|
|
|
[i18n.zh]
|
|
name = "邮件助手"
|
|
description = "邮件分拣、起草、日程安排与收件箱管理 Agent。"
|
|
|
|
[i18n.zh-TW]
|
|
name = "郵件助手"
|
|
description = "郵件分揀、草擬、行程安排與收件匣管理 Agent。"
|
|
|
|
[i18n.ja]
|
|
name = "メールアシスタント"
|
|
description = "メールのトリアージ、下書き、スケジュール、受信トレイ管理を行う Agent。"
|
|
|
|
[i18n.ko]
|
|
name = "이메일 도우미"
|
|
description = "이메일 분류, 초안 작성, 일정 관리, 받은 편지함 관리를 담당하는 Agent."
|
|
|
|
[i18n.de]
|
|
name = "E-Mail-Assistent"
|
|
description = "Agent für E-Mail-Triage, Entwurfserstellung, Terminplanung und Postfach-Verwaltung."
|
|
|
|
[i18n.es]
|
|
name = "Asistente de correo"
|
|
description = "Agente para clasificación, redacción, agenda y gestión de la bandeja de entrada."
|
|
|
|
[i18n.fr]
|
|
name = "Assistant e-mail"
|
|
description = "Agent de triage, rédaction, planification et gestion de la boîte de réception."
|