wiki-serve
Skill50 starsChanged 7 months agoMITView on GitHub
Start the wiki web server — browsable Wikipedia-style UI with live research, split-pane editor, AI assist, and themes. Manual trigger only: /wiki-serve, 'start wiki server', 'browse the wiki'.
- Installs packages
In this repository4 other files it gives its agents.
- wiki-maintainSkill
- wiki-readSkill
- wiki-viewSkill
- wiki-writeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Run the /wiki-serve skill from Claude Code (recommended):
- Very specific: line 42
If dependencies are missing, install manually: pip install -r requirements.txt
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Wiki Serve
Launch a local web server that presents the wiki as a browsable, Wikipedia-style website with live background research, integrated chat, and a split-pane editor with AI assist.
Resolve .wiki/ from plugin install scope. Auto-create if missing.
Arguments
/wiki-serve— start the server (default port 8420)/wiki-serve stop— stop the running server
Startup
The FastAPI web server only runs when explicitly requested. There are two ways to start it:
Skill-Based Launch
- Run the
/wiki-serveskill from Claude Code (recommended):/wiki-serve - The server automatically:
- Installs dependencies if needed
- Handles page indexing, research workers, and file watching
- Opens your browser to localhost:8420
Manual Launch
Dependencies are installed automatically by the plugin's SessionStart hook. To start the server manually from the command line:
python path/to/skills/serve/scripts/server.py --wiki-dir .wiki/ --port 8420Replace path/to with the full path to your LLM-Wiki installation (typically .claude/plugins/llm-wiki).
If dependencies are missing, install manually: pip install -r requirements.txt
Features
- Page rendering — markdown → HTML with wiki-link transformation, red-link detection
- Live research — click any red link to trigger background research (stub-first: summary in 30s, full upgrade async)
- Search — full-text search with autocomplete
- Split-pane editor — markdown + live preview, markdown toolbar, AI assist bar
- Page type templates — concept, brainstorming, idea, memory, status, rules, config, skill, plus custom templates from
.wiki/templates/ - Chat — wiki-aware AI assistant in bottom-right panel
- Research queue — manage, cancel, reorder research tasks
- Knowledge graph — interactive page relationship visualization
- Three themes — light, dark, terminal
- Export — HTML and markdown download
Stop
Kill the server process on port 8420. Either:
/wiki-serve stop- The server auto-stops when the session ends (daemon process)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.