본문으로 건너뛰기
cccskills
무료GitHub에 공개

source-management

Manage the connected sources used for workplace search. Identify available chat, email, document, and business systems, guide new connections, prioritize sources by question type, and explain search coverage when request limits interrupt access.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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.

설치 방법 보기

이럴 때 유용합니다

  • Check which workplace sources are searchable
  • Get guidance on connecting a new source
  • Prioritize sources for decisions, status, or policy questions
  • Continue searching when one source reaches its request limit

포함된 파일(1)

  • SKILL.md5.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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 settings
2. Add the [tool] MCP server configuration
3. 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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Review a design or web page against WCAG 2.1 AA, an accessibility standard. Organize findings on contrast, keyboard access, forms, and screen reader behavior, with severity levels and practical recommendations for fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Review accessibility before design handoff
  • Check text and interface color contrast
  • Review keyboard navigation and focus behavior
anthropics/knowledge-work-plugins3.1만2026년 10월 19일 업데이트

Build a single brief on an existing customer using available sales records, emails, documents, call notes, and internal chat. Understand the current situation, key contacts, recent discussions, and gaps that may need attention.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Preparing for a meeting with an existing customer
  • Catching up on an account during a handover
  • Reviewing recent discussions and stalled opportunities
anthropics/knowledge-work-plugins3.1만2026년 10월 19일 업데이트

Build or refresh a strategic customer account plan from sales records, emails, and meeting transcripts. Organize goals, stakeholders, growth opportunities, risks, and dated actions into a document, then sync approved highlights to the customer relationship management system.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating a quarterly plan for a key customer
  • Refreshing an existing account plan
  • Reviewing stakeholder coverage and growth opportunities
anthropics/knowledge-work-plugins3.1만2026년 10월 19일 업데이트

Research prospective companies and contacts, check existing customer records, and assess fit against your ideal customer profile. Receive a sourced brief covering recent developments, likely priorities, outreach talking points, and a suggested next step.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Researching a company before a sales approach
  • Checking existing account records and ownership
  • Assessing fit against your ideal customer profile
anthropics/knowledge-work-plugins3.1만2026년 10월 19일 업데이트

Research sales accounts using Common Room data to summarize company details, buying signals, ownership, and key contacts. Answer specific questions directly or prepare a broader briefing with evidence-based next steps, clearly identifying missing information.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Prepare a company briefing before a sales conversation
  • Check buying signals and recent account activity
  • Find account owners and key contacts
anthropics/knowledge-work-plugins3.1만2026년 10월 19일 업데이트

Score and group accounts by customer fit and engagement, such as recent contact and open sales opportunities. Identify where to focus sales effort, choose next actions, and spot promising accounts with neglected outreach or missing information.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Prioritize a portfolio of assigned accounts
  • Find strong-fit accounts that need outreach
  • Identify promising accounts with no recent activity
anthropics/knowledge-work-plugins3.1만2026년 10월 19일 업데이트

anthropics의 스킬 모두 보기

이 스킬의 문제 신고