GodModeAI2025

Knowledge Distiller — AI skill for Claude Code

AI community

AI agent skill that distills documents into temporally-aware structured knowledge graphs.

How to install Knowledge Distiller

This entry records only its repository, not the path inside it, so there is no exact command to give. Open GodModeAI2025/knowledge-distiller and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Knowledge Distiller does

AI agent skill that distills documents into temporally-aware structured knowledge graphs. Dual output: .knowledge.md + .knowledge.json

Alternatives in AI

Part 4 — Generate AGENTS.md And AI Agent Configuration Files — I'll help you create the instruction files that will guide your AI coding assistant to build your MVP 2.1k ★
Llmwiki — Open Source Implementation of Karpathy's LLM Wiki 1.5k ★
Launch An AI Feature — Workflow recipe — take an AI/LLM feature from a probabilistic-aware PRD to a launch-ready model card by chaini 1.3k ★

README

Knowledge Distiller v4.0

Extract knowledge, not text — and keep the evidence attached.

Knowledge Distiller is a local, file-based knowledge-graph toolchain and compiler contract. Its canonical `.knowledge.json` graph separates concepts, claims, relationships, facts, source evidence, time, spatial roles and derivations. Deterministic tools validate, merge and render that graph without requiring a daemon or database and without outbound network access or telemetry. An authenticated loopback API is an optional facade, not a runtime prerequisite.

The repository currently implements bounded source normalization and deterministic post-compilation validation, merge, evaluation, rendering and run receipts. It does **not** contain a Segment-to-Graph semantic compiler: an external agent/compiler must author the evidence-linked graph first. The extractor and post-compilation runner are separate tools; there is no automatic end-to-end handoff and the runner neither invokes a model nor applies a compiler profile.

Spec 1.1 is an additive trust layer: existing Spec 1.0 files remain valid.

Why this version is different

Weak shortcut	Implemented contract
Plausible statement with a source name	Reusable evidence with an exact selector/locator
One opaque “quality” number	`conformance_score` plus scoped golden evaluation; semantic truth is never implied
“The AI reasoned that …”	Explicit origin, evidence, short derivation summary and review status; no chain-of-thought storage
A place string with unclear meaning	Role-qualified spatial context such as jurisdiction, market or mentioned location
Conflicting value overwritten	Both facts retained and linked through an explicit conflict
Count-only merge guard	Identity- and payload-aware merge with exact prior archive plus mandatory JSON and Markdown diffs
CDN-backed viewer	One dependency-free offline HTML file with an interactive SVG graph
IDs interpolated into paths	Pre