* 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.
103 lines
3.1 KiB
TOML
103 lines
3.1 KiB
TOML
id = "meeting-summary"
|
|
name = "Meeting Summary & Action Items"
|
|
description = "Transform raw meeting notes or transcript into a structured summary, decisions log, and follow-up email."
|
|
category = "productivity"
|
|
tags = ["meeting", "notes", "productivity", "collaboration"]
|
|
|
|
[i18n.zh]
|
|
name = "会议纪要与行动项"
|
|
description = "将原始会议记录或转录文本整理为结构化摘要、决策日志和跟进邮件。"
|
|
|
|
[[parameters]]
|
|
name = "notes"
|
|
description = "Raw meeting notes or transcript"
|
|
param_type = "string"
|
|
required = true
|
|
|
|
[[parameters]]
|
|
name = "meeting_context"
|
|
description = "Meeting type, attendees, and goal (optional)"
|
|
param_type = "string"
|
|
required = false
|
|
default = ""
|
|
|
|
[[steps]]
|
|
name = "structured_summary"
|
|
prompt_template = """
|
|
You are an executive assistant. From the raw meeting notes below, extract:
|
|
|
|
**Key Discussion Points** — 3-7 bullet points on what was discussed
|
|
**Decisions Made** — each decision with rationale and who decided
|
|
**Open Questions** — unresolved items that need follow-up
|
|
**Blockers & Risks** — anything flagged as blocking progress
|
|
|
|
Context: {{meeting_context}}
|
|
|
|
Notes:
|
|
{{notes}}
|
|
"""
|
|
|
|
[[steps]]
|
|
name = "action_items"
|
|
prompt_template = """
|
|
Extract all action items from the meeting. For each:
|
|
- Action: specific, measurable task
|
|
- Owner: person responsible (use name from notes)
|
|
- Due date: explicit date or relative (e.g. 'by next Friday')
|
|
- Priority: High / Medium / Low
|
|
- Dependencies: what must happen first
|
|
|
|
Format as a table.
|
|
|
|
Summary:
|
|
{{structured_summary}}
|
|
|
|
Notes:
|
|
{{notes}}
|
|
"""
|
|
depends_on = ["structured_summary"]
|
|
|
|
[[steps]]
|
|
name = "followup_email"
|
|
prompt_template = """
|
|
Write a professional follow-up email to send to all attendees. Include:
|
|
- Subject line
|
|
- Brief recap (2-3 sentences)
|
|
- Decisions section
|
|
- Action items table (owner, task, due date)
|
|
- Next steps / next meeting placeholder
|
|
|
|
Keep tone professional but concise. Use the attendees' first names.
|
|
|
|
Summary:
|
|
{{structured_summary}}
|
|
|
|
Action items:
|
|
{{action_items}}
|
|
"""
|
|
depends_on = ["structured_summary", "action_items"]
|
|
|
|
[i18n.zh-TW]
|
|
name = "會議摘要與行動項目"
|
|
description = "將原始會議記錄或逐字稿整理為結構化摘要、決策日誌與後續追蹤郵件。"
|
|
|
|
[i18n.ja]
|
|
name = "会議サマリとアクションアイテム"
|
|
description = "議事録や文字起こしを構造化サマリ、決定事項リスト、フォローアップメールに変換。"
|
|
|
|
[i18n.ko]
|
|
name = "회의 요약 및 액션 아이템"
|
|
description = "원본 회의 메모나 녹취를 구조화된 요약, 결정 로그, 팔로업 이메일로 변환."
|
|
|
|
[i18n.de]
|
|
name = "Meeting-Zusammenfassung & Action Items"
|
|
description = "Rohe Meeting-Notizen oder Transkripte in strukturierte Zusammenfassung, Entscheidungsprotokoll und Follow-up-Mail verwandeln."
|
|
|
|
[i18n.es]
|
|
name = "Resumen de reuniones y acciones"
|
|
description = "Transforma notas o transcripciones en un resumen estructurado, registro de decisiones y correo de seguimiento."
|
|
|
|
[i18n.fr]
|
|
name = "Compte-rendu et actions"
|
|
description = "Transformer des notes ou transcriptions brutes en compte-rendu structuré, journal de décisions et e-mail de suivi."
|