LLM Wiki tooling is still young, so choose by workflow shape rather than brand. A useful tool should preserve raw sources, write inspectable markdown, keep index and log files current, expose review state, and avoid pretending that every generated claim is already trusted.
Tool categories
| Category | Best fit | Watch for |
|---|---|---|
| Folder plus coding agent | Personal or team wikis where markdown and git are enough. | Weak review gates if root instructions are vague. |
| Desktop knowledge-base app | Users who want local files, UI navigation, and bundled ingest workflows. | Opaque storage or hard-to-export graph state. |
| Compiler or CLI | Repeatable ingest, lint, and CI-friendly updates. | Over-automation before source and review policies exist. |
| Adapter layer | Turning chats, tickets, PDFs, repos, or transcripts into raw sources. | Missing provenance or unsafe private-data handling. |
| Search or graph add-on | Larger corpora where manual index routing is not enough. | Replacing human-readable navigation with an opaque retrieval layer. |
Evaluation checklist
ExportableCan you recover raw files, wiki pages, index, log, and metadata without the tool?
AuditableCan a reviewer trace generated claims back to source locations?
ReviewableCan candidate updates be staged before durable pages change?
PortableCan another agent or model family read the operating contract?
Protocol boundary
A future or private system may expose wiki search, read, or write operations through local tools or protocol surfaces. LlmWikis does not currently claim public MCP server support. Treat protocol integrations as implementation candidates that still need access rules, source policy, review gates, and abuse handling.
Tool maturity ladder
| Maturity | Acceptable claim | Evidence needed |
|---|---|---|
| Manual folder pattern | The wiki can be maintained with files, prompts, and review discipline. | Folder tree, schema, index, log, and worked example. |
| Script-assisted | Deterministic checks can catch structural drift. | Lint scripts, sample output, and known limitations. |
| Compiler or CLI | Ingest, query, or lint can run repeatably under a command surface. | Versioned docs, test fixtures, rollback path, and review staging. |
| Protocol exposed | Agents can access controlled wiki operations through a tool boundary. | Authentication, access control, audit log, abuse handling, and source policy. |
| Public service | Hosted ingest/search/editing exists for outside users. | Legal, privacy, moderation, monitoring, security review, and production evidence. |
Selection matrix
| Question | Good answer | Risky answer |
|---|---|---|
| Where are originals stored? | In a readable raw source layer. | Hidden inside a proprietary cache. |
| How are changes reviewed? | Staged diff, status labels, and log entry. | Silent rewrite after every prompt. |
| How does search route? | Index, links, source metadata, and optional retrieval. | Only opaque semantic similarity. |
| How does it fail? | Explicit unsupported, blocked, stale, or contradicted states. | Confident prose with no machine-readable state. |