source-management by anthropics/knowledge-work-plugins
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill source-management如果你看到不熟悉的占位符或需要检查哪些工具已连接,请参阅 CONNECTORS.md。
了解可用的源,帮助连接新的源,并管理源的查询方式。
通过检查可用工具来确定连接了哪些 MCP 源。每个源对应一组 MCP 工具:
| 源 | 核心能力 |
|---|---|
| ~~chat | 搜索消息,读取频道和线程 |
| 搜索消息,读取单个电子邮件 | |
| ~~cloud storage | 搜索文件,获取文档内容 |
| ~~project tracker | 搜索任务,输入提示搜索 |
| ~~CRM | 查询记录(账户、联系人、商机) |
| ~~knowledge base | 语义搜索,关键词搜索 |
如果某个工具前缀可用,则表示该源已连接且可搜索。
当用户搜索但连接了很少或没有连接源时:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
你当前连接了 [N] 个源:[列表]。
要扩展搜索范围,你可以在 MCP 设置中连接其他源:
- ~~chat — 消息、线程、频道
- ~~email — 电子邮件、对话、附件
- ~~cloud storage — 文档、表格、幻灯片
- ~~project tracker — 任务、项目、里程碑
- ~~CRM — 账户、联系人、商机
- ~~knowledge base — wiki 页面、知识库文章
连接的源越多,搜索结果就越完整。
当用户询问未连接的特定工具时:
[工具名称] 当前未连接。要添加它:
1. 打开你的 MCP 设置
2. 添加 [工具] MCP 服务器配置
3. 在提示时进行身份验证
连接后,它将自动包含在未来的搜索中。
不同的查询类型受益于首先搜索某些源。使用这些优先级来加权结果,而不是跳过源:
决策查询("我们决定了什么..."):
1. ~~chat(发生决策的对话)
2. ~~email(决策确认、公告)
3. ~~cloud storage(会议记录、决策日志)
4. Wiki(如果决策有文档记录)
5. Task tracker(如果决策记录在任务中)
状态查询("...的状态是什么"):
1. Task tracker(~~project tracker — 权威状态)
2. ~~chat(实时讨论)
3. ~~cloud storage(状态文档、报告)
4. ~~email(状态更新邮件)
5. Wiki(项目页面)
文档查询("...的文档在哪里"):
1. ~~cloud storage(主要文档存储)
2. Wiki / ~~knowledge base(知识库)
3. ~~email(通过邮件分享的文档)
4. ~~chat(在频道中分享的文档)
5. Task tracker(链接到任务的文档)
人员查询("谁负责..." / "谁知道..."):
1. ~~chat(消息作者、频道成员)
2. Task tracker(任务分配者)
3. ~~cloud storage(文档作者、协作者)
4. ~~CRM(账户所有者、联系人)
5. ~~email(邮件参与者)
事实/政策查询("我们对...的政策是什么"):
1. Wiki / ~~knowledge base(官方文档)
2. ~~cloud storage(政策文档、手册)
3. ~~email(政策公告)
4. ~~chat(政策讨论)
当查询类型不明确时:
1. ~~chat(数量最多,最实时)
2. ~~email(正式沟通)
3. ~~cloud storage(文档和文件)
4. Wiki / ~~knowledge base(结构化知识)
5. Task tracker(工作项)
6. CRM(客户数据)
MCP 源可能有速率限制。请妥善处理:
速率限制响应通常表现为:
当源被速率限制时:
注意:[源] 暂时受到速率限制。以下结果来自
[其他源]。你可以在几分钟后重试以包含 [源]。
4. 对于摘要 — 如果在扫描过程中受到速率限制,请注明在触发限制之前覆盖了哪个时间范围
在会话期间跟踪源可用性:
源状态:
~~chat: ✓ 可用
~~email: ✓ 可用
~~cloud storage: ✓ 可用
~~project tracker: ✗ 未连接
~~CRM: ✗ 未连接
~~knowledge base: ⚠ 速率限制(2 分钟后重试)
报告搜索结果时,请包含搜索了哪些源,以便用户了解答案的范围。
企业搜索插件可与任何 MCP 连接的源配合使用。随着新的 MCP 服务器可用,它们可以添加到 .mcp.json 配置中。搜索和摘要命令将根据可用工具自动检测并包含新源。
要添加新源:
.mcp.json每周安装数
148
仓库
GitHub 星标
8.8K
首次出现
2026年1月31日
安全审计
安装于
opencode130
codex128
gemini-cli124
github-copilot118
claude-code114
amp111
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Knows what sources are available, helps connect new ones, and manages how sources are queried.
Determine which MCP sources are connected by checking available tools. Each source corresponds to a set of MCP tools:
| Source | Key capabilities |
|---|---|
| ~~chat | Search messages, read channels and threads |
| Search messages, read individual emails | |
| ~~cloud storage | Search files, fetch document contents |
| ~~project tracker | Search tasks, typeahead search |
| ~~CRM | Query records (accounts, contacts, opportunities) |
| ~~knowledge base | Semantic search, keyword search |
If a tool prefix is available, the source is connected and searchable.
When a user searches but has few or no sources connected:
You currently have [N] source(s) connected: [list].
To expand your search, you can connect additional sources in your MCP settings:
- ~~chat — messages, threads, channels
- ~~email — emails, conversations, attachments
- ~~cloud storage — docs, sheets, slides
- ~~project tracker — tasks, projects, milestones
- ~~CRM — accounts, contacts, opportunities
- ~~knowledge base — wiki pages, knowledge base articles
The more sources you connect, the more complete your search results.
When a user asks about a specific tool that is not connected:
[Tool name] isn't currently connected. To add it:
1. Open your MCP settings
2. Add the [tool] MCP server configuration
3. Authenticate when prompted
Once connected, it will be automatically included in future searches.
Different query types benefit from searching certain sources first. Use these priorities to weight results, not to skip sources:
Decision queries ("What did we decide..."):
1. ~~chat (conversations where decisions happen)
2. ~~email (decision confirmations, announcements)
3. ~~cloud storage (meeting notes, decision logs)
4. Wiki (if decisions are documented)
5. Task tracker (if decisions are captured in tasks)
Status queries ("What's the status of..."):
1. Task tracker (~~project tracker — authoritative status)
2. ~~chat (real-time discussion)
3. ~~cloud storage (status docs, reports)
4. ~~email (status update emails)
5. Wiki (project pages)
Document queries ("Where's the doc for..."):
1. ~~cloud storage (primary doc storage)
2. Wiki / ~~knowledge base (knowledge base)
3. ~~email (docs shared via email)
4. ~~chat (docs shared in channels)
5. Task tracker (docs linked to tasks)
People queries ("Who works on..." / "Who knows about..."):
1. ~~chat (message authors, channel members)
2. Task tracker (task assignees)
3. ~~cloud storage (doc authors, collaborators)
4. ~~CRM (account owners, contacts)
5. ~~email (email participants)
Factual/Policy queries ("What's our policy on..."):
1. Wiki / ~~knowledge base (official documentation)
2. ~~cloud storage (policy docs, handbooks)
3. ~~email (policy announcements)
4. ~~chat (policy discussions)
When query type is unclear:
1. ~~chat (highest volume, most real-time)
2. ~~email (formal communications)
3. ~~cloud storage (documents and files)
4. Wiki / ~~knowledge base (structured knowledge)
5. Task tracker (work items)
6. CRM (customer data)
MCP sources may have rate limits. Handle them gracefully:
Rate limit responses typically appear as:
When a source is rate limited:
Note: [Source] is temporarily rate limited. Results below are from
[other sources]. You can retry in a few minutes to include [source].
4. For digests — if rate limited mid-scan, note which time range was covered before the limit hit
Track source availability during a session:
Source Status:
~~chat: ✓ Available
~~email: ✓ Available
~~cloud storage: ✓ Available
~~project tracker: ✗ Not connected
~~CRM: ✗ Not connected
~~knowledge base: ⚠ Rate limited (retry in 2 min)
When reporting search results, include which sources were searched so the user knows the scope of the answer.
The enterprise search plugin works with any MCP-connected source. As new MCP servers become available, they can be added to the .mcp.json configuration. The search and digest commands will automatically detect and include new sources based on available tools.
To add a new source:
.mcp.jsonWeekly Installs
148
Repository
GitHub Stars
8.8K
First Seen
Jan 31, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode130
codex128
gemini-cli124
github-copilot118
claude-code114
amp111
AI Elements:基于shadcn/ui的AI原生应用组件库,快速构建对话界面
56,200 周安装