llm-wiki-orient

LLM-Wiki Orient

Goal

Give the user a clear, non-hype explanation of LLM-Wiki and route them to the next useful skill.

When to use

Use when the user asks:

• "What is LLM-Wiki?"
• "How is this different from RAG?"
• "What tools exist?"
• "Is this useful for my notes/team/repo?"
• "Explain OpenWiki/wiki memory/compiled knowledge."

For objections such as "why do I need this?", "what proof exists?", "what benefits will I get?", "how do I keep it alive?", or "do I need Obsidian?", route to or invoke llm-wiki-faq.

Inputs

• The user's question about LLM-Wiki (what it is, how it differs from RAG/GraphRAG, whether to adopt it).
• Optional context frame: personal second brain, team/company knowledge, repository documentation, research corpus, or product build.
• Optional local-first requirement and sensitivity/privacy level.
• Optional target agent: Claude Code, Codex, Cursor, OpenCode or other.
• Whether the user already has documents to migrate or is starting empty.

Procedure

1. Identify the user's frame

Infer or ask for the minimum needed context:

• personal second brain, team/company knowledge, repository documentation, research corpus, or product build;
• local-first requirement;
• target agent: Claude Code, Codex, Cursor, OpenCode or other;
• existing documents or empty start;
• sensitivity/privacy level.

If the user only wants a general explanation, do not interrogate them.

2. Explain the pattern

Use this mental model:

raw/     immutable source material
wiki/    LLM-compiled, human-readable Markdown knowledge layer
schema/  AGENTS.md, CLAUDE.md, skills, schemas and conventions

Emphasize:

• LLM-Wiki is a compiled knowledge layer, not just a note app.
• Raw sources stay preserved.
• The wiki is reviewable Markdown.
• Skills define procedures over the wiki.
• index.md and log.md make the wiki navigable and auditable.
• Evidence and adoption questions should be answered with direct/adjacent/local evidence levels, not hype.