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.
94 lines
3.3 KiB
TOML
94 lines
3.3 KiB
TOML
id = "content-review"
|
|
name = "Content Review"
|
|
description = "Multi-agent content review pipeline that drafts, reviews for quality and accuracy, then produces a final edited version incorporating feedback."
|
|
category = "creation"
|
|
tags = ["content", "review", "writing", "editing"]
|
|
|
|
[i18n.zh]
|
|
name = "内容审校"
|
|
description = "多智能体内容审校流水线，先起草内容，再分别审查质量和准确性，最后综合反馈生成终稿。"
|
|
|
|
[[parameters]]
|
|
name = "topic"
|
|
description = "The topic or subject to write about"
|
|
param_type = "string"
|
|
required = true
|
|
|
|
[[parameters]]
|
|
name = "tone"
|
|
description = "Desired tone (formal, casual, technical, persuasive)"
|
|
param_type = "string"
|
|
required = false
|
|
default = "formal"
|
|
|
|
[[parameters]]
|
|
name = "word_count"
|
|
description = "Target word count for the content"
|
|
param_type = "number"
|
|
required = false
|
|
default = 500
|
|
|
|
[[steps]]
|
|
name = "draft"
|
|
prompt_template = "Write a {{tone}} article about {{topic}} with approximately {{word_count}} words. Include a clear introduction, well-structured body, and conclusion. Use concrete examples where appropriate."
|
|
|
|
[[steps]]
|
|
name = "review_quality"
|
|
prompt_template = """
|
|
Review the following draft for writing quality. Evaluate clarity, coherence, grammar, tone consistency (target: {{tone}}), and overall readability. Provide specific, actionable feedback with line-level suggestions.
|
|
|
|
Draft:
|
|
{{draft}}
|
|
"""
|
|
depends_on = ["draft"]
|
|
|
|
[[steps]]
|
|
name = "review_accuracy"
|
|
prompt_template = """
|
|
Review the following draft for factual accuracy and logical consistency. Flag any claims that appear unsupported, statistics that need citation, logical fallacies, or misleading statements. List each issue with a suggested correction.
|
|
|
|
Draft:
|
|
{{draft}}
|
|
"""
|
|
depends_on = ["draft"]
|
|
|
|
[[steps]]
|
|
name = "final_edit"
|
|
prompt_template = """
|
|
Produce a final edited version of the draft below, incorporating the quality and accuracy feedback. Preserve the original voice and intent while addressing all identified issues.
|
|
|
|
Original draft:
|
|
{{draft}}
|
|
|
|
Quality feedback:
|
|
{{review_quality}}
|
|
|
|
Accuracy feedback:
|
|
{{review_accuracy}}
|
|
"""
|
|
depends_on = ["review_quality", "review_accuracy"]
|
|
|
|
[i18n.zh-TW]
|
|
name = "內容審校"
|
|
description = "多智能體內容審校流水線，先起草內容，再分別審查品質與準確性，最後綜合回饋產生終稿。"
|
|
|
|
[i18n.ja]
|
|
name = "コンテンツレビュー"
|
|
description = "複数 Agent による内容レビュー。下書きを作成し、品質と正確性をレビュー、フィードバックを反映した最終版を生成。"
|
|
|
|
[i18n.ko]
|
|
name = "콘텐츠 검토"
|
|
description = "다중 에이전트 콘텐츠 검토 파이프라인. 초안을 작성하고 품질과 정확성을 검토한 뒤 피드백을 반영한 최종본을 생성."
|
|
|
|
[i18n.de]
|
|
name = "Content-Review"
|
|
description = "Multi-Agent-Review-Pipeline: Entwurf erstellen, Qualität und Korrektheit prüfen und eine endgültige Fassung mit eingearbeitetem Feedback liefern."
|
|
|
|
[i18n.es]
|
|
name = "Revisión de contenido"
|
|
description = "Pipeline multiagente que redacta, revisa calidad y precisión y produce una versión final con la retroalimentación incorporada."
|
|
|
|
[i18n.fr]
|
|
name = "Revue de contenu"
|
|
description = "Pipeline multi-agent : rédige, contrôle la qualité et la précision, puis produit une version finale intégrant les retours."
|