资讯资讯

WorkBuddy 开放平台解析:用 Skill、Connector、专家与知识库给 AI 同事「配工具」WorkBuddy 开放平台解析:用 Skill、Connector、专家与知识库给 AI 同事「配工具」

📅 2026-09-03 ⏱️ 约 5 分钟阅读⏱️ 5 min read ✍️ AI导航编辑部✍️ AI Nav Editorial 🔗 ai-tokens.cn
WorkBuddy 最近把「AI 办公工作台」正式做成了一套可扩展的开放平台(扩展体系):不再只是聊天助手,而是允许企业和个人在之上扩展能力、接入外部服务、封装领域专家、挂载企业知识——相当于给你的 AI 同事「装上班、配工具」。WorkBuddy has turned its AI office workbench into an extensible Open Platform (extension system): no longer just a chat assistant, it lets enterprises and individuals extend capabilities, connect external services, package domain experts and mount enterprise knowledge — essentially 'kitting out' your AI colleague.

WorkBuddy 最近把「AI 办公工作台」正式做成了一套可扩展的开放平台(扩展体系)。简单说,它不再只是一个聊天助手,而是允许企业和个人在之上扩展能力、接入外部服务、封装领域专家、挂载企业知识——相当于给你的 AI 同事「装上班、配工具」。

扩展能力靠 Skill。Skill 是可复用的能力单元,封装特定领域的指令、工具与知识;系统已内置约 301 个开箱即用,企业/成员还能自定义上传,并按白名单/黑名单管控谁能使用。

接入外部服务靠 Connector / MCP。每个连接器封装认证凭证 + MCP 服务端配置 + 工具权限过滤,支持 MCP OAuth 2.1、OAuth 2.0、API Key 三种认证;创建后组织内成员无需单独配置即可通过 Agent 读写 GitHub、腾讯文档等平台数据。

封装领域专家靠 Expert——角色化的 AI 代理,以 .zip 包上传,按白/黑名单下发;挂载企业私有数据靠企业知识库,二者共同构成「懂业务」的 AI 同事。

关键是安全:Skill 运行期可向平台申请短时效的 Open Platform Token,去读写用户的腾讯文档、网盘、邮箱等资源,而不必长期持有凭据——凭据由平台按会话临时签发。

管理上,企业后台用白/黑名单策略统一管控 Skill/Connector/Expert 的可见与可用范围,并通过「企业市场」对成员树形展示;个人用户则通过 BuiltinMarket 一键安装技能与连接器。再配合 RRULE 自动化(每天/每周/每月/每年定时任务),把重复活交给机器。

想动手?把一段 MCP 连接器配置合进 ~/.workbuddy/mcp.json,再到连接器管理页点「信任」即可启用;详细包结构、manifest 示例与企业版档位,见文末「阅读完整技术文档」。本文整理自 WorkBuddy 官方文档,价格与功能以官方最新公告为准。

WorkBuddy has turned its AI office workbench into an extensible Open Platform (extension system): it is no longer just a chat assistant, but lets enterprises and individuals extend capabilities, connect external services, package domain experts and mount enterprise knowledge — essentially 'kitting out' your AI colleague.

Capabilities extend via Skill — a reusable unit encapsulating domain instructions, tools and knowledge. ~301 built-in Skills ship ready to use; enterprises/members can also upload custom ones, gated by allow/deny lists.

External services connect via Connector / MCP. Each connector wraps credentials + MCP server config + tool-permission filtering, supporting MCP OAuth 2.1, OAuth 2.0 and API Key. Once created, org members use it through the Agent with no separate setup — reading/writing GitHub, Tencent Docs, etc.

Domain experts come via Expert — role-based agents uploaded as .zip and distributed by allow/deny list; enterprise private data mounts via the Knowledge Base. Together they make an AI colleague that 'knows the business'.

Security matters: at runtime a Skill can request a short-lived Open Platform Token to read/write the user's Tencent Docs, drive, email, etc., without holding credentials long-term — tokens are issued per session by the platform.

On governance, the admin console uses allow/deny lists to control visibility and availability of Skills/Connectors/Experts, showcased to members via the Enterprise Market; individuals install skills/connectors one-click via BuiltinMarket. Add RRULE automations (daily/weekly/monthly/yearly) to hand repetitive work to the machine.

Want to try? Merge an MCP connector config into ~/.workbuddy/mcp.json and click 'Trust' in Connector management to enable it. For package structure, manifest examples and enterprise tiers, see 'Read the full technical doc' at the end. Compiled from WorkBuddy official docs; pricing/features follow official notices.