Credentials. Role documents and transcripts are sent to the configured LLM endpoint, so confirm your provider meets your data policy before compiling sensitive material.
Who it is forAn operations or engineering lead whose team loses context every time someone changes roles or leaves.
The problemContext built up by individuals walks out the door with them and new hires spend weeks rebuilding it.
The outcomeA role-oriented wiki of distilled articles that stays with the seat when the person in it changes.
What you need first
- An OpenAI-compatible LLM API key and endpoint (OpenAI, DeepSeek, Ollama, vLLM, Azure OpenAI, etc.)
- Docker, or a Linux amd64/arm64 or macOS arm64 machine for the CLI install
- Your source files, notes, or URLs to compile
Steps
- Collect the role's documents, meeting transcripts and notes into one folder.
- Install KaaS and set your LLM credentials as described in the Quick Start.
- Submit the folder's files through the Submit page or start the service with
kaas serve. - Review the compiled articles in the Wiki page and hand-edit any article that needs correction.
Prompt for your agent
Using the KaaS repo at bybit-exchange/kaas, compile the documents for the <role> seat from <folder> into a wiki. Expected output: Markdown articles for that role that answer the team's common questions. Verify that a sample answer cites an article containing the source facts.
Caveat. The README describes the role-based approach as its own motivation, and output quality depends on the source material and chosen LLM.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for bybit-exchange/kaas and "Keep team knowledge when people change roles"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
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
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer