Catalog
Yeachan-Heo/wiki

Yeachan-Heo

wiki

LLM Wiki — persistent markdown knowledge base that compounds across sessions (Karpathy model)

global
New~522
v1.1Saved May 11, 2026

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.

Categories

Pages are organized by category: architecture, decision, pattern, debugging, environment, session-log

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)
Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

72/100

Grade

B

Good

Safety

82

Quality

68

Clarity

75

Completeness

60

Summary

A persistent markdown-based knowledge base system that allows LLMs to ingest, query, and maintain project-specific documentation across sessions. It uses keyword and tag-based search (no embeddings), stores pages in `.omc/wiki/` with YAML frontmatter, and includes automatic session logging and health checks via lint operations.

Detected Capabilities

file readfile writefile deletelocal filesystem operationsmarkdown parsingtag-based searchYAML frontmatter processingauto-logging to append-only log file

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

wiki addsave knowledgequery wikidocument decisioncapture session

Use Cases

  • Build a persistent knowledge base of architectural decisions across sessions
  • Capture and organize debugging insights and troubleshooting patterns
  • Maintain environment-specific configuration and setup notes
  • Query past session discoveries and cross-reference related topics
  • Lint wiki health to detect stale content and broken cross-references

Quality Notes

  • Clear scoping: operations limited to `.omc/wiki/` directory, which is project-local and git-ignored by default
  • Good boundary documentation: explicitly states 'NO vector embeddings' and 'wiki pages are git-ignored by default' to manage expectations
  • Well-defined API contract with concrete function signatures (wiki_ingest, wiki_query, wiki_lint, etc.)
  • Organized category system (architecture, decision, pattern, debugging, environment, session-log) provides structure for knowledge organization
  • Append-only log design prevents loss of operation history
  • Auto-capture feature is configurable via `.omc-config.json`, giving users control
  • Missing: no error handling documentation (what happens if a page doesn't exist? how does deletion handle dependencies?)
  • Missing: storage format details (YAML frontmatter structure not fully specified) — author needs to define expected field names and types
  • Missing: size constraints or limits on pages/wiki (could grow unbounded)
  • Missing: example output format for query results — unclear how 'snippets' are formatted or what 'citations' means in practice
Model: claude-haiku-4-5-20251001Analyzed: May 11, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

v1.1

Content updated

2026-04-20

Latest
v1.0

No changelog

2026-04-12

Add Yeachan-Heo/wiki to your library

Command Palette

Search for a command to run...