$ loading_
Manage enterprise search sources, connections, priority order, and rate-limit awareness.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "source-management" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/enterprise-search/skills/source-management/SKILL.md 2. Save it as ~/.claude/skills/source-management/SKILL.md 3. Reload skills and tell me it's ready
List the enterprise search sources that are already connected and detectable, and identify which ones are not fully connected yet.
A source inventory showing connected, available-but-unconnected, and problematic sources.
I want to add a new knowledge base to enterprise search. Tell me what to connect next, how to connect it, and what prerequisites to verify first.
Step-by-step guidance for adding the source, including recommendations and prerequisite checks.
Based on access frequency and reliability, suggest a priority order for current sources and warn me which ones may be affected by rate limits.
A recommended source priority order with rate-limit risks and operational cautions noted.
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:
…
Embed Zoom Virtual Agent chat on web with secure controls and context updates.
Quickly add Zoom’s prebuilt React video UI to web workflows.
Create stakeholder updates tailored to audience, cadence, and communication goals.
Review an analysis for methodology, accuracy, bias, and evidence support.
Generate people analytics reports on headcount, attrition, diversity, and org health.
Identify, categorize, and prioritize technical debt for smarter refactoring decisions.
Discover and access massive public geospatial datasets from Source Cooperative.
Search repositories, find code, and fetch content with Sourcegraph AI search.
Index local SQLite, CSV, and Markdown metadata for hybrid semantic search.
Query and retrieve data across GitHub, Neo4j, PostgreSQL, and Milvus.
Connect SiYuan Note so AI can search, read, create, and organize notes.
Access, search, retrieve, and manage microCMS content through MCP.