Skills
What's different about skills in OpenKnowledge: you edit them in the WYSIWYG editor like any doc, version them as content, and symlink one skill into every editor you use.
A skill in OpenKnowledge is content, not a config file: authored in the WYSIWYG editor, versioned like any doc, and symlinked into every editor from one source.
Edit skills like docs
A project skill is not a raw text file you hand-edit in a dotfile. It is a document in your base: written in the same WYSIWYG editor, versioned, with the same backlinks and live preview as the rest of your knowledge. Improving a skill is the same flow as improving any page.
Write once, install everywhere
install symlinks the skill into each editor's skills directory (Claude Code, Cursor, Codex, OpenCode). Every editor points at the one .ok/skills/<name> source, so nothing is copied and nothing drifts: edit the skill once and every agent has the change, with no re-install.
Two scopes
- Project skills live in the base, versioned and shared with it like any other content. The one every project ships with is what makes an agent behave well the moment you connect it: read and write through the tools, cite sources, keep the link graph healthy.
- Global skills follow you across every project on your machine.
Skills are an open standard, and a skill can carry scripts that run on your machine. Treat a third-party skill like installing software. Use trusted sources, and read what it does first.
Up next
- Agentic search: how the agent reads your base.
- LLM wiki: build a source-grounded knowledge base an agent curates, end to end.