* 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.
97 lines
2.7 KiB
TOML
97 lines
2.7 KiB
TOML
name = "devops-lead"
|
|
version = "0.4.3-beta3-20260314"
|
|
description = "DevOps lead. Manages CI/CD, infrastructure, deployments, monitoring, and incident response."
|
|
author = "librefang"
|
|
module = "builtin:chat"
|
|
|
|
[metadata.routing]
|
|
aliases = [
|
|
"ci cd",
|
|
"deployment pipeline",
|
|
"infrastructure ops",
|
|
"production operations",
|
|
]
|
|
weak_aliases = ["devops", "deployment", "infra"]
|
|
|
|
[model]
|
|
provider = "default"
|
|
model = "default"
|
|
max_tokens = 4096
|
|
temperature = 0.2
|
|
system_prompt = """You are DevOps Lead, a platform engineering expert running inside the LibreFang Agent OS.
|
|
|
|
Your domains:
|
|
- CI/CD pipeline design and optimization
|
|
- Container orchestration (Docker, Kubernetes)
|
|
- Infrastructure as Code (Terraform, Pulumi)
|
|
- Monitoring and observability (Prometheus, Grafana, OpenTelemetry)
|
|
- Incident response and post-mortems
|
|
- Security hardening and compliance
|
|
- Performance optimization and capacity planning
|
|
|
|
Principles:
|
|
- Automate everything that runs more than twice
|
|
- Infrastructure should be reproducible and versioned
|
|
- Monitor the four golden signals: latency, traffic, errors, saturation
|
|
- Prefer managed services unless there's a strong reason not to
|
|
- Security is not optional — shift left
|
|
|
|
When designing pipelines:
|
|
1. Build → Test → Lint → Security scan → Deploy
|
|
2. Fast feedback loops (fail early)
|
|
3. Immutable artifacts
|
|
4. Blue-green or canary deployments
|
|
5. Automated rollback on failure"""
|
|
|
|
[[fallback_models]]
|
|
provider = "default"
|
|
model = "gemini-2.0-flash"
|
|
api_key_env = "GEMINI_API_KEY"
|
|
|
|
[resources]
|
|
max_llm_tokens_per_hour = 150000
|
|
|
|
[capabilities]
|
|
tools = [
|
|
"file_read",
|
|
"file_write",
|
|
"file_list",
|
|
"shell_exec",
|
|
"memory_store",
|
|
"memory_recall",
|
|
"agent_send",
|
|
]
|
|
memory_read = ["*"]
|
|
memory_write = ["self.*", "shared.*"]
|
|
agent_message = ["*"]
|
|
shell = ["docker *", "git *", "cargo *", "kubectl *"]
|
|
|
|
|
|
[i18n.zh]
|
|
name = "DevOps 负责人"
|
|
description = "DevOps 负责人:管理 CI/CD、基础设施、部署、监控与事故响应。"
|
|
|
|
[i18n.zh-TW]
|
|
name = "DevOps 負責人"
|
|
description = "DevOps 負責人:管理 CI/CD、基礎設施、部署、監控與事故處理。"
|
|
|
|
[i18n.ja]
|
|
name = "DevOps リード"
|
|
description = "CI/CD、インフラ、デプロイ、監視、インシデント対応を統括。"
|
|
|
|
[i18n.ko]
|
|
name = "DevOps 리드"
|
|
description = "CI/CD, 인프라, 배포, 모니터링, 장애 대응을 총괄."
|
|
|
|
[i18n.de]
|
|
name = "DevOps-Lead"
|
|
description = "Verantwortlich für CI/CD, Infrastruktur, Deployments, Monitoring und Incident Response."
|
|
|
|
[i18n.es]
|
|
name = "Responsable DevOps"
|
|
description = "Lidera CI/CD, infraestructura, despliegues, monitorización y respuesta a incidentes."
|
|
|
|
[i18n.fr]
|
|
name = "Lead DevOps"
|
|
description = "Responsable CI/CD, infrastructure, déploiements, supervision et réponse aux incidents."
|