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.
101 lines
2.9 KiB
TOML
101 lines
2.9 KiB
TOML
id = "decision-matrix"
|
|
name = "Decision Matrix"
|
|
description = "Evaluate competing options against weighted criteria to produce a clear, defensible recommendation."
|
|
category = "thinking"
|
|
tags = ["decision", "analysis", "strategy", "thinking"]
|
|
|
|
[i18n.zh]
|
|
name = "决策矩阵"
|
|
description = "对竞争方案按加权标准进行评估，输出清晰、有据可查的推荐结论。"
|
|
|
|
[[parameters]]
|
|
name = "decision"
|
|
description = "The decision to be made and its context"
|
|
param_type = "string"
|
|
required = true
|
|
|
|
[[parameters]]
|
|
name = "options"
|
|
description = "The options or alternatives being considered"
|
|
param_type = "string"
|
|
required = true
|
|
|
|
[[steps]]
|
|
name = "criteria"
|
|
prompt_template = """
|
|
You are a decision analyst. For the decision below, define the evaluation criteria:
|
|
1. List 5-8 criteria that matter most for this decision
|
|
2. For each criterion: define what 'good' looks like (high score) and 'bad' looks like (low score)
|
|
3. Assign weights (must sum to 100%) based on business importance
|
|
4. Note which criteria are must-haves (disqualifiers if failed)
|
|
|
|
Decision: {{decision}}
|
|
Options: {{options}}
|
|
"""
|
|
|
|
[[steps]]
|
|
name = "scoring"
|
|
prompt_template = """
|
|
Score each option against each criterion on a 1-10 scale. Justify every score with one sentence of evidence or reasoning. Then calculate weighted scores.
|
|
|
|
Format as a table: Option | Criterion | Raw Score | Weight | Weighted Score.
|
|
|
|
Add a totals row per option.
|
|
|
|
Decision: {{decision}}
|
|
Options: {{options}}
|
|
|
|
Criteria and weights:
|
|
{{criteria}}
|
|
"""
|
|
depends_on = ["criteria"]
|
|
|
|
[[steps]]
|
|
name = "recommendation"
|
|
prompt_template = """
|
|
Synthesise the analysis into a decision memo:
|
|
|
|
## Recommendation
|
|
Clear winner with one-sentence rationale.
|
|
|
|
## Why Not the Others
|
|
For each non-recommended option: the decisive weakness.
|
|
|
|
## Key Risks of the Recommended Option
|
|
Top 3 risks and mitigations.
|
|
|
|
## Conditions That Would Change This Recommendation
|
|
What new information would flip the decision.
|
|
|
|
## Next Steps
|
|
3 immediate actions to execute the decision.
|
|
|
|
Scoring:
|
|
{{scoring}}
|
|
"""
|
|
depends_on = ["scoring"]
|
|
|
|
[i18n.zh-TW]
|
|
name = "決策矩陣"
|
|
description = "依加權標準評估多個方案，輸出清晰且有依據的推薦結論。"
|
|
|
|
[i18n.ja]
|
|
name = "意思決定マトリクス"
|
|
description = "重み付き基準で複数案を評価し、根拠ある推奨結論を導出。"
|
|
|
|
[i18n.ko]
|
|
name = "의사결정 매트릭스"
|
|
description = "가중 기준으로 경쟁하는 옵션들을 평가해 명확하고 근거 있는 권고안을 도출."
|
|
|
|
[i18n.de]
|
|
name = "Entscheidungsmatrix"
|
|
description = "Konkurrierende Optionen anhand gewichteter Kriterien bewerten und eine klare, belastbare Empfehlung ableiten."
|
|
|
|
[i18n.es]
|
|
name = "Matriz de decisión"
|
|
description = "Evalúa opciones rivales frente a criterios ponderados y produce una recomendación clara y defendible."
|
|
|
|
[i18n.fr]
|
|
name = "Matrice de décision"
|
|
description = "Évaluer des options concurrentes selon des critères pondérés et produire une recommandation claire et défendable."
|