By JayJiangCT
Knowlery: the knowledge base your agents can live in — query, capture, and maintain plain-markdown knowledge bases by conversation.
Open-ended Q&A against the knowledge base. Locates candidate pages with one call to the deterministic retrieval script (.knowlery/bin/query.mjs), then reads the promising ones with Obsidian CLI and synthesizes an evidence-based answer with citations. Use when the user asks questions about vault content like "what is X", "why did we decide Y", "explain Z", "what do my notes say about", "summarize what I know about", or any question that should be answered from accumulated knowledge rather than general training data.
Scan agent-maintained directories for health issues: orphan pages, broken wikilinks, stale content, frontmatter violations, tag taxonomy drift, oversized pages. Use this skill whenever the user wants to audit knowledge base quality, check for broken links, find stale or orphan pages, or says anything like "check my wiki", "are there any issues", "audit the knowledge base", "find broken links", or "what needs fixing".
Pressure-tests beliefs against vault evidence. Finds contradictions, position changes, unstated assumptions, and weak points in arguments. Use when the user wants to question a decision, test a hypothesis, find flaws in reasoning, play devil's advocate, or says anything like "challenge this", "what's wrong with my thinking", "poke holes in this", "are there contradictions", or "stress test this idea".
The core knowledge compilation skill. Reads raw notes and external sources, then distills them into structured, cross-referenced knowledge pages in entities/, concepts/, comparisons/, and queries/. Keeps SCHEMA.md tag and domain taxonomy in sync when new tags or domains appear. Use this skill whenever the user mentions compiling notes, digesting material, updating the knowledge base, running a cook cycle, or says anything like "process my notes", "compile this", "add this to the wiki", "what's new in my notes", or "update knowledge pages". Also activate when the user pastes external content and wants it integrated into the knowledge base.
Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Executables (bin/) — files in this plugin's bin/directory are added to the Bash tool's PATH while the plugin is enabled.
The knowledge base your agents can live in.
A local-first knowledge system for people and agents.
Plain Markdown in. Traceable knowledge out.
One plain-markdown workspace, served by three shells: an MCP server and CLI for Codex, Claude, Cursor, and Antigravity — and an Obsidian plugin as its richest human interface. Obsidian maximizes Knowlery; nothing about it requires Obsidian.
Your free-form notes stay yours. Agents get a structured, retrievable layer —
entities/, concepts/, comparisons/, queries/ — compiled from your
material through a reviewed pipeline, plus the skills and conduct that make
them good collaborators. Retrieval is deterministic and measured, answers
carry citations, and "no confident match" is an honest verdict instead of
noise. The workspace format, CLI surface, and MCP contracts are frozen under
semver and pinned by contract tests.
Read the official documentation: https://jayjiangct.github.io/knowlery/.
Install the agent plugin — MCP server plus all fifteen skills in one action:
Claude Code: /plugin marketplace add JayJiangCT/knowlery
/plugin install knowlery
Codex: codex plugin marketplace add <source>
codex plugin add knowlery@<marketplace>
Or add one MCP config block to any client (Cursor, Claude Desktop, Antigravity, …):
{ "command": "npx", "args": ["-y", "knowlery@^1", "mcp"] }
Then everything is conversation: "set up a knowledge base called main", "remember this", "what do I know about X?", "give my KB a checkup". Per-client setup: Connect Your Agent · usage by conversation: Talk to Your Knowledge Base.
Install Knowlery from Obsidian's community plugin directory (Settings → Community plugins → Browse) and run the setup wizard. You get the action-first dashboard, Knowledge health, and the bundle sharing UI — and the vault registers itself so every agent can address it by name. Full walkthrough: Start in Obsidian.
Either way it's the same plain folder: a KB born in a conversation opens in Obsidian with zero migration, and an Obsidian vault is automatically available to your agents.
Knowlery's identity is the Atlas Fold system — a K-shaped route connecting source, structure, and retrieval, drawn in graphite and paper with a single Knowledge Lime signal. The metaphor is deliberate: a map you can trust, not a mind you have to believe.
| Position | Local-first knowledge infrastructure — your notes remain plain Markdown; Knowlery adds structure, retrieval, and agent access without taking ownership of the source. |
| Character | Exact, calm, and quietly alive — technical enough to earn developer trust, warm enough to feel like a place where knowledge accumulates. |
| Difference | Structure over spectacle — no chatbot face, neural cloud, or AI glow. The visual language is navigation through a maintained body of knowledge. |
The full brand system — logo construction, palette, typography, voice, and
usage rules — lives in design/brand/ (open
brand-guide.html in a browser). Marks,
lockups, and the app icon are under
design/brand/assets/.
In LLM Wiki, Andrej Karpathy describes a pattern different from one-off RAG: instead of re-deriving answers from raw notes on every question, an agent incrementally builds and maintains a persistent wiki—structured, interlinked markdown that sits between you and your sources. New material is read, distilled, and folded into entity pages, topic summaries, and cross-links; the base is kept current rather than re-scanned from scratch each time.
npx claudepluginhub jayjiangct/knowlery --plugin knowleryBuild and maintain a portable knowledge base as an Open Knowledge Format (OKF) bundle. The kb hub plus kb-* action skills.
Long-term memory for Claude Code powered by Memex. Provides persistent knowledge capture, retrieval, and memory-augmented workflows across all projects.
LLM-powered personal wiki — autonomous knowledge base with research-on-miss, ingestion, search, a browsable web UI, and universal data gravity. Saves and retrieves knowledge automatically whenever relevant.
Persistent, compounding knowledge base maintained by LLMs in Obsidian — agent-first edition. Four task-oriented agents (Researcher / Advisor / Curator / Scribe) with citations, confidence, supersession, and rolling session cache. Inspired by Karpathy's LLM Wiki pattern.
Build and maintain LLM-powered knowledge bases as Obsidian wikis with compile, query, lint, and evolve workflows
Plugin-first second brain package for AI agents and humans.