gitwtfhub

wtf is open-dossier?

jpaarhuis/open-dossier — explained in plain English

Analysis updated 2026-05-18

2Audience · pm founderComplexity · 2/5LicenseSetup · easy

TL;DR

A Claude skill that builds a persistent, growing knowledge base from documents, tracking facts, inferences, and decisions separately.

Mindmap

mindmap
  root((Open Dossier))
    What it does
      Persistent knowledge base
      Labels facts vs guesses
      Tracks decisions
    Tech stack
      Claude Code
      Claude Skills
      Markdown files
    Use cases
      Ingest documents
      Answer with citations
      Track actions and decisions
    Audience
      PMs and founders
      Consultants
    Setup
      Install as plugin
      Init a dossier
      Ingest sources

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Build a growing knowledge base from meeting notes, transcripts, and documents that Claude can reference later.

REASON 2

Ask questions about accumulated project knowledge and get answers with citations to the original sources.

REASON 3

Track which statements are documented facts, inferences, hypotheses, or settled decisions.

REASON 4

Maintain a living project briefing, action list, and decision log that stays current as new sources are added.

What's in the stack?

Claude CodeClaude SkillsMarkdown

How it stacks up

jpaarhuis/open-dossier0-bingwu-0/live-interpreter010zx00x1/faresnipe
Stars222
LanguagePythonPython
Setup difficultyeasymoderateeasy
Complexity2/52/52/5
Audiencepm foundergeneralgeneral

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 5min

Install as a Claude Code plugin or copy the skill folder into your skills directory.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

Wtf does this do

Open Dossier is a Claude skill for building up a persistent, growing body of knowledge from documents, emails, meeting transcripts, notes, and research over time, instead of starting fresh with each new conversation. Most AI conversations lose all their accumulated understanding once the session ends. Open Dossier is built to do the opposite: every document you feed into it adds to a knowledge structure that stays on disk and keeps growing. You start with an empty dossier, a folder on your computer, and add source documents to it as your work progresses. Each source is preserved exactly as it was given, then converted to a readable format, analyzed for what matters, and connected into a set of wiki style pages that combine knowledge from multiple sources. The dossier also keeps a one page running summary of the current state, a log of what was added and when, plans, a list of actions to take, and a record of decisions that were made. A key idea is that every meaningful statement in the dossier is labeled as one of four types: something taken directly from a source, an interpretation or inference made from it, a hypothesis that still needs confirming, or a settled decision. This makes it possible to tell at a glance what is a documented fact versus a guess, and contradictions between sources are flagged rather than silently ignored. You interact with it through a handful of commands: setting up a new dossier, ingesting a document, asking a question that gets answered using everything the dossier knows so far with citations back to sources, checking the dossier's health for stale or contradictory information, or refreshing the summary page. It can also respond to plain language requests like asking it to process a document or answer a question about what was decided. It installs into Claude Code either as a plugin or by copying a skill folder, and can also be uploaded as a skill to Claude.ai or the desktop app. The project is released under the MIT license.

Yoink these prompts

Prompt 1
Run /open-dossier init to set up a new knowledge dossier in this folder.
Prompt 2
Ingest this meeting transcript into the dossier and update the relevant wiki pages.
Prompt 3
Ask the dossier what was decided about a specific topic, with citations to the sources.
Prompt 4
Run /open-dossier lint to check the dossier for contradictions or stale hypotheses.
Prompt 5
Install open-dossier as a Claude Code plugin using the plugin marketplace command.

Frequently asked questions

wtf is open-dossier?

A Claude skill that builds a persistent, growing knowledge base from documents, tracking facts, inferences, and decisions separately.

What license does open-dossier use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is open-dossier to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is open-dossier for?

Mainly pm founder.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.