Install
/plugin install open-knowledge@open-knowledge-skillsWho It Suits
If you want an agent to handle a Markdown knowledge base through repeatable steps, and you want to read the skill itself before installing it, this collection is a good fit. The official page says that each skill teaches an agent one repeatable task, and that all of them are pure Markdown that can be opened and read before installation.
The platform skill is called open-knowledge. It teaches an agent to read, search, link, and write Markdown through Open Knowledge's MCP service. The skill directory also mentions .claude/skills/, .cursor/skills/, .codex/skills/ and the neutral .agents/skills/. These are directory names; they do not mean that each environment has a separately documented plugin command.
It is best suited to people who can already work in an environment that supports /plugin and who want to search or read first rather than write immediately. The official explanation is at
https://github.com/inkeep/open-knowledge-skills
First Try in 3 Minutes
Use only this official plugin path, in two steps; do not switch to another installer. First add it:
/plugin marketplace add inkeep/open-knowledge-skills
Then install the platform plugin:
/plugin install open-knowledge@open-knowledge-skills
Prerequisite: the current agent supports these two /plugin commands. The page also says that you can copy the skills into the folders listed above, but that is not the primary path for a first try; do not copy them in parallel the first time.
Make the first task read-only. After installation, ask the agent to read or search existing Markdown; do not have it link new entries or write anything first. Reading and searching are capabilities explicitly named by the platform skill and are also the easiest to verify. Writing changes the knowledge base, so first ask it to list the files it plans to change, then allow it only after you confirm.
Success signals: both /plugin commands are accepted, open-knowledge is available, and the agent can return a summary of Markdown it found or read instead of saying it is not installed. The page does not specify an MCP service address or key setup steps; when those are missing, do not invent a connection string.
Use Cases
Case one: read or search existing Markdown first.
The official page describes open-knowledge as teaching the agent to read and search. For the first attempt, query only: provide a title or keyword and check whether the returned excerpt comes from your knowledge base. The page does not specify search syntax or a result count. What can be confirmed is that these two kinds of actions exist and that the skill text itself can be opened as Markdown before installation.
Case two: inspect link relationships first, then write after confirmation.
The same platform skill also covers link and write. For the first attempt, ask the agent only to explain where a document is already linked, or to preview the paragraph it plans to write. After you confirm the path and content, allow the write. The page does not provide a link-field template or conflict handling; the confirmed scope ends with these two actions being taught by open-knowledge.
Both cases use the same plugin installation path. Every other skill is also described as “one repeatable task,” but the page does not name those tasks.
Usage Boundaries
The primary path is /plugin marketplace add inkeep/open-knowledge-skills followed by /plugin install open-knowledge@open-knowledge-skills. Copying into .claude/skills/, .cursor/skills/, .codex/skills/ or .agents/skills/ is also described as possible, but it is not the first command. Do not apply the plugin commands to an environment where the page only documents copying directories.
open-knowledge depends on Open Knowledge's MCP service. The page does not give the service URL, authentication, or local startup method in the sentences provided. Without the service, reading and searching will stop.
Writing changes Markdown. No permission model or rollback procedure is provided. Being able to read the skill text before installation does not mean that the knowledge base content will be available automatically after installation.