$ loading_
帮助用户管理企业搜索已连接数据源，并优化接入顺序与限流认知。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "source-management" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/enterprise-search/skills/source-management/SKILL.md 2. 保存为 ~/.claude/skills/source-management/SKILL.md 3. 装好后重载技能，告诉我可以用了
请列出当前企业搜索已连接和可检测到的数据源，并说明哪些还未完成连接。
返回数据源清单，区分已连接、可用但未连接及异常状态。
我想把新的知识库接入企业搜索，请告诉我下一步该连接什么、如何连接，以及连接前需要确认的条件。
给出新增数据源的接入建议、操作步骤和前置检查项。
请根据访问频率和稳定性，建议当前数据源的优先级排序，并提醒我哪些来源可能受限流影响。
输出推荐的来源优先级，并标注可能的限流风险与注意事项。
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:
…
围绕客户问题进行多来源调研与溯源，快速整理背景并支持准确回复。
连接思源笔记与 AI，进行笔记检索、整理、导出和知识管理自动化