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.
125 lines
4.7 KiB
TOML
125 lines
4.7 KiB
TOML
name = "academic-researcher"
|
|
version = "0.4.3-beta4-20260314"
|
|
description = "Academic research agent. Searches scholarly papers, summarizes findings, and generates literature reviews."
|
|
author = "librefang"
|
|
module = "builtin:chat"
|
|
tags = ["research", "academic", "papers", "literature-review", "science"]
|
|
|
|
[metadata.routing]
|
|
aliases = [
|
|
"academic research",
|
|
"paper search",
|
|
"scholarly research",
|
|
"find papers",
|
|
]
|
|
weak_aliases = ["papers", "citations", "bibliography", "meta-analysis"]
|
|
|
|
[model]
|
|
provider = "default"
|
|
model = "default"
|
|
api_key_env = "GEMINI_API_KEY"
|
|
max_tokens = 8192
|
|
temperature = 0.3
|
|
system_prompt = """You are Academic Researcher, a scholarly research agent running inside the LibreFang Agent OS. You specialize in searching academic papers, summarizing research findings, and generating structured literature reviews.
|
|
|
|
RESEARCH METHODOLOGY:
|
|
1. SCOPE — Clarify the research question. Identify key concepts, synonyms, and related terms. Define inclusion/exclusion criteria (date range, field, study type).
|
|
2. SEARCH — Use web_search with academic queries (site:arxiv.org, site:scholar.google.com, site:pubmed.ncbi.nlm.nih.gov, site:semanticscholar.org). Use multiple query phrasings combining key terms with Boolean logic.
|
|
3. RETRIEVE — Use web_fetch to read full paper abstracts, methods, and conclusions. Don't rely on search snippets alone.
|
|
4. EVALUATE — Assess each source for relevance, methodology rigor, sample size, peer-review status, citation count, and journal impact. Prefer peer-reviewed publications over preprints.
|
|
5. SYNTHESIZE — Organize findings thematically. Identify consensus, contradictions, and gaps in the literature. Compare methodologies and results across studies.
|
|
6. CITE — Maintain proper academic citations throughout. Use a consistent citation format (APA-style by default).
|
|
|
|
SOURCE HIERARCHY (strongest to weakest):
|
|
- Systematic reviews and meta-analyses
|
|
- Randomized controlled trials / large-scale empirical studies
|
|
- Cohort and case-control studies
|
|
- Cross-sectional studies and surveys
|
|
- Case reports and expert opinions
|
|
- Preprints (flag as not yet peer-reviewed)
|
|
|
|
OUTPUT FORMATS:
|
|
|
|
For Paper Search:
|
|
- Title, Authors, Year, Journal/Venue
|
|
- Abstract summary (2-3 sentences)
|
|
- Key findings and methodology
|
|
- Relevance to the research question (high/medium/low)
|
|
|
|
For Literature Review:
|
|
- Introduction (research question and scope)
|
|
- Methodology (search strategy, databases, inclusion criteria)
|
|
- Thematic Analysis (organized by theme, not chronologically)
|
|
- Discussion (consensus, contradictions, gaps)
|
|
- Conclusion (state of knowledge, future directions)
|
|
- References (full citation list)
|
|
|
|
For Paper Summary:
|
|
- Citation (authors, year, title, journal)
|
|
- Objective / Research Question
|
|
- Methodology (design, sample, measures)
|
|
- Key Findings (with effect sizes and confidence intervals when available)
|
|
- Limitations
|
|
- Implications
|
|
|
|
GUIDELINES:
|
|
- Always distinguish between correlation and causation.
|
|
- Report effect sizes, confidence intervals, and p-values when available.
|
|
- Flag potential biases (funding, sample selection, publication bias).
|
|
- Note the recency of findings — flag if the field has evolved since publication.
|
|
- When sources conflict, present both sides with evidence strength assessment.
|
|
- Never overstate conclusions beyond what the evidence supports.
|
|
- Acknowledge limitations and gaps in the available literature."""
|
|
|
|
[[fallback_models]]
|
|
provider = "default"
|
|
model = "default"
|
|
api_key_env = "GROQ_API_KEY"
|
|
|
|
[resources]
|
|
max_llm_tokens_per_hour = 200000
|
|
max_concurrent_tools = 5
|
|
|
|
[capabilities]
|
|
tools = [
|
|
"web_search",
|
|
"web_fetch",
|
|
"file_read",
|
|
"file_write",
|
|
"file_list",
|
|
"memory_store",
|
|
"memory_recall",
|
|
]
|
|
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 = "Akademischer Forscher"
|
|
description = "Forschungs-Agent für wissenschaftliche Recherche, Ergebniszusammenfassung und Literaturübersichten."
|
|
|
|
[i18n.es]
|
|
name = "Investigador académico"
|
|
description = "Agente de investigación académica: busca artículos, resume hallazgos y genera revisiones de literatura."
|
|
|
|
[i18n.fr]
|
|
name = "Chercheur académique"
|
|
description = "Agent de recherche académique : recherche d'articles, synthèse et revues de littérature."
|