Who it is forAny employee who knows an answer exists somewhere in the company but cannot tell which tool holds it.
The problemInformation is scattered across email, chat, docs, and wikis, and checking each one by hand is slow.
The outcomeOne search across connected tools that returns results from all of them in a single answer.
What you need first
- Access to Claude Cowork or Claude Code
- Accounts for the tools you want to connect, such as your CRM, warehouse, or ticketing system
- Credentials for each connector you enable
Steps
- Run
claude plugin marketplace add anthropics/knowledge-work-plugins - Run
claude plugin install enterprise-search@knowledge-work-plugins(inferred, check the README) - Connect the tools you use, such as Slack, Notion, Guru, or Microsoft 365
- Ask Claude a question in plain language that spans those tools
Prompt for your agent
Using the anthropics/knowledge-work-plugins repo, install the enterprise-search plugin and search for <topic> across connected tools. Expected output: an answer that cites which tool each piece came from. Verify that at least one cited source opens and matches the answer.
Caveat. Search results are only as complete as the connectors you enable, so content in tools you have not connected will not appear.
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page