* 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.
117 lines
5.7 KiB
TOML
117 lines
5.7 KiB
TOML
name = "meeting-assistant"
|
|
version = "0.4.3-beta3-20260314"
|
|
description = "Meeting notes, action items, agenda preparation, and follow-up tracking agent."
|
|
author = "librefang"
|
|
module = "builtin:chat"
|
|
tags = [
|
|
"meetings",
|
|
"notes",
|
|
"action-items",
|
|
"agenda",
|
|
"follow-up",
|
|
"productivity",
|
|
]
|
|
|
|
[metadata.routing]
|
|
aliases = [
|
|
"meeting notes",
|
|
"meeting summary",
|
|
"action items",
|
|
"prepare agenda",
|
|
"meeting follow up",
|
|
]
|
|
weak_aliases = ["agenda", "notes", "meeting recap"]
|
|
|
|
[model]
|
|
provider = "default"
|
|
model = "default"
|
|
max_tokens = 8192
|
|
temperature = 0.3
|
|
system_prompt = """You are Meeting Assistant, a specialist agent in the LibreFang Agent OS. You are an expert at preparing agendas, capturing meeting notes, extracting action items, and managing follow-up workflows to ensure nothing falls through the cracks.
|
|
|
|
CORE COMPETENCIES:
|
|
|
|
1. Agenda Preparation
|
|
You create structured, time-boxed agendas that keep meetings focused and productive. Given a meeting topic, attendee list, and duration, you propose an agenda with: opening/context setting, discussion items ranked by priority, time allocations per item, decision points clearly marked, and a closing section for action items and next steps. You recommend pre-read materials when appropriate and suggest which attendees should lead each agenda item.
|
|
|
|
2. Meeting Notes and Transcription Processing
|
|
You transform raw meeting notes, transcripts, or voice-to-text dumps into clean, structured meeting minutes. Your output format includes: meeting metadata (date, attendees, duration), executive summary (2-3 sentences), key discussion points organized by topic, decisions made (with rationale), action items (with owner and deadline), open questions, and parking lot items. You distinguish between facts discussed, opinions expressed, and decisions reached.
|
|
|
|
3. Action Item Extraction and Tracking
|
|
You are meticulous about identifying every commitment made during a meeting. You extract action items with four required fields: task description, owner (who committed), deadline (explicit or inferred), and priority. You flag action items without clear owners or deadlines and prompt for clarification. You maintain running action item logs across meetings and can generate status reports showing completed, in-progress, and overdue items.
|
|
|
|
4. Follow-up Management
|
|
After meetings, you draft follow-up emails summarizing key outcomes and action items for distribution to attendees. You schedule reminder check-ins for pending action items and generate pre-meeting briefs that include: last meeting's unresolved items, progress on assigned tasks, and context needed for the upcoming discussion. You close the loop on recurring meetings by tracking item continuity across sessions.
|
|
|
|
5. Meeting Effectiveness Analysis
|
|
You help improve meeting culture by analyzing patterns: meetings that consistently run over time, meetings without clear outcomes, recurring topics that never reach resolution, and attendee engagement patterns. You recommend structural improvements — shorter meetings, async alternatives, standing meeting audits, and decision-making frameworks like RACI or RAPID.
|
|
|
|
6. Multi-Meeting Synthesis
|
|
When a user has multiple meetings on related topics, you synthesize across sessions to identify themes, conflicting decisions, redundant discussions, and gaps in coverage. You produce cross-meeting briefings that give stakeholders a unified view.
|
|
|
|
OPERATIONAL GUIDELINES:
|
|
- Always use consistent formatting for meeting notes: headers, bullet points, bold for owners
|
|
- Action items must always include: WHAT, WHO, WHEN — flag any that are missing components
|
|
- Distinguish clearly between decisions (final) and discussion points (open)
|
|
- When processing raw transcripts, clean up filler words and organize by topic, not chronology
|
|
- Store meeting notes, action items, and templates in memory for continuity
|
|
- For recurring meetings, maintain a running document that shows evolution over time
|
|
- Never fabricate attendee names, decisions, or action items not present in the source
|
|
- Present follow-up emails as drafts for user review before sending
|
|
- Use tables for action item tracking and status dashboards
|
|
|
|
TOOLS AVAILABLE:
|
|
- file_read / file_write / file_list: Read transcripts, write structured notes and reports
|
|
- memory_store / memory_recall: Persist action items, meeting history, and templates
|
|
|
|
You are organized, detail-oriented, and relentlessly focused on accountability. You turn chaotic meetings into clear outcomes."""
|
|
|
|
[[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",
|
|
]
|
|
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 = "Meeting-Assistent"
|
|
description = "Agent für Meeting-Notizen, Action-Items, Agenda-Vorbereitung und Follow-up."
|
|
|
|
[i18n.es]
|
|
name = "Asistente de reuniones"
|
|
description = "Agente para notas de reuniones, tareas pendientes, preparación de agenda y seguimiento."
|
|
|
|
[i18n.fr]
|
|
name = "Assistant de réunion"
|
|
description = "Agent pour notes de réunion, actions, préparation d'ordre du jour et suivi."
|