ThinkWiki

LLM wiki kit

First committed by wzdavid

Published in wzdavid/ThinkWiki. Publisher page

38 GitHub starsUpdated 2026-07-13

What it is

Install once, talk to your agent. ThinkWiki turns documents and notes into a local Markdown wiki with inbox review, content knowledge graph, and browsable HTML workspace.

— the description by wzdavid

AutoGineer overview, from the brain’s own files

ThinkWiki is an agent-native skill designed to turn scattered information into a structured, durable local workspace. By integrating directly with skills-compatible AI agents, it allows users to manage their knowledge base through natural conversation rather than manual CLI commands. It supports a wide range of input formats, including PDFs, web pages, and various document types, organizing them into a system that features an inbox for review, a local viewer, and an interactive content knowledge graph. The system is built to be local-first, ensuring that Markdown files remain the source of truth, while providing HTML-based interfaces for visualizing relationships between topics, entities, and claims.

How it works

Memory model: LLM wiki

AutoGineer overview, from the brain’s own files

ThinkWiki functions as a skill installed into an AI agent's environment. It uses a set of Python scripts to manage a local directory of Markdown files. The system processes inputs through an inbox workflow, where content is reviewed before being ingested into the wiki. It generates a series of HTML outputs, including a workspace home, an inbox console, a page viewer, and a graph explorer. Users interact with these features by asking their agent to perform tasks like clipping content, building the knowledge graph, or serving the workspace via a local loopback server.

Folders
Folder	Role	Files
.github	agent-config	1
docs	docs	41
scripts	scripts	34
templates	templates	13
tests	tests	1

The agent reads

SKILL.md evidence: README.md

Requirements

Runtimes: Python

API keys (by name): THINKWIKI_EMBED_API_KEY, THINKWIKI_LLM_API_KEY

Set it up

Clone the repository at the commit AutoGineer scanned:

git clone https://github.com/wzdavid/ThinkWiki.git && cd ThinkWiki && git checkout 89f477d7a4095ba2ecf49ef9332e240c6f1208a1

cd ThinkWiki && claude
AutoGineer scanned these files at commit 89f477d.
Not scanned by AutoGineerThe author’s README also describes installing it from a clone of its repository. Read its install section: AutoGineer did not scan that path. https://github.com/wzdavid/ThinkWiki/blob/89f477d7a4095ba2ecf49ef9332e240c6f1208a1/README.md#manual-install-optional
First committed by wzdavid. Published in wzdavid/ThinkWiki. Licence: MIT License.

Usage

AutoGineer overview, from the brain’s own files

Initialize a new local wiki workspace
Clip web pages, files, or text into an inbox for later processing
Ingest reviewed items into the permanent wiki structure
Query the wiki for information with evidence-based responses
Generate and visualize a content knowledge graph
Serve the wiki workspace as a local HTML site for browser-based navigation

“Create a local knowledge base named Research Notes in my workspace.”: The agent initializes a new ThinkWiki workspace structure in the specified directory.
“Clip this article into the inbox: https://example.com/article”: The agent saves the content of the URL into the ThinkWiki inbox for later review.
“What did we already decide about context budgets?”: The agent searches the existing wiki pages and provides an answer supported by evidence from the knowledge base.
“Build the knowledge graph and open the workspace home in my browser.”: The agent generates the graph visualization and starts the local server to display the workspace in the browser.

Documentation by wzdavid

ThinkWiki

Image: Release Image: License Image: Python

ThinkWiki is an agent-native local knowledge base skill. Talk to your agent to turn scattered documents, web pages, notes, and conversations into a durable Markdown workspace — with inbox review, local browsing, and an interactive content knowledge graph you can open in a browser.

Chinese version: README.zh.md

Repository: https://github.com/wzdavid/ThinkWiki

Works With Skills-Compatible Agents

ThinkWiki follows the open Agent Skills format (SKILL.md + bundled scripts). If your agent can install skills and run local commands, it can run ThinkWiki.

You do not need to memorize CLI commands. Install the skill once, then create and manage your wiki entirely through conversation.

Agent / Host	Typical use
Claude Code	Install the repo as a skill, then ask it to build and query your wiki
OpenClaw	Full skill workflow; use `serve` + the built-in browser to open HTML outputs
Trae	Install under `.trae/skills`, then manage the wiki in chat
Hermes Agent	Local skill directory + shell execution
OpenAI Codex / Codex CLI	Skills-compatible coding agents with local file access
Cursor	Agent mode with project skills
Gemini CLI	Skills-compatible CLI agent
GitHub Copilot	Agent / coding workflows in VS Code that support skills
Other skills hosts	Any product that loads `SKILL.md` and can run `python3 scripts/thinkwiki ...` locally

Requirement: a local environment with Python 3. ThinkWiki bootstraps its own runtime on first use. Pure cloud chat without local file or shell access cannot run a local wiki.

Get Started: Install Through Conversation

Point your agent at this repository and ask it to install the skill for you.

Example prompt:

Please install the ThinkWiki skill from https://github.com/wzdavid/ThinkWiki , bootstrap the runtime, and run a health check to confirm everything works on my machine.

The agent will typically clone or copy the skill into your host's skills directory, run bootstrap, and verify capabilities with doctor. You should not need to run those steps yourself unless you prefer manual setup.

After installation, start using it immediately:

Create a local knowledge base named My Wiki in my workspace.

Clip this article into the inbox first: https://example.com/article

Import this PDF into the wiki: /path/to/file.pdf

Answer from my wiki: what did we already decide about context budgets?

Build the knowledge graph and open the workspace home in my browser.

The agent reads SKILL.md, maps your intent to stable ThinkWiki actions, and reports what changed — including paths to Markdown pages and HTML outputs.

Why ThinkWiki

Agent-first: users talk to an agent, not to a long list of commands.
Local-first: Markdown files remain the source of truth on your machine.
HTML-first: inbox, viewer, graph, and governance pages are real browsable workspaces.
Knowledge-first: the graph is a content knowledge graph — topics, concepts, entities, claims, and governance — not just a file-link map.

What It Produces

ThinkWiki generates a workspace that includes:

output/index.html: unified workspace home
output/inbox/index.html: inbox review console
output/viewer/index.html: local page browser
output/graph/index.html: interactive graph explorer
output/graph/report.html: graph governance report
output/graph/entity-merge-review.html: entity merge review page
output/graph/entity-merge-plan.html: entity merge dry-run preview when requested

Preview

Workspace Home (`output/index.html`)

The unified workspace home summarizes recent changes, recommended next actions, inbox backlog, and a graph snapshot so you can decide whether to read, ingest, or explore.

Image: ThinkWiki workspace home preview

Inbox Review (`output/inbox/index.html`)

Review clipped web pages, files, and notes before formal ingest. Items are grouped into ready, review, and weak so you can process the highest-value captures first.

Image: ThinkWiki inbox review preview

Local Viewer (`output/viewer/index.html`)

Browse the entire wiki by page type, confidence, and status. Open any page directly in the viewer without leaving the local HTML workspace.

Image: ThinkWiki local viewer preview

Knowledge Graph (`output/graph/index.html`)

Explore the content knowledge graph interactively. Switch between knowledge, document, and suggested views to inspect semantic relations and candidate edges.

Image: ThinkWiki knowledge graph preview

Graph Governance Report (`output/graph/report.html`)

Inspect graph health signals such as isolated pages, hub stubs, fragile bridges, suggested links, and entity merge candidates before making structural changes.

Image: ThinkWiki graph governance report preview

Everyday Commands (In Plain Language)

Once ThinkWiki is installed, these are the kinds of requests users make most often:

You say	ThinkWiki does
Create a wiki called `Research Notes`	Initializes a local workspace
Clip / save this URL or file to inbox	Captures content for later review
Ingest the ready inbox items	Promotes reviewed captures into wiki pages
What does my wiki say about X?	Evidence-first Q&A from existing pages
Save this answer as a query page	Persists high-value outputs
Show me the knowledge graph	Builds/refreshes graph HTML
Review entity merge candidates	Surfaces alias collisions for manual confirmation
Open the wiki workspace in my browser	Runs `serve` and returns `http://127.0.0.1:8765/index.html`

Core Capabilities

Initialize a local wiki workspace
Clip web pages, files, or pasted text into an inbox for later review
Import Markdown, PDF, DOCX, XLSX, XLS, PPTX, web pages, and plain text
Answer questions from existing wiki pages with evidence-first behavior
Save high-value outputs as query, synthesis, decision, or concept pages
Build a content knowledge graph with knowledge, document, and suggested views
Generate entity governance outputs, including ambiguous alias review and deterministic merge flows
Check runtime health, workspace status, and graph governance state

Content Knowledge Graph

ThinkWiki v1.6.0 builds a schema v2 graph with default_view = knowledge.

The knowledge view can contain:

page-backed nodes such as source, topic, concept, decision, synthesis, query, and entity
claim nodes extracted from structured wiki content
semantic relations such as about, belongs_to, depends_on, asserts, supports, contradicts, and suggests_related_to

This means the graph is not limited to raw file references. It can represent knowledge structure, evidence structure, and entity governance directly.

Browse HTML Outputs

Agent chat UIs usually cannot render ThinkWiki HTML inline. Ask your agent to start the built-in loopback server when you want to inspect inbox, viewer, graph, or governance pages:

Start the ThinkWiki output server and give me the workspace URL.

Or run it yourself:

python3 scripts/thinkwiki serve --root /path/to/my-wiki

By default this serves <wiki-root>/output/ at http://127.0.0.1:8765/. Start from http://127.0.0.1:8765/index.html.

On OpenClaw, after serve is running, the agent can also open the workspace home with:

openclaw browser --browser-profile openclaw open http://127.0.0.1:8765/index.html

On other agents, open the same URL in your system browser, or use whatever browser tool the host provides.

Use serve --print-urls when you only need the URL list without starting the server.

Environment Variables

Remote AI features are disabled by default. Configure only what you need:

Content generation (`crystallize`, `digest`)

Requires all three variables. Any OpenAI-compatible chat completion endpoint works (MiniMax, OpenAI, DeepSeek, local Ollama, etc.).

Variable	Required	Purpose
`THINKWIKI_LLM_API_KEY`	Yes, to enable	API key for the configured LLM provider
`THINKWIKI_LLM_BASE_URL`	Yes, to enable	Chat completions URL, e.g. `https://api.openai.com/v1/chat/completions`
`THINKWIKI_LLM_MODEL`	Yes, to enable	Model name, e.g. `gpt-4o-mini` or `MiniMax-M3`
`THINKWIKI_LLM_TEMPERATURE`	No	Optional temperature override

Without a complete LLM configuration, crystallize and digest use local heuristics only.

Entity embedding (`entity-merge-review`, `graph-report`, `health`)

Enabled when THINKWIKI_EMBED_API_KEY is set. Defaults to SiliconFlow BGE-M3; override the endpoint or model if needed.

Variable	Required	Purpose
`THINKWIKI_EMBED_API_KEY`	Yes, to enable	API key for the embedding provider
`THINKWIKI_EMBED_BASE_URL`	No	Embedding URL(s), comma-separated; default `https://api.siliconflow.cn/v1/embeddings`
`THINKWIKI_EMBED_MODEL`	No	Embedding model; default `BAAI/bge-m3`

Manual Install (Optional)

If you prefer to set up the skill yourself instead of asking an agent:

git clone https://github.com/wzdavid/ThinkWiki ThinkWiki
cd ThinkWiki
python3 scripts/thinkwiki bootstrap
python3 scripts/thinkwiki doctor --repo-root .

Then install the folder into your agent's skills directory according to that host's documentation.

CLI Reference (For Agents And Power Users)

ThinkWiki keeps one stable entry point that agents call under the hood:

python3 scripts/thinkwiki <command> [args]

Common commands: init, clip, ingest, inbox, viewer, graph, graph-report, entity-merge-review, entity-merge-apply, serve, health, status, doctor.

See SKILL.md for the agent behavior contract and intent mapping.

Repository Docs

README.md: concise English project overview
README.zh.md: Chinese overview
SKILL.md: skill behavior contract for agent hosts
CHANGELOG.md: release history

License

MIT

docs/demo-wiki/output/index.html

Shown as plain text.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>ThinkWiki Outputs</title>
  <style>
    :root {
      --bg: #0b1020;
      --panel: #121935;
      --text: #edf2ff;
      --muted: #a8b3cf;
      --border: rgba(255,255,255,0.1);
      --accent: #8ab4ff;
    }
    * { box-sizing: border-box; }
    body {
      margin: 0;
      min-height: 100vh;
      font-family: ui-sans-serif, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
      background: linear-gradient(180deg, #0b1020 0%, #10172f 100%);
      color: var(--text);
      display: grid;
      place-items: center;
      padding: 24px;
    }
    .shell {
      width: min(880px, 100%);
      background: rgba(9, 13, 28, 0.86);
      border: 1px solid var(--border);
      border-radius: 24px;
      padding: 28px;
    }
    h1, p { margin-top: 0; }
    .lead {
      color: var(--muted);
      line-height: 1.6;
      margin-bottom: 20px;
    }
    .hero {
      display: grid;
      gap: 18px;
      margin-bottom: 24px;
    }
    .eyebrow {
      color: var(--accent);
      text-transform: uppercase;
      letter-spacing: 0.08em;
      font-size: 0.82rem;
      margin-bottom: 10px;
    }
    .hero-title {
      display: flex;
      align-items: center;
      justify-content: space-between;
      gap: 16px;
      flex-wrap: wrap;
    }
    .hero-title h1 {
      margin-bottom: 0;
    }
    .meta {
      display: flex;
      gap: 10px;
      flex-wrap: wrap;
    }
    .badge {
      border: 1px solid var(--border);
      border-radius: 999px;
      padding: 6px 12px;
      color: var(--muted);
      font-size: 0.92rem;
      background: rgba(255,255,255,0.03);
    }
    .stats {
      display: grid;
      grid-template-columns: repeat(auto-fit, minmax(120px, 1fr));
      gap: 12px;
    }
    .stat {
      border: 1px solid var(--border);
      background: var(--panel);
      border-radius: 18px;
      padding: 16px;
    }
    .stat strong {
      display: block;
      font-size: 1.45rem;
      margin-bottom: 6px;
    }
    .stat span {
      color: var(--muted);
    }
    .grid {
      display: grid;
      gap: 14px;
    }
    .workspace-grid {
      display: grid;
      gap: 14px;
      grid-template-columns: 1.1fr 0.9fr;
      margin-top: 18px;
    }
    .section-grid {
      display: grid;
      grid-template-columns: repeat(2, minmax(0, 1fr));
      gap: 14px;
      margin-top: 18px;
    }
    .panel {
      border: 1px solid var(--border);
      background: rgba(255,255,255,0.02);
      border-radius: 18px;
      padding: 18px;
    }
    .panel h2 {
      margin: 0 0 8px;
      font-size: 1rem;
    }
    .panel p {
      margin: 0 0 14px;
      color: var(--muted);
      line-height: 1.5;
    }
    .card {
      display: block;
      text-decoration: none;
      color: inherit;
      border: 1px solid var(--border);
      background: var(--panel);
      border-radius: 18px;
      padding: 18px;
    }
    .card:hover {
      border-color: rgba(138,180,255,0.55);
      box-shadow: 0 0 0 1px rgba(138,180,255,0.18);
    }
    .card strong {
      display: block;
      margin-bottom: 6px;
      font-size: 1.05rem;
    }
    .card span {
      display: block;
      color: var(--muted);
      margin-bottom: 10px;
    }
    code {
      color: var(--accent);
      font-family: ui-monospace, SFMono-Regular, Menlo, monospace;
      word-break: break-word;
    }
    .empty {
      border: 1px dashed var(--border);
      border-radius: 18px;
      padding: 18px;
      color: var(--muted);
    }
    .small {
      padding: 14px;
      font-size: 0.95rem;
    }
    .mini-card {
      display: block;
      text-decoration: none;
      color: inherit;
      border: 1px solid var(--border);
      background: rgba(18, 25, 53, 0.85);
      border-radius: 16px;
      padding: 14px;
      margin-bottom: 10px;
    }
    .mini-card:last-child {
      margin-bottom: 0;
    }
    .mini-card:hover {
      border-color: rgba(138,180,255,0.55);
    }
    .mini-card strong {
      display: block;
      margin-bottom: 6px;
    }
    .quality {
      display: inline-block;
      margin-top: 8px;
      border-radius: 999px;
      padding: 4px 8px;
      font-size: 0.82rem;
      text-transform: uppercase;
      letter-spacing: 0.04em;
    }
    .quality-ready {
      background: rgba(47, 163, 91, 0.16);
      color: #8de2a7;
    }
    .quality-review {
      background: rgba(242, 166, 43, 0.16);
      color: #ffd08a;
    }
    .quality-weak {
      background: rgba(214, 77, 77, 0.16);
      color: #ff9f9f;
    }
    .quality-media {
      background: rgba(104, 114, 255, 0.16);
      color: #b9c0ff;
    }
    .mini-card span {
      display: block;
      color: var(--muted);
      line-height: 1.45;
    }
    .mini-meta {
      display: flex;
      justify-content: space-between;
      gap: 12px;
      margin-bottom: 8px;
      color: var(--muted);
      font-size: 0.88rem;
    }
    .mini-type {
      text-transform: uppercase;
      letter-spacing: 0.04em;
      color: var(--accent);
    }
    .guide {
      margin-top: 18px;
      border: 1px solid rgba(138,180,255,0.22);
      background: rgba(138,180,255,0.08);
      border-radius: 18px;
      padding: 16px 18px;
    }
    .guide strong {
      display: block;
      margin-bottom: 8px;
    }
    .guide span {
      color: var(--muted);
      line-height: 1.55;
    }
    .bullet-list {
      margin: 0;
      padding-left: 18px;
      color: var(--muted);
      display: grid;
      gap: 10px;
      line-height: 1.5;
    }
    .bullet-list strong {
      color: var(--text);
    }
    .actions {
      display: grid;
      gap: 10px;
    }
    .action-card {
      display: block;
      text-decoration: none;
      color: inherit;
      border: 1px solid var(--border);
      background: rgba(18, 25, 53, 0.85);
      border-radius: 16px;
      padding: 14px;
    }
    .action-card:hover {
      border-color: rgba(138,180,255,0.55);
    }
    .action-card strong {
      display: block;
      margin: 6px 0;
    }
    .action-card span {
      color: var(--muted);
      line-height: 1.45;
      display: block;
    }
    .action-tag {
      display: inline-block;
      font-size: 0.8rem;
      letter-spacing: 0.04em;
      text-transform: uppercase;
      color: var(--accent);
    }
    .snapshot {
      display: grid;
      gap: 10px;
    }
    .snapshot-copy {
      color: var(--muted);
      line-height: 1.55;
    }
    .snapshot-chip {
      border: 1px solid var(--border);
      border-radius: 14px;
      background: rgba(255,255,255,0.03);
      padding: 12px 14px;
      color: var(--muted);
    }
    .snapshot-chip strong {
      color: var(--text);
    }
    @media (max-width: 720px) {
      .stats {
        grid-template-columns: repeat(2, minmax(0, 1fr));
      }
      .workspace-grid {
        grid-template-columns: 1fr;
      }
      .section-grid {
        grid-template-columns: 1fr;
      }
    }
  </style>
</head>
<body>
  <main class="shell">
    <section class="hero">
      <div class="eyebrow">Knowledge Workspace</div>
      <div class="hero-title">
        <h1>ThinkWiki Demo Wiki</h1>
        <div class="meta">
          <span class="badge">Workspace Home</span>
          <span class="badge">Generated 2026-06-23</span>
        </div>
      </div>
      <p class="lead">This is more than an output index. It is the current workspace home for the wiki, where you can see what changed, what needs attention, and what is still waiting in the inbox before deciding whether to open the viewer or the graph.</p>
      <div class="stats">
        <div class='stat'><strong>4</strong><span>Outputs</span></div>
<div class='stat'><strong>1</strong><span>Inbox</span></div>
<div class='stat'><strong>1</strong><span>Ready</span></div>
<div class='stat'><strong>11</strong><span>Pages</span></div>
<div class='stat'><strong>11</strong><span>Graph Nodes</span></div>
<div class='stat'><strong>41</strong><span>Graph Edges</span></div>
<div class='stat'><strong>0</strong><span>Claims</span></div>
<div class='stat'><strong>0</strong><span>Entities</span></div>
      </div>
    </section>
    <div class="workspace-grid">
      <section class="panel">
        <h2>What Changed</h2>
        <p>This section highlights recently updated and recently generated pages so you can quickly see what changed in the wiki.</p>
        <a class='mini-card' href='viewer/index.html#page=wiki/queries/what-makes-ai-native-team.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>query</span><span>2026-06-19</span></div><strong>What Makes an AI Native Team</strong><span>Saved query summarizing the defining traits of an AI native delivery team.</span></a>
<a class='mini-card' href='viewer/index.html#page=wiki/sources/review-checklist.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>source</span><span>2026-06-19</span></div><strong>Review Checklist</strong><span>A source page explaining how human review, acceptance criteria, and escalation paths fit together.</span></a>
<a class='mini-card' href='viewer/index.html#page=wiki/sources/platform-spec.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>source</span><span>2026-06-19</span></div><strong>Platform Spec</strong><span>A source page describing why execution specs and context must be treated as one delivery system.</span></a>
<a class='mini-card' href='viewer/index.html#page=wiki/topics/model-platform.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>topic</span><span>2026-06-19</span></div><strong>Model Platform</strong><span>Topic page for reusable context, evaluation workflows, and internal tooling.</span></a>
        <div style="height: 12px;"></div>
        <a class='mini-card' href='viewer/index.html#page=wiki/queries/what-makes-ai-native-team.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>query</span><span>2026-06-19</span></div><strong>What Makes an AI Native Team</strong><span>Saved query summarizing the defining traits of an AI native delivery team.</span></a>
<a class='mini-card' href='viewer/index.html#page=wiki/concepts/execution-spec.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>concept</span><span>2026-06-19</span></div><strong>Execution Spec</strong><span>A reusable specification that binds task framing, context, policy, and review expectations together.</span></a>
<a class='mini-card' href='viewer/index.html#page=wiki/decisions/execution-policy.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>decision</span><span>2026-06-19</span></div><strong>Execution Policy</strong><span>Decision page that recommends treating context and execution as first-class platform capabilities.</span></a>
<a class='mini-card' href='viewer/index.html#page=wiki/syntheses/delivery-system.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>synthesis</span><span>2026-06-19</span></div><strong>Delivery System Synthesis</strong><span>Synthesis page summarizing how source, topic, concept, and decision pages reinforce one another.</span></a>
      </section>
      <section class="panel">
        <h2>Next Actions</h2>
        <p>Jump directly into the most valuable next step instead of manually deciding where to look first.</p>
        <div class="actions">
          <a class='action-card' href='inbox/index.html#ready' target='_blank' rel='noopener'><span class='action-tag'>Ingest</span><strong>Prioritize Ready Inbox</strong><span>There are 1 inbox items ready for final review and formal ingest. Start with the Ready section.</span></a>
<a class='action-card' href='inbox/index.html' target='_blank' rel='noopener'><span class='action-tag'>Review</span><strong>Review Inbox Queue</strong><span>There are 1 captured items. Review the latest one before deciding whether to ingest it.</span></a>
<a class='action-card' href='viewer/index.html' target='_blank' rel='noopener'><span class='action-tag'>Read</span><strong>Open Local Viewer</strong><span>Browse the whole wiki by page type, status, and confidence.</span></a>
<a class='action-card' href='graph/index.html' target='_blank' rel='noopener'><span class='action-tag'>Explore</span><strong>Open Knowledge Graph</strong><span>Open the graph to inspect key pages, bridge pages, and suggested links.</span></a>
        </div>
      </section>
    </div>
    <div class="workspace-grid">
      <section class="panel">
        <h2>Needs Attention</h2>
        <p>This section highlights the weakest spots in the current knowledge base, such as isolated pages, weakly connected pages, or pages missing summaries and sources.</p>
        <ul class='bullet-list'><li>There are <strong>1</strong> high-degree thin pages. Improve their summaries and context first.</li></ul>
      </section>
      <section class="panel">
        <h2>Graph Snapshot</h2>
        <p>Read structural graph insights directly from the knowledge graph so the home page can tell you what matters most right now.</p>
        <div class="snapshot">
          <div class='snapshot-copy'>The current key page is AI Native Team. The main pages already have a basic connection structure. There are 1 high-degree thin pages worth strengthening first. There are 8 suggested links ready for review.</div>
<div class='snapshot-chip'>Current key page: <strong>AI Native Team</strong></div>
<div class='snapshot-chip'>Graph Schema v2</div><div class='snapshot-chip'>Default View knowledge</div><div class='snapshot-chip'>Knowledge Nodes 11</div><div class='snapshot-chip'>Claims 0</div><div class='snapshot-chip'>Entities 0</div><div class='snapshot-chip'>Aliased Entities 0</div><div class='snapshot-chip'>Aliases 0</div><div class='snapshot-chip'>Ambiguous Alias Groups 0</div><div class='snapshot-chip'>Ambiguous Entities 0</div><div class='snapshot-chip'>Suggested Edges 8</div>
<div class='snapshot-chip'>Isolated Pages 0</div><div class='snapshot-chip'>Isolated Entities 0</div><div class='snapshot-chip'>Suggested Links 8</div><div class='snapshot-chip'>Ambiguous Alias Groups 0</div><div class='snapshot-chip'>Hub Stubs 1</div><div class='snapshot-chip'>Fragile Bridges 0</div><div class='snapshot-chip'>Isolated Clusters 0</div>
<ul class='bullet-list'><li>Strengthen high-degree thin pages with better summaries, context, and sources.</li><li>Review suggested links and convert strong candidates into explicit page links.</li></ul>
        </div>
      </section>
    </div>
    <div class="section-grid">
      <section class="panel">
        <h2>Featured Pages</h2>
        <p>Surface concept, decision, synthesis, and source pages first so you can spot the most valuable knowledge artifacts quickly.</p>
        <a class='mini-card' href='viewer/index.html#page=wiki/sources/review-checklist.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>source</span><span>2026-06-19</span></div><strong>Review Checklist</strong><span>A source page explaining how human review, acceptance criteria, and escalation paths fit together.</span></a>
<a class='mini-card' href='viewer/index.html#page=wiki/sources/platform-spec.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>source</span><span>2026-06-19</span></div><strong>Platform Spec</strong><span>A source page describing why execution specs and context must be treated as one delivery system.</span></a>
<a class='mini-card' href='viewer/index.html#page=wiki/concepts/execution-spec.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>concept</span><span>2026-06-19</span></div><strong>Execution Spec</strong><span>A reusable specification that binds task framing, context, policy, and review expectations together.</span></a>
<a class='mini-card' href='viewer/index.html#page=wiki/decisions/execution-policy.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>decision</span><span>2026-06-19</span></div><strong>Execution Policy</strong><span>Decision page that recommends treating context and execution as first-class platform capabilities.</span></a>
      </section>
      <section class="panel">
        <h2>Outputs Overview</h2>
        <p>The viewer and graph remain the two most important outputs, but they now live inside one unified workspace view.</p>
        <div class="grid">
          <a class='card' href='inbox/index.html' target='_blank' rel='noopener'><strong>Inbox Review</strong><span>Review inbox items and copy the next ingest commands</span><code>inbox/index.html</code></a>
<a class='card' href='viewer/index.html' target='_blank' rel='noopener'><strong>Local Viewer</strong><span>Browse the entire wiki by page type, confidence, and status</span><code>viewer/index.html</code></a>
<a class='card' href='graph/index.html' target='_blank' rel='noopener'><strong>Knowledge Graph</strong><span>Switch between knowledge, document, and suggested views to inspect content relations and candidate edges</span><code>graph/index.html</code></a>
<a class='card' href='graph/report.html' target='_blank' rel='noopener'><strong>Graph Governance Report</strong><span>Inspect isolated pages, fragile bridges, disconnected clusters, and governance actions</span><code>graph/report.html</code></a>
        </div>
      </section>
      <section class="panel">
        <h2>Inbox Queue</h2>
        <p>This section shows the most recent inbox captures. Open the raw item first for a quick review, then decide whether to run ingest.</p>
        <a class='mini-card' href='../normalized/inbox/2026-06-20-team-retrospective.md' target='_blank' rel='noopener'><div class='mini-meta'><span class='mini-type'>wechat</span><span>2026-06-23 11:26</span></div><strong>Team Retrospective</strong><span>Collect this note in inbox first, then decide whether it should become a source page.</span><span>ThinkWiki Channel · ThinkWiki Team</span><span class='quality quality-ready'>quality: ready</span><span class='quality quality-wait_completed'>capture: wait_completed</span><span class='quality quality-media'>media: localized</span><code>normalized/inbox/2026-06-20-team-retrospective.md</code></a>
      </section>
    </div>
    <div class="guide">
      <strong>Start here</strong>
      <span>Start with `What Changed`, `Needs Attention`, and `Inbox Queue`, then decide whether to open the viewer or the graph. If you just imported or captured new material, rerun viewer and graph to refresh this home page.</span>
    </div>
  </main>
</body>
</html>

98 files · 5 not served here

Advantages

Enables natural language management of a knowledge base without requiring the user to memorize complex CLI commands. evidence: README.md
Maintains Markdown files as the local source of truth, ensuring data portability and ownership. evidence: README.md
Provides a rich, interactive content knowledge graph that maps semantic relations like claims and entities rather than just file links. evidence: README.md

Limitations

Requires a local environment with Python 3 and cannot function in pure cloud-based chat environments without local file or shell access. evidence: README.md
Agent chat UIs typically cannot render the generated HTML interfaces inline, requiring the use of a separate browser or a local loopback server. evidence: README.md

Security

Risk level: No risk found

This brain runs

Agent instructions that run or fetch something (5)

SKILL.md: If the user wants a new workspace, run `init`.
SKILL.md: After `viewer`, `graph`, `inbox`, or `graph-report`, run `serve` when the user wants to browse the results.
SKILL.md: If a long-running `serve` process is not practical in the current session, run `serve --print-urls` and tell the user to start `serve` locally, then open the printed workspace URL.
SKILL.md: After starting `serve`, give the user the workspace home URL first (`http://127.0.0.1:8765/index.html` by default) and, in OpenClaw, offer to open it with `openclaw browser --browser-profile openclaw open <url>`. · uses the network
SKILL.md: If the host cannot keep a long-running process alive, run `serve --print-urls` to show the URLs and ask the user to start `serve` in a local terminal or background job.

Attribution and licence

First committed by

wzdavid

Publisher

Wei Zhang (Community)

Source

wzdavid/ThinkWiki · commit 89f477d

Licence

MIT License (files served here)

ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-12

Contributors

wzdavid

AutoGineer is not affiliated with or endorsed by wzdavid.

Install from source

5 of its files are not served here, so there is no ZIP. wzdavid/ThinkWiki at 89f477d

What it is

How it works

Requirements

Set it up

Usage

Documentation by wzdavid

ThinkWiki

Works With Skills-Compatible Agents

Get Started: Install Through Conversation

Why ThinkWiki

What It Produces

Preview

Workspace Home (output/index.html)

Inbox Review (output/inbox/index.html)

Local Viewer (output/viewer/index.html)

Knowledge Graph (output/graph/index.html)

Graph Governance Report (output/graph/report.html)

Everyday Commands (In Plain Language)

Core Capabilities

Content Knowledge Graph

Browse HTML Outputs

Environment Variables

Content generation (crystallize, digest)

Entity embedding (entity-merge-review, graph-report, health)

Manual Install (Optional)

CLI Reference (For Agents And Power Users)

Repository Docs

License

Advantages

Limitations

Security

This brain runs

Attribution and licence

Install from source

Workspace Home (`output/index.html`)

Inbox Review (`output/inbox/index.html`)

Local Viewer (`output/viewer/index.html`)

Knowledge Graph (`output/graph/index.html`)

Graph Governance Report (`output/graph/report.html`)

Content generation (`crystallize`, `digest`)

Entity embedding (`entity-merge-review`, `graph-report`, `health`)