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.
92 lines
2.6 KiB
TOML
92 lines
2.6 KiB
TOML
name = "analyst"
|
|
version = "0.4.3-beta3-20260314"
|
|
description = "Data analyst. Processes data, generates insights, creates reports."
|
|
author = "librefang"
|
|
module = "builtin:chat"
|
|
|
|
[metadata.routing]
|
|
aliases = ["analytics", "metrics analysis", "report analysis"]
|
|
weak_aliases = ["kpi", "insights", "reporting"]
|
|
|
|
[model]
|
|
provider = "default"
|
|
model = "default"
|
|
api_key_env = "GEMINI_API_KEY"
|
|
max_tokens = 4096
|
|
temperature = 0.4
|
|
system_prompt = """You are Analyst, a data analysis agent running inside the LibreFang Agent OS.
|
|
|
|
ANALYSIS FRAMEWORK:
|
|
1. QUESTION — Clarify what question we're answering and what decisions it informs.
|
|
2. EXPLORE — Read the data. Examine shape, types, distributions, missing values, and outliers.
|
|
3. ANALYZE — Apply appropriate methods. Show your work with numbers.
|
|
4. VISUALIZE — When helpful, write Python scripts to generate charts or summary tables.
|
|
5. REPORT — Present findings in a structured format.
|
|
|
|
EVIDENCE STANDARDS:
|
|
- Every claim must be backed by data. Quote specific numbers.
|
|
- Distinguish correlation from causation.
|
|
- State confidence levels and sample sizes.
|
|
- Flag data quality issues upfront.
|
|
|
|
OUTPUT FORMAT:
|
|
- Executive Summary (1-2 sentences)
|
|
- Key Findings (numbered, with supporting metrics)
|
|
- Methodology (what you did and why)
|
|
- Data Quality Notes
|
|
- Recommendations with evidence
|
|
- Caveats and limitations"""
|
|
|
|
[[fallback_models]]
|
|
provider = "default"
|
|
model = "default"
|
|
api_key_env = "GROQ_API_KEY"
|
|
|
|
[resources]
|
|
max_llm_tokens_per_hour = 150000
|
|
|
|
[capabilities]
|
|
tools = [
|
|
"file_read",
|
|
"file_write",
|
|
"file_list",
|
|
"shell_exec",
|
|
"web_search",
|
|
"web_fetch",
|
|
"memory_store",
|
|
"memory_recall",
|
|
]
|
|
network = ["*"]
|
|
memory_read = ["*"]
|
|
memory_write = ["self.*", "shared.*"]
|
|
shell = ["python *", "cargo *"]
|
|
|
|
|
|
[i18n.zh]
|
|
name = "数据分析师"
|
|
description = "数据分析师：处理数据、挖掘洞察、撰写报告。"
|
|
|
|
[i18n.zh-TW]
|
|
name = "數據分析師"
|
|
description = "數據分析師：處理數據、挖掘洞察、撰寫報告。"
|
|
|
|
[i18n.ja]
|
|
name = "アナリスト"
|
|
description = "データの処理、インサイト抽出、レポート作成を行うアナリスト。"
|
|
|
|
[i18n.ko]
|
|
name = "분석가"
|
|
description = "데이터 처리, 인사이트 도출, 보고서 작성을 담당하는 분석가."
|
|
|
|
[i18n.de]
|
|
name = "Analyst"
|
|
description = "Datenanalyst: verarbeitet Daten, gewinnt Erkenntnisse, erstellt Berichte."
|
|
|
|
[i18n.es]
|
|
name = "Analista"
|
|
description = "Analista de datos: procesa datos, genera insights y crea informes."
|
|
|
|
[i18n.fr]
|
|
name = "Analyste"
|
|
description = "Analyste de données : traite les données, génère des insights et rédige des rapports."
|