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.
102 lines
3.5 KiB
TOML
102 lines
3.5 KiB
TOML
id = "weekly-report"
|
|
name = "Weekly Report Generator"
|
|
description = "Turn raw work notes into a polished weekly report with highlights, metrics, blockers, and next week's priorities."
|
|
category = "productivity"
|
|
tags = ["report", "weekly", "productivity", "management"]
|
|
|
|
[i18n.zh]
|
|
name = "周报生成器"
|
|
description = "将零散工作笔记整理为规范周报，包含亮点、指标、阻塞项和下周计划。"
|
|
|
|
[[parameters]]
|
|
name = "work_notes"
|
|
description = "Raw work notes, bullet points, or activity log for the week"
|
|
param_type = "string"
|
|
required = true
|
|
|
|
[[parameters]]
|
|
name = "team_or_role"
|
|
description = "Your team name or role (used to frame context appropriately)"
|
|
param_type = "string"
|
|
required = false
|
|
default = ""
|
|
|
|
[[parameters]]
|
|
name = "audience"
|
|
description = "Who will read this report (manager, team, executive)"
|
|
param_type = "string"
|
|
required = false
|
|
default = "manager"
|
|
|
|
[[steps]]
|
|
name = "extract"
|
|
prompt_template = """
|
|
You are an executive assistant. Parse the following raw work notes and extract every item into structured categories:
|
|
|
|
**Completed** — fully done tasks (include measurable outcomes if mentioned)
|
|
**In Progress** — work started but not finished (include % complete or next milestone if available)
|
|
**Blockers** — anything preventing progress, and who or what is blocking
|
|
**Decisions Made** — choices or agreements reached this week
|
|
**Metrics** — any numbers mentioned (velocity, usage, revenue, bugs closed, etc.)
|
|
**Upcoming** — planned work mentioned for next week
|
|
|
|
Do not summarise or rephrase — extract faithfully.
|
|
|
|
Team/Role: {{team_or_role}}
|
|
|
|
Raw notes:
|
|
{{work_notes}}
|
|
"""
|
|
|
|
[[steps]]
|
|
name = "report_writer"
|
|
prompt_template = """
|
|
Write a polished weekly report for a {{audience}} audience. Tone should be professional and concise — no padding.
|
|
|
|
## Highlights
|
|
Top 3 achievements this week, each in one sentence with measurable impact where available.
|
|
|
|
## Progress
|
|
Grouped by project or workstream. For each: what was done, current status, and any dependency.
|
|
|
|
## Metrics
|
|
Key numbers from the week. If none were provided, omit this section.
|
|
|
|
## Blockers & Risks
|
|
Each blocker: description, impact, owner, and requested action.
|
|
|
|
## Next Week
|
|
Top 3-5 priorities with owner and expected outcome.
|
|
|
|
## Notes
|
|
Decisions made, process changes, or anything the audience should be aware of.
|
|
|
|
Extracted data:
|
|
{{extract}}
|
|
"""
|
|
depends_on = ["extract"]
|
|
|
|
[i18n.zh-TW]
|
|
name = "週報產生器"
|
|
description = "將零散的工作筆記整理為規範週報，包含亮點、指標、阻塞項與下週計劃。"
|
|
|
|
[i18n.ja]
|
|
name = "週次レポートジェネレーター"
|
|
description = "雑多な作業メモを整えられた週次レポートに変換：ハイライト、指標、ブロッカー、翌週の優先事項。"
|
|
|
|
[i18n.ko]
|
|
name = "주간 보고서 생성기"
|
|
description = "단편적인 업무 노트를 다듬어진 주간 보고서로 변환: 하이라이트, 지표, 블로커, 다음 주 우선순위."
|
|
|
|
[i18n.de]
|
|
name = "Wochenbericht-Generator"
|
|
description = "Rohe Arbeitsnotizen in einen polierten Wochenbericht überführen: Highlights, Metriken, Blocker und Prioritäten der nächsten Woche."
|
|
|
|
[i18n.es]
|
|
name = "Generador de informe semanal"
|
|
description = "Convierte notas de trabajo en un informe semanal pulido con logros, métricas, bloqueos y prioridades para la próxima semana."
|
|
|
|
[i18n.fr]
|
|
name = "Générateur de rapport hebdo"
|
|
description = "Transformer des notes de travail brutes en un rapport hebdomadaire soigné : faits marquants, métriques, blocages et priorités de la semaine suivante."
|