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.
124 lines
3.6 KiB
TOML
124 lines
3.6 KiB
TOML
id = "blog-post"
|
|
name = "Blog Post Writer"
|
|
description = "Research a topic, build a structured outline, write a full-length blog post, then optimise for SEO."
|
|
category = "creation"
|
|
tags = ["writing", "blog", "seo", "content"]
|
|
|
|
[i18n.zh]
|
|
name = "博客文章撰写"
|
|
description = "调研主题，构建结构化提纲，撰写完整博客文章，并进行 SEO 优化。"
|
|
|
|
[[parameters]]
|
|
name = "topic"
|
|
description = "Blog post topic or working title"
|
|
param_type = "string"
|
|
required = true
|
|
|
|
[[parameters]]
|
|
name = "audience"
|
|
description = "Target audience and their expertise level"
|
|
param_type = "string"
|
|
required = false
|
|
default = "general audience"
|
|
|
|
[[parameters]]
|
|
name = "tone"
|
|
description = "Desired tone (e.g. technical, conversational, authoritative)"
|
|
param_type = "string"
|
|
required = false
|
|
default = "informative and engaging"
|
|
|
|
[[steps]]
|
|
name = "research"
|
|
prompt_template = """
|
|
You are a research journalist. For the blog topic below, compile:
|
|
1. Key facts, statistics, and data points (with source type)
|
|
2. Common misconceptions to debunk
|
|
3. Expert perspectives and contrasting views
|
|
4. Recent developments or trends
|
|
5. Concrete examples and case studies
|
|
6. Angles that haven't been covered well in existing content
|
|
|
|
Topic: {{topic}}
|
|
Audience: {{audience}}
|
|
"""
|
|
|
|
[[steps]]
|
|
name = "outline"
|
|
prompt_template = """
|
|
You are a content strategist. Create a detailed blog post outline:
|
|
- Compelling headline (3 options)
|
|
- Hook / opening angle
|
|
- H2 sections with H3 subsections
|
|
- Key point per section
|
|
- Data or example to use in each section
|
|
- Conclusion and CTA
|
|
|
|
Target length: 1200-1800 words.
|
|
Tone: {{tone}}
|
|
Audience: {{audience}}
|
|
|
|
Research:
|
|
{{research}}
|
|
"""
|
|
depends_on = ["research"]
|
|
|
|
[[steps]]
|
|
name = "draft"
|
|
prompt_template = """
|
|
Write the full blog post following the outline. Guidelines:
|
|
- Open with a hook that immediately addresses the reader's pain or curiosity
|
|
- Use short paragraphs (3-4 sentences max)
|
|
- Include the statistics and examples from research
|
|
- Use subheadings to aid scannability
|
|
- End with a clear takeaway and one actionable CTA
|
|
- Tone: {{tone}}
|
|
|
|
Outline:
|
|
{{outline}}
|
|
|
|
Research:
|
|
{{research}}
|
|
"""
|
|
depends_on = ["outline", "research"]
|
|
|
|
[[steps]]
|
|
name = "seo_optimise"
|
|
prompt_template = """
|
|
SEO-optimise the blog post:
|
|
1. **Primary keyword** — identify the best target keyword
|
|
2. **Meta title** (under 60 chars) and **meta description** (under 155 chars)
|
|
3. **Keyword placement** — suggest where to naturally insert the primary keyword and 3 secondary keywords
|
|
4. **Internal link opportunities** — topics to link to
|
|
5. **Image alt text suggestions** — 2-3 descriptive alts
|
|
6. **Revised headline** if needed for keyword inclusion
|
|
|
|
Draft:
|
|
{{draft}}
|
|
"""
|
|
depends_on = ["draft"]
|
|
|
|
[i18n.zh-TW]
|
|
name = "部落格文章撰寫"
|
|
description = "調研主題、建立結構化大綱、撰寫完整部落格文章，並進行 SEO 優化。"
|
|
|
|
[i18n.ja]
|
|
name = "ブログ記事ライター"
|
|
description = "トピックを調査し、構造化されたアウトラインを作り、記事を執筆、SEO を最適化。"
|
|
|
|
[i18n.ko]
|
|
name = "블로그 포스트 작성"
|
|
description = "주제를 조사하고 구조화된 개요를 만든 뒤, 전체 블로그 글을 작성하고 SEO를 최적화합니다."
|
|
|
|
[i18n.de]
|
|
name = "Blogpost-Autor"
|
|
description = "Thema recherchieren, strukturiertes Outline erstellen, vollständigen Blogpost schreiben und für SEO optimieren."
|
|
|
|
[i18n.es]
|
|
name = "Redactor de blog"
|
|
description = "Investiga un tema, crea un esquema estructurado, redacta un post completo y optimiza para SEO."
|
|
|
|
[i18n.fr]
|
|
name = "Rédacteur de blog"
|
|
description = "Rechercher un sujet, bâtir un plan structuré, rédiger un article complet puis optimiser pour le SEO."
|