DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to file documents into a knowledge base with Claude Code with Knowledge Base Kit

Initialize a workspace for Claude Code and process a document through the local skill.

  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code

Who it is forA developer or writer who already uses Claude Code and wants to keep reading notes and attachments in a Markdown knowledge base.

The problemReference documents pile up in downloads folders, and agents re-read the same long files each session.

The outcomeA Claude Code-ready workspace where a processed document has full.md, summary.md, and its original attachment, plus a catalog agents can read first.

What you need first

  • Python 3.10+
  • Node.js 20+
  • Pandoc 3+
  • An authenticated Claude Code or Codex CLI for model-assisted processing
  • A downloaded or cloned copy of the knowledge-base-kit repository

Steps

  1. git clone https://github.com/Sixian-Li/knowledge-base-kit.git && cd Knowledge Base Kit (inferred, check the README)
  2. python3 -m venv .venv
  3. source .venv/bin/activate
  4. python -m pip install -r requirements.txt
  5. python scripts/init_workspace.py ../my-kb --backend claude (inferred, check the README)
  6. cd ../my-kb then python kb.py check --backend claude (inferred, check the README)

Prompt for your agent

In the knowledge-base-kit repo, initialize a Claude backend workspace at <workspace-path>. Open it in Claude Code and use the local process_docs skill with the Claude backend on inbox/<file-name>. Show the proposed category and changed files and wait for review before filing. Verify that `python kb.py check --backend claude` passes.

Caveat. Model-assisted processing requires an authenticated Claude Code CLI, and text drafting follows that provider's data handling.

Share: 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