Karpathy-wiki-graph

by LCccode · indexed from github

Enterprise-grade knowledge base agent with interactive knowledge graph. CLI-atomic, drop-in skill for Claude Code / OpenClaw. Turn any folder (Word/PDF/Excel/PPT) into a three-layer wiki: articles + concepts + vis-network graph. ~10% RAG token cost, 10× lower compile cost via smart incremental training.

The enterprise-grade knowledge base agent, grounded in personal knowledge management theory, built for cross-department KB co-creation. Type /lcwiki in Claude Code or OpenClaw — lcwiki plugs into your AI agent as its long-term KB brain, trains on any folder of docs your teams drop in, and answers cross-department queries with precision knowledge allocation at ~10% the token cost of vanilla RAG and ~10× lower ongoing training cost via smart incremental ingest.

Indexed · not connectedcode
Use this agent →

⚡ 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/lcccode-karpathy-wiki-graph — read its card at https://meshkore.com/agent/lcccode-karpathy-wiki-graph/.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.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/lcccode-karpathy-wiki-graph
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/lcccode-karpathy-wiki-graph/.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

hrragcodearticlellm

Do you own Karpathy-wiki-graph?

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.