[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P1MS1F23F75T4FTKTWCPT":3,"skill-same:01M71P1MS1F23F75T4FTKTWCPT":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M71P1MS1F23F75T4FTKTWCPT","source-management",null,"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.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsource-management\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsource-management\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"source","management","source management","plugins","https","github","rate limiting","work","users","guides","connect","MCP","new","knowledge","awareness","Enterprise","search","enterprise search","for","sources","2026-11-10 10:56:23",false,"---\nname: source-management\ndescription: \"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.\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"enterprise-search\u002Fskills\u002Fsource-management\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\n---\n# Source Management\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nKnows what sources are available, helps connect new ones, and manages how sources are queried.\n\n## Checking Available Sources\n\nDetermine which MCP sources are connected by checking available tools. Each source corresponds to a set of MCP tools:\n\n| Source | Key capabilities |\n|--------|-----------------|\n| **~~chat** | Search messages, read channels and threads |\n| **~~email** | Search messages, read individual emails |\n| **~~cloud storage** | Search files, fetch document contents |\n| **~~project tracker** | Search tasks, typeahead search |\n| **~~CRM** | Query records (accounts, contacts, opportunities) |\n| **~~knowledge base** | Semantic search, keyword search |\n\nIf a tool prefix is available, the source is connected and searchable.\n\n## Guiding Users to Connect Sources\n\nWhen a user searches but has few or no sources connected:\n\n```\nYou currently have [N] source(s) connected: [list].\n\nTo expand your search, you can connect additional sources in your MCP settings:\n- ~~chat — messages, threads, channels\n- ~~email — emails, conversations, attachments\n- ~~cloud storage — docs, sheets, slides\n- ~~project tracker — tasks, projects, milestones\n- ~~CRM — accounts, contacts, opportunities\n- ~~knowledge base — wiki pages, knowledge base articles\n\nThe more sources you connect, the more complete your search results.\n```\n\nWhen a user asks about a specific tool that is not connected:\n\n```\n[Tool name] isn't currently connected. To add it:\n1. Open your MCP settings\n2. Add the [tool] MCP server configuration\n3. Authenticate when prompted\n\nOnce connected, it will be automatically included in future searches.\n```\n\n## Source Priority Ordering\n\nDifferent query types benefit from searching certain sources first. Use these priorities to weight results, not to skip sources:\n\n### By Query Type\n\n**Decision queries** (\"What did we decide...\"):\n```\n1. ~~chat (conversations where decisions happen)\n2. ~~email (decision confirmations, announcements)\n3. ~~cloud storage (meeting notes, decision logs)\n4. Wiki (if decisions are documented)\n5. Task tracker (if decisions are captured in tasks)\n```\n\n**Status queries** (\"What's the status of...\"):\n```\n1. Task tracker (~~project tracker — authoritative status)\n2. ~~chat (real-time discussion)\n3. ~~cloud storage (status docs, reports)\n4. ~~email (status update emails)\n5. Wiki (project pages)\n```\n\n**Document queries** (\"Where's the doc for...\"):\n```\n1. ~~cloud storage (primary doc storage)\n2. Wiki \u002F ~~knowledge base (knowledge base)\n3. ~~email (docs shared via email)\n4. ~~chat (docs shared in channels)\n5. Task tracker (docs linked to tasks)\n```\n\n**People queries** (\"Who works on...\" \u002F \"Who knows about...\"):\n```\n1. ~~chat (message authors, channel members)\n2. Task tracker (task assignees)\n3. ~~cloud storage (doc authors, collaborators)\n4. ~~CRM (account owners, contacts)\n5. ~~email (email participants)\n```\n\n**Factual\u002FPolicy queries** (\"What's our policy on...\"):\n```\n1. Wiki \u002F ~~knowledge base (official documentation)\n2. ~~cloud storage (policy docs, handbooks)\n3. ~~email (policy announcements)\n4. ~~chat (policy discussions)\n```\n\n### Default Priority (General Queries)\n\nWhen query type is unclear:\n```\n1. ~~chat (highest volume, most real-time)\n2. ~~email (formal communications)\n3. ~~cloud storage (documents and files)\n4. Wiki \u002F ~~knowledge base (structured knowledge)\n5. Task tracker (work items)\n6. CRM (customer data)\n```\n\n## Rate Limiting Awareness\n\nMCP sources may have rate limits. Handle them gracefully:\n\n### Detection\n\nRate limit responses typically appear as:\n- HTTP 429 responses\n- Error messages mentioning \"rate limit\", \"too many requests\", or \"quota exceeded\"\n- Throttled or delayed responses\n\n### Handling\n\nWhen a source is rate limited:\n\n1. **Do not retry immediately** — respect the limit\n2. **Continue with other sources** — do not block the entire search\n3. **Inform the user**:\n```\nNote: [Source] is temporarily rate limited. Results below are from\n[other sources]. You can retry in a few minutes to include [source].\n```\n4. **For digests** — if rate limited mid-scan, note which time range was covered before the limit hit\n\n### Prevention\n\n- Avoid unnecessary API calls — check if the source is likely to have relevant results before querying\n- Use targeted queries over broad scans when possible\n- For digests, batch requests where the API supports it\n- Cache awareness: if a search was just run, avoid re-running the same query immediately\n\n## Source Health\n\nTrack source availability during a session:\n\n```\nSource Status:\n  ~~chat:        ✓ Available\n  ~~email:        ✓ Available\n  ~~cloud storage:  ✓ Available\n  ~~project tracker:        ✗ Not connected\n  ~~CRM:   ✗ Not connected\n  ~~knowledge base:      ⚠ Rate limited (retry in 2 min)\n```\n\nWhen reporting search results, include which sources were searched so the user knows the scope of the answer.\n\n## Adding Custom Sources\n\nThe 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.\n\nTo add a new source:\n1. Add the MCP server configuration to `.mcp.json`\n2. Authenticate if required\n3. The source will be included in subsequent searches automatically\n","# Source Management\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nKnows what sources are available, helps connect new ones, and manages how sources are queried.\n\n## Checking Available Sources\n\nDetermine which MCP sources are connected by checking available tools. Each source corresponds to a set of MCP tools:\n\n| Source | Key capabilities |\n|--------|-----------------|\n| **~~chat** | Search messages, read channels and threads |\n| **~~email** | Search messages, read individual emails |\n| **~~cloud storage** | Search files, fetch document contents |\n| **~~project tracker** | Search tasks, typeahead search |\n| **~~CRM** | Query records (accounts, contacts, opportunities) |\n| **~~knowledge base** | Semantic search, keyword search |\n\nIf a tool prefix is available, the source is connected and searchable.\n\n## Guiding Users to Connect Sources\n\nWhen a user searches but has few or no sources connected:\n\n```\nYou currently have [N] source(s) connected: [list].\n\nTo expand your search, you can connect additional sources in your MCP settings:\n- ~~chat — messages, threads, channels\n- ~~email — emails, conversations, attachments\n- ~~cloud storage — docs, sheets, slides\n- ~~project tracker — tasks, projects, milestones\n- ~~CRM — accounts, contacts, opportunities\n- ~~knowledge base — wiki pages, knowledge base articles\n\nThe more sources you connect, the more complete your search results.\n```\n\nWhen a user asks about a specific tool that is not connected:\n\n```\n[Tool name] isn't currently connected. To add it:\n1. Open your MCP settings\n2. Add the [tool] MCP server configuration\n3. Authenticate when prompted\n\nOnce connected, it will be automatically included in future searches.\n```\n\n## Source Priority Ordering\n\nDifferent query types benefit from searching certain sources first. Use these priorities to weight results, not to skip sources:\n\n### By Query Type\n\n**Decision queries** (\"What did we decide...\"):\n```\n1. ~~chat (conversations where decisions happen)\n2. ~~email (decision confirmations, announcements)\n3. ~~cloud storage (meeting notes, decision logs)\n4. Wiki (if decisions are documented)\n5. Task tracker (if decisions are captured in tasks)\n```\n\n**Status queries** (\"What's the status of...\"):\n```\n1. Task tracker (~~project tracker — authoritative status)\n2. ~~chat (real-time discussion)\n3. ~~cloud storage (status docs, reports)\n4. ~~email (status update emails)\n5. Wiki (project pages)\n```\n\n**Document queries** (\"Where's the doc for...\"):\n```\n1. ~~cloud storage (primary doc storage)\n2. Wiki \u002F ~~knowledge base (knowledge base)\n3. ~~email (docs shared via email)\n4. ~~chat (docs shared in channels)\n5. Task tracker (docs linked to tasks)\n```\n\n**People queries** (\"Who works on...\" \u002F \"Who knows about...\"):\n```\n1. ~~chat (message authors, channel members)\n2. Task tracker (task assignees)\n3. ~~cloud storage (doc authors, collaborators)\n4. ~~CRM (account owners, contacts)\n5. ~~email (email participants)\n```\n\n**Factual\u002FPolicy queries** (\"What's our policy on...\"):\n```\n1. Wiki \u002F ~~knowledge base (official documentation)\n2. ~~cloud storage (policy docs, handbooks)\n3. ~~email (policy announcements)\n4. ~~chat (policy discussions)\n```\n\n### Default Priority (General Queries)\n\nWhen query type is unclear:\n```\n1. ~~chat (highest volume, most real-time)\n2. ~~email (formal communications)\n3. ~~cloud storage (documents and files)\n4. Wiki \u002F ~~knowledge base (structured knowledge)\n5. Task tracker (work items)\n6. CRM (customer data)\n```\n\n## Rate Limiting Awareness\n\nMCP sources may have rate limits. Handle them gracefully:\n\n### Detection\n\nRate limit responses typically appear as:\n- HTTP 429 responses\n- Error messages mentioning \"rate limit\", \"too many requests\", or \"quota exceeded\"\n- Throttled or delayed responses\n\n### Handling\n\nWhen a source is rate limited:\n\n1. **Do not retry immediately** — respect the limit\n2. **Continue with other sources** — do not block the entire search\n3. **Inform the user**:\n```\nNote: [Source] is temporarily rate limited. Results below are from\n[other sources]. You can retry in a few minutes to include [source].\n```\n4. **For digests** — if rate limited mid-scan, note which time range was covered before the limit hit\n\n### Prevention\n\n- Avoid unnecessary API calls — check if the source is likely to have relevant results before querying\n- Use targeted queries over broad scans when possible\n- For digests, batch requests where the API supports it\n- Cache awareness: if a search was just run, avoid re-running the same query immediately\n\n## Source Health\n\nTrack source availability during a session:\n\n```\nSource Status:\n  ~~chat:        ✓ Available\n  ~~email:        ✓ Available\n  ~~cloud storage:  ✓ Available\n  ~~project tracker:        ✗ Not connected\n  ~~CRM:   ✗ Not connected\n  ~~knowledge base:      ⚠ Rate limited (retry in 2 min)\n```\n\nWhen reporting search results, include which sources were searched so the user knows the scope of the answer.\n\n## Adding Custom Sources\n\nThe 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.\n\nTo add a new source:\n1. Add the MCP server configuration to `.mcp.json`\n2. Authenticate if required\n3. The source will be included in subsequent searches automatically\n",{"name":5,"tags":49,"tools":50,"source":51,"license":14,"description":7,"source_path":52,"source_commit":53},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","enterprise-search\u002Fskills\u002Fsource-management","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsource-management",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add monoes\u002Fmonomind --skill source-management",{"tool":69,"command":70},"bunx","bunx skills add monoes\u002Fmonomind --skill source-management",{"tool":72,"command":73},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill source-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsource-management\u002FSKILL.md",true,[77],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,[83,110,145,171,192,217],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":109},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[90,91,92,93,94,95,96,37,97,98,99,100,101,102,103,104,105,106,107,108],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":126,"publishedAt":109},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[118,121],{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[127,128,129,94,130,131,132,133,98,134,135,136,137,138,139,140,141,142,143,144],"writing","writing plans","plans","superpowers","implementation plan","when","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":109},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000031","产品经理",[138,156,157,158,159,37,160,132,161,162,31,137,163,164,165,166,167,168,169,170],"write spec","spec","user request","problem","acceptance","ask","vague","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":175,"sourceHtmlUrl":176,"categories":177,"keywords":181,"publishedAt":109},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[178],{"categoryNo":179,"categoryName":180,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000033","数据分析师",[98,138,182,183,42,184,37,169,132,185,186,187,188,31,29,189,28,190,27,191],"write query","postgres","snowflake","best practices","natural-language","with","multi","sql","syntax","data",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":202,"publishedAt":109},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[198,201],{"categoryNo":199,"categoryName":200,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[203,204,205,206,42,207,208,209,210,97,211,212,213,98,101,29,214,215,216,28],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":224,"publishedAt":109},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[223],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[205,225,226,227,228,229,230,42,231,232,134,233,234,235,101,29,236,237,28,238],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]