Source Management

作者 anthropicsae1513ea94dc無授權條款27K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

Manages connected MCP sources for enterprise search. Detects available sources, guides users to connect new ones, handles source priority ordering, and manages rate limiting awareness.

精選僅含說明AI & Agents
AI 產生的概覽

管理企業搜尋所用的已連線 MCP 來源:偵測可用性、引導連線、安排來源優先順序並處理速率限制。

功能
此技能定義代理如何追蹤企業搜尋中可用的 MCP 連線來源(聊天、電子郵件、雲端儲存、專案追蹤工具、CRM、知識庫)。它提供指引,說明如何告知使用者已連線哪些來源、如何連線新來源,以及如何在工作階段中回報來源健康狀態。它也依查詢類型規定優先順序,並訂出偵測、處理與預防速率限制的規則。它產出的是指示以及給使用者看的狀態或連線訊息,而非檔案或程式碼。
適用情境
當代理跨多個 MCP 來源執行企業搜尋或摘要工作,需要知道有哪些來源、哪些已連線,以及該依什麼順序查詢時使用。也適用於某個來源缺少、未驗證或受到速率限制,需要給使用者指引或狀態回報的情況。
執行需求
需要設定並驗證 MCP 連線的來源及其工具;此技能本身不含指令碼,只提供指示。它引用 CONNECTORS.md 檔案,以及用來新增自訂來源的 .mcp.json 設定。

Source Management

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.

Checking Available Sources

Determine which MCP sources are connected by checking available tools. Each source corresponds to a set of MCP tools:

SourceKey capabilities
~~chatSearch messages, read channels and threads
~~emailSearch messages, read individual emails
~~cloud storageSearch files, fetch document contents
~~project trackerSearch tasks, typeahead search
~~CRMQuery records (accounts, contacts, opportunities)
~~knowledge baseSemantic search, keyword search

If a tool prefix is available, the source is connected and searchable.

Guiding Users to Connect Sources

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 settings2. Add the [tool] MCP server configuration3. Authenticate when prompted
Once connected, it will be automatically included in future searches.

Source Priority Ordering

Different query types benefit from searching certain sources first. Use these priorities to weight results, not to skip sources:

By Query Type

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)

Default Priority (General Queries)

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)

Rate Limiting Awareness

MCP sources may have rate limits. Handle them gracefully:

Detection

Rate limit responses typically appear as:

  • HTTP 429 responses
  • Error messages mentioning "rate limit", "too many requests", or "quota exceeded"
  • Throttled or delayed responses

Handling

When a source is rate limited:

  1. Do not retry immediately — respect the limit
  2. Continue with other sources — do not block the entire search
  3. Inform the user:
Note: [Source] is temporarily rate limited. Results below are from[other sources]. You can retry in a few minutes to include [source].
  1. For digests — if rate limited mid-scan, note which time range was covered before the limit hit

Prevention

  • Avoid unnecessary API calls — check if the source is likely to have relevant results before querying
  • Use targeted queries over broad scans when possible
  • For digests, batch requests where the API supports it
  • Cache awareness: if a search was just run, avoid re-running the same query immediately

Source Health

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.

Adding Custom Sources

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:

  1. Add the MCP server configuration to .mcp.json
  2. Authenticate if required
  3. The source will be included in subsequent searches automatically

來源與署名

來源:anthropics/knowledge-work-plugins位於enterprise-search/skills/source-management提交ae1513e

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 anthropics/knowledge-work-plugins 的技能

Ticket Deflector

anthropics

精選

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

待分類27K今天更新

Tax Season Organizer

anthropics

精選

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

待分類27K今天更新

Tax Prep

anthropics

精選

根據已結帳的帳目準備稅務資料:季度預估繳稅明細,或年終 1099-NEC 清單與會計師資料包。

Business & Finance27K今天更新

Smb Onboard

anthropics

精選

引導小型企業主完成首次設定:連接工具、執行一次展現價值的配方、記錄業務背景並設定每週檢查節奏。

Productivity & Workflow27K今天更新

Smb Router

anthropics

精選

將小型企業主的需求轉接到合適的外掛技能或指令,並說明可用功能。

Productivity & Workflow27K今天更新

Month End Prep

anthropics

精選

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

待分類27K今天更新