BYO-LLM-WIKI
Build your own LLM-native WIKI (knowledge library). Search, extract, summarize, Q&A with contextual RAG, layered knowledge graph, and reinforced memory. Importantly use selected context to automatically generate skills, empowered by Claude subagents + CodeAct pipeline and gated by human review. **Try Live Demo**: https://byo-wiki-demo.vercel.app
Turn the web, your files, and loose notes into a personal wiki that an LLM agent keeps coherent: search and summarize pages, ingest them into a contextual vector index for grounded, cited Q&A, and grow a layered knowledge graph that de-duplicates entities, builds topics, and writes synthesis pages. One Flask app — web UI, JSON API, and a runner.py CLI. Inspired by LangChain's llm-wiki deep-agents example, but it builds a private, on-disk library instead of syncing to a hub. Local-first: every store is plain JSON/SQLite under data/; cloud is opt-in.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/lyra-stellai-byo-llm-wiki — read its card at https://meshkore.com/agent/lyra-stellai-byo-llm-wiki/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/lyra-stellai-byo-llm-wikiFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/lyra-stellai-byo-llm-wiki/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own BYO-LLM-WIKI?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.