source-management
installsforks
How to install source-management?
anthropics/knowledge-work-plugins/source-management
$npx -y skills add anthropics/knowledge-work-plugins --skill source-managementsource-management is an agent skill published from anthropics/knowledge-work-plugins, installable through the skills CLI.
SKILL.md
| 1 | # Source Management |
| 2 | |
| 3 | > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). |
| 4 | |
| 5 | Knows what sources are available, helps connect new ones, and manages how sources are queried. |
| 6 | |
| 7 | ## Checking Available Sources |
| 8 | |
| 9 | Determine which MCP sources are connected by checking available tools. Each source corresponds to a set of MCP tools: |
| 10 | |
| 11 | | Source | Key capabilities | |
| 12 | |--------|-----------------| |
| 13 | | **~~chat** | Search messages, read channels and threads | |
| 14 | | **~~email** | Search messages, read individual emails | |
| 15 | | **~~cloud storage** | Search files, fetch document contents | |
| 16 | | **~~project tracker** | Search tasks, typeahead search | |
| 17 | | **~~CRM** | Query records (accounts, contacts, opportunities) | |
| 18 | | **~~knowledge base** | Semantic search, keyword search | |
| 19 | |
| 20 | If a tool prefix is available, the source is connected and searchable. |
| 21 | |
| 22 | ## Guiding Users to Connect Sources |
| 23 | |
| 24 | When a user searches but has few or no sources connected: |
| 25 | |
| 26 | ``` |
| 27 | You currently have [N] source(s) connected: [list]. |
| 28 | |
| 29 | To expand your search, you can connect additional sources in your MCP settings: |
| 30 | - ~~chat — messages, threads, channels |
| 31 | - ~~email — emails, conversations, attachments |
| 32 | - ~~cloud storage — docs, sheets, slides |
| 33 | - ~~project tracker — tasks, projects, milestones |
| 34 | - ~~CRM — accounts, contacts, opportunities |
| 35 | - ~~knowledge base — wiki pages, knowledge base articles |
| 36 | |
| 37 | The more sources you connect, the more complete your search results. |
| 38 | ``` |
| 39 | |
| 40 | When a user asks about a specific tool that is not connected: |
| 41 | |
| 42 | ``` |
| 43 | [Tool name] isn't currently connected. To add it: |
| 44 | 1. Open your MCP settings |
| 45 | 2. Add the [tool] MCP server configuration |
| 46 | 3. Authenticate when prompted |
| 47 | |
| 48 | Once connected, it will be automatically included in future searches. |
| 49 | ``` |
| 50 | |
| 51 | ## Source Priority Ordering |
| 52 | |
| 53 | Different query types benefit from searching certain sources first. Use these priorities to weight results, not to skip sources: |
| 54 | |
| 55 | ### By Query Type |
| 56 | |
| 57 | **Decision queries** ("What did we decide..."): |
| 58 | ``` |
| 59 | 1. ~~chat (conversations where decisions happen) |
| 60 | 2. ~~email (decision confirmations, announcements) |
| 61 | 3. ~~cloud storage (meeting notes, decision logs) |
| 62 | 4. Wiki (if decisions are documented) |
| 63 | 5. Task tracker (if decisions are captured in tasks) |
| 64 | ``` |
| 65 | |
| 66 | **Status queries** ("What's the status of..."): |
| 67 | ``` |
| 68 | 1. Task tracker (~~project tracker — authoritative status) |
| 69 | 2. ~~chat (real-time discussion) |
| 70 | 3. ~~cloud storage (status docs, reports) |
| 71 | 4. ~~email (status update emails) |
| 72 | 5. Wiki (project pages) |
| 73 | ``` |
| 74 | |
| 75 | **Document queries** ("Where's the doc for..."): |
| 76 | ``` |
| 77 | 1. ~~cloud storage (primary doc storage) |
| 78 | 2. Wiki / ~~knowledge base (knowledge base) |
| 79 | 3. ~~email (docs shared via email) |
| 80 | 4. ~~chat (docs shared in channels) |
| 81 | 5. Task tracker (docs linked to tasks) |
| 82 | ``` |
| 83 | |
| 84 | **People queries** ("Who works on..." / "Who knows about..."): |
| 85 | ``` |
| 86 | 1. ~~chat (message authors, channel members) |
| 87 | 2. Task tracker (task assignees) |
| 88 | 3. ~~cloud storage (doc authors, collaborators) |
| 89 | 4. ~~CRM (account owners, contacts) |
| 90 | 5. ~~email (email participants) |
| 91 | ``` |
| 92 | |
| 93 | **Factual/Policy queries** ("What's our policy on..."): |
| 94 | ``` |
| 95 | 1. Wiki / ~~knowledge base (official documentation) |
| 96 | 2. ~~cloud storage (policy docs, handbooks) |
| 97 | 3. ~~email (policy announcements) |
| 98 | 4. ~~chat (policy discussions) |
| 99 | ``` |
| 100 | |
| 101 | ### Default Priority (General Queries) |
| 102 | |
| 103 | When query type is unclear: |
| 104 | ``` |
| 105 | 1. ~~chat (highest volume, most real-time) |
| 106 | 2. ~~email (formal communications) |
| 107 | 3. ~~cloud storage (documents and files) |
| 108 | 4. Wiki / ~~knowledge base (structured knowledge) |
| 109 | 5. Task tracker (work items) |
| 110 | 6. CRM (customer data) |
| 111 | ``` |
| 112 | |
| 113 | ## Rate Limiting Awareness |
| 114 | |
| 115 | MCP sources may have rate limits. Handle them gracefully: |
| 116 | |
| 117 | ### Detection |
| 118 | |
| 119 | Rate limit responses typically appear as: |
| 120 | - HTTP 429 responses |
| 121 | - Error messages mentioning "rate limit", "too many requests", or "quota exceeded" |
| 122 | - Throttled or delayed responses |
| 123 | |
| 124 | ### Handling |
| 125 | |
| 126 | When a source is rate limited: |
| 127 | |
| 128 | 1. **Do not retry immediately** — respect the limit |
| 129 | 2. **Continue with other sources** — do not block the entire search |
| 130 | 3. **Inform the user**: |
| 131 | ``` |
| 132 | Note: [Source] is temporarily rate limited. Results below are from |
| 133 | [other sources]. You can retry in a few minutes to include [source]. |
| 134 | ``` |
| 135 | 4. **For digests** — if rate limited mid-scan, note which time range was covered before the limit hit |
| 136 | |
| 137 | ### Prevention |
| 138 | |
| 139 | - Avoid unnecessary API calls — check if the source is likely to have relevant results before querying |
| 140 | - Use targeted queries over broad scans when possible |
| 141 | - For digests, batch requests where the API supports it |
| 142 | - Cache awareness: if a search was just run, avoid re-running the same query immediately |
| 143 | |
| 144 | ## Source Health |
| 145 | |
| 146 | Track source availability during a session: |
| 147 | |
| 148 | ``` |
| 149 | Source Status: |
| 150 | ~~chat: ✓ Available |
| 151 | ~~email: ✓ Available |
| 152 | ~~cloud storage: ✓ Available |
People who liked this also viewed
6 picksType
- lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026
- lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026
- lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。 当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026
- lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026
- lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026
- lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026
