Wiki

Persistent, self-maintained markdown knowledge base for project and session knowledge. Inspired by Karpathy's LLM Wiki concept.

Operations

Ingest

Process knowledge into wiki pages. A single ingest can touch multiple pages.

wiki_ingest({ title: "Auth Architecture", content: "...", tags: ["auth", "architecture"], category: "architecture" })

Query

Search across all wiki pages by keywords and tags. Returns matching pages with snippets — YOU (the LLM) synthesize answers with citations from the results.

wiki_query({ query: "authentication", tags: ["auth"], category: "architecture" })

Lint

Run health checks on the wiki. Detects orphan pages, stale content, broken cross-references, oversized pages, and structural contradictions.

wiki_lint()

Quick Add

Add a single page quickly (simpler than ingest).

wiki_add({ title: "Page Title", content: "...", tags: ["tag1"], category: "decision" })

List / Read / Delete

wiki_list()           # Show all pages (reads index.md)
wiki_read({ page: "auth-architecture" })  # Read specific page
wiki_delete({ page: "outdated-page" })    # Delete a page

Log

View wiki operation history by reading .omc/wiki/log.md.

Storage

Pages: .omc/wiki/*.md (markdown with YAML frontmatter)
Index: .omc/wiki/index.md (auto-maintained catalog)
Log: .omc/wiki/log.md (append-only operation chronicle)

Cross-References

Use [[page-name]] wiki-link syntax to create cross-references between pages.

Auto-Capture

At session end, significant discoveries are automatically captured as session-log pages. Configure via wiki.autoCapture in .omc-config.json (default: enabled).

Hard Constraints

NO vector embeddings — query uses keyword + tag matching only
Wiki pages are git-ignored by default (.omc/wiki/ is project-local)

Model Routing

haiku — quick lookups, lightweight inspection, narrow docs work
sonnet — standard implementation, debugging, and review
opus — architecture, deep analysis, consensus planning, and high-risk review
fable — Claude Fable 5 (above Opus); pass it explicitly on the Task call or pin it per agent with agents.<name>.model
The session model chosen with /model applies to the main loop only. Delegated agents run on their pinned tier unless the Task call passes model explicitly or the agent is overridden via agents.<name>.model. To run delegated work on Fable, use one of those two surfaces; selecting Fable in /model alone does not change delegation.

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

76/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

82

Quality

72

Clarity

78

Completeness

70

Summary

A persistent, session-spanning markdown knowledge base skill that enables LLMs to ingest, query, lint, and maintain project documentation across sessions. Inspired by Karpathy's LLM Wiki concept, it organizes pages by category (architecture, decision, pattern, etc.) using keyword/tag matching and wiki-link cross-references, with auto-capture of session discoveries.

Detected Capabilities

file readfile writefile deletemarkdown parsingYAML frontmatter handlingkeyword searchtag-based filteringcross-reference validation

Trigger Keywords

Phrases that agents use to match this skill to user intent.

maintain knowledge basewiki addwiki querysession notesdocument decisionsarchive discoveries

Use Cases

Build a growing project knowledge base that persists across chat sessions
Document architecture decisions and patterns incrementally
Query and synthesize answers from past session discoveries
Maintain a searchable debugging log organized by category and tags
Cross-reference related pages using wiki-link syntax
Validate wiki health and detect stale or orphaned content

Quality Notes

Well-structured operations with clear API signatures for each action (ingest, query, lint, etc.)
Hard constraints explicitly documented (no vector embeddings, keyword-only search, git-ignored storage)
Storage location clearly specified (.omc/wiki/ convention with auto-maintained index and log)
Category taxonomy well-defined (6 clear categories with distinct purposes)
Model routing guidance provided for cost/capability tradeoffs, though somewhat tangential to core wiki functionality
Cross-reference syntax clearly documented (wiki-link [[page-name]] format)
Configuration point identified (wiki.autoCapture in .omc-config.json), though not fully detailed
Assumes .omc/ directory structure without explicit guardrail documentation or error handling guidance
Auto-capture feature mentioned but not explained in terms of what 'significant' means or how to configure capture behavior
No explicit guidance on handling conflicts, duplicate pages, or validation rules for page titles

Model: claude-haiku-4-5-20251001Analyzed: Sep 9, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

wiki