A living personal wiki. Wenlan turns your documents, notes, and AI chats into pages with links to their sources, and updates them as sources change without overwriting your edits. Claude Code, Codex and other AI tools can build on it.
This repository also configures its own agents. See what wenlan tells them →
Skill Claude Code
Per-surface verification loops for wenlan — daemon, cli, mcp, plugin, suite strength (mutation), behavior trace, weekly sweep. Routes to scripts; every check records evidence via attest. Deeper than the built-in verify skill — use prove for mutation audits, behavior tracing, and the weekly sweep; built-in /verify…
Skill Claude Code
Build, launch, screenshot, and drive the wenlan-app Tauri desktop app in dev mode on macOS (WKWebView) or Windows (WebView2). Use when asked to run or start the app, verify a UI change in the real running app (not just tests), or take a screenshot of it.
Skill Claude Code needs its repo
Build, launch, and stop the wenlan daemon (wenlan-server) for local dev and verification. Use when asked to run or restart the daemon, or before driving any surface (HTTP, CLI, MCP) against a live instance.
Skill Claude Code
Drive/evidence recipe for verifying wenlan changes at their real surfaces (daemon HTTP, CLI, MCP stdio). The handle file the built-in verify protocol expects; launch primitives live in the run-wenlan skill, deeper machinery (mutation audit, behavior trace, weekly sweep) in the prove skill.
Skill Claude CodeCodex
Read the current Space-owned project Brief from Wenlan. With an optional topic, appends separately labeled related context from the same Space. Invoked as /brief [topic] when resuming work or asking to catch up.
Skill Claude CodeCodex
Save a memory to Wenlan in flow. Active capture verb — use proactively when the user states a preference, makes a decision, corrects you, or shares a durable fact. Invoked as /capture .
Skill Claude CodeCodex
Power-user audit of Wenlan's pending surfaces: accept or dismiss pending revisions (conflicts/merges), or audit pending captures (not yet confirmed). Most users want /brief for revisions; that handles the daily flow. Use /curate only for explicit deep-walk audits after bulk imports, or to walk the full queue rather…
Skill Claude CodeCodex
Synthesize wiki pages from related memories. One endpoint, one flow: daemon clusters and synthesizes what it can; agent finishes whatever the daemon couldn't (no LLM or cluster too big). Invoked as /distill [target].
Skill Claude CodeCodex
Delete a memory from Wenlan by ID. Destructive and cannot be undone — prefer /capture with supersedes for corrections. Invoked as /forget .
Skill Claude CodeCodex
End a work session. Stores durable captures, writes a narrative session log, and automatically applies typed item-level deltas to the current Space Brief. Invoked as /handoff.
Skill Claude CodeCodex
One-screen quick reference for the Wenlan plugin. Lists the daily verbs, the daily flow, where data lives, and how to view it without a GUI. Use when the user says "help", "what can I do", "list wenlan commands", "how do I use wenlan", invokes /help, or explicitly asks about import progress.
Skill Claude CodeCodex
Lint Wenlan memory quality and hygiene, check vocabulary, or resolve every finding into a ready repair, review item, system action, or blocker.
Skill Claude CodeCodex
List or open distilled pages by delegating to the local wenlan pages CLI. /pages opens the page when one matches, or prints the matches when several do. /pages lists recent pages. Invoked as /pages [query].
Skill Claude CodeCodex
Search Wenlan's local memory by query. Targeted lookup, not orientation. Invoked as /recall . Use when the user asks "do you remember", "what do you know about", "look up".
Skill Claude CodeCodex
Frictionless Wenlan setup for Codex. Detects a missing local runtime, installs or repairs it, and verifies the plugin to MCP to local runtime round-trip. Run when the user says "set up wenlan", "is wenlan working", or "fix wenlan".
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: