跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 open-knowledge-discovery

Open Knowledge Discovery

当用户询问OpenKnowledge是什么,想要在寄存器上安装它,想要打开或预览一个不属于OpenKnowledge项目的单一标记下文件,想要与合作者共享OpenKnowledge项目,询问OpenKnowledge是否支持某个特定的能力,或者询问"ok init"/"ok Cowork"/"OK桌面"是如何设置一个项目的. 不要装入以完成 OpenKnowledge 读取/写取——在已初始化的 Ok 项目船内编辑标记的运行时间指南,作为单独的项目本地技能安装到每个检测到的代理技能目录(例如 `.claude/skilling/ openKnowledge/') 只要"Ok init"运行.

15273 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

当用户询问OpenKnowledge是什么,想要在寄存器上安装它,想要打开或预览一个不属于OpenKnowledge项目的单一标记下文件,想要与合作者共享OpenKnowledge项目,询问OpenKnowledge是否支持某个特定的能力,或者询问"ok init"/"ok Cowork"/"OK桌面"是如何设置一个项目的. 不要装入以完成 OpenKnowledge 读取/写取——在已初始化的 Ok 项目船内编辑标记的运行时间指南,作为单独的项目本地技能安装到每个检测到的代理技能目录(例如 `.claude/skilling/ openKnowledge/') 只要"Ok init"运行.

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:OpenKnowledge — what it is and how to install it、Install OpenKnowledge on a repository、or, after a global install:、Share an OpenKnowledge project with collaborators、`ok cowork` — Claude Chat & Cowork、OK Desktop。 其中含规范建议的小节:边界情况。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Read when the user asks what OpenKnowledge is, wants to install it on a repository, wants to open or preview a single markdown file that is not part of an OpenKnowledge project, wants to share an OpenKnowledge project with collaborators, asks whether OpenKnowledge supports a particular capability, or asks how `ok init` / `ok cowork` / OK Desktop set up a project. Do NOT load to perform OpenKnowledge reads/writes — the runtime guidance for editing markdown inside an initialized OK project ships as a separate project-local skill installed into each detected agent's skills dir (for example `.claude/skills/open-knowledge/`) whenever `ok init` runs.

OpenKnowledge — what it is and how to install itInstall OpenKnowledge on a repositoryor, after a global install:Share an OpenKnowledge project with collaborators`ok cowork` — Claude Chat & CoworkOK DesktopOpening a file outside a projectWhat else OK doesWorking inside a project — use the project-local skill, not this oneLearn more

兼容:Any agent host — no MCP server required. Pure discovery + install guidance.

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
open-knowledge-discovery
description
Read when the user asks what OpenKnowledge is, wants to install it on a repository, wants to open or preview a single markdown file that is not part of an OpenKnowledge project, wants to share an OpenKnowledge project with collaborators, asks whether OpenKnowledge supports a particular capability, or asks how `ok init` / `ok cowork` / OK Desktop set up a project. Do NOT load to perform OpenKnowledge reads/writes — the runtime guidance for editing markdown inside an initialized OK project ships as a separate project-local skill installed into each detected agent's skills dir (for example `.claude/skills/open-knowledge/`) whenever `ok init` runs.
compatibility
Any agent host — no MCP server required. Pure discovery + install guidance.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「open-knowledge-discovery」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-3ae81fb75c206d3b-Open-Knowledge-Discovery.html
请存为 .cursor/skills/open-knowledge-discovery/SKILL.md 或 .claude/skills/open-knowledge-discovery/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/inkeep/open-knowledge-skills' --list

npx skills add 'https://github.com/inkeep/open-knowledge-skills' --skill 'open-knowledge-discovery'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: open-knowledge-discovery description: "Read when the user asks what OpenKnowledge is, wants to install it on a repository, wants to open or preview a single markdown file that is not part of an OpenKnowledge project, wants to share an OpenKnowledge project with collaborators, asks whether OpenKnowledge supports a particular capability, or asks how `ok init` / `ok cowork` / OK Desktop set up a project. Do NOT load to perform OpenKnowledge reads/writes — the runtime guidance for editing markdown inside an initialized OK project ships as a separate project-local skill installed into each detected agent's skills dir (for example `.claude/skills/open-knowledge/`) whenever `ok init` runs." compatibility: "Any agent host — no MCP server required. Pure discovery + install guidance." metadata: author: "Inkeep" repository: "https://github.com/inkeep/open-knowledge-skills" --- # OpenKnowledge — what it is and how to install it OpenKnowledge (OK) is a markdown-CRDT collaboration platform. It turns a directory of `.md` / `.mdx` files into a live, multi-writer knowledge base: agents and humans edit the same documents in real time, every change is attributed, and a browser preview renders edits as they land. This skill covers **discovery, install, and opening OpenKnowledge files** — including single files that are not part of a project (see *Opening a file outside a project* below). It does **not** carry the in-project read/write runtime contract (the STOP rules for native file tools, the grounding and linking rules, the MCP routing table) — that ships separately as the project-local skill installed by `ok init` (see *Working inside a project* below). > **CLI name.** Commands below use Stable's `ok` (`open-knowledge`). OpenKnowledge > Beta's terminal commands are `ok-beta` (`open-knowledge-beta`), with `~/.ok-beta/` > in place of `~/.ok/`. ## Install OpenKnowledge on a repository Run `ok init` from the repository root: ```bash npx @inkeep/open-knowledge init # or, after a global install: npm install -g @inkeep/open-knowledge ok init ``` `ok init` is the one setup verb. It: - scaffolds a `.ok/` directory (project config — `content.dir` defaults to `.`); - wires the OpenKnowledge MCP server into the coding agents it detects on this machine — skip with `--no-mcp`; - installs the **project-local runtime skill** into each detected agent's skills dir (`/skills/open-knowledge/`) so agents working in this repo get the full read/write contract. OK only writes into agent directories that already exist — it never creates one, so nothing appears for agents you don't use, and `ok init` says so when it finds none; - ensures the project has a `.git/`. Re-run `ok init` any time to refresh wiring and skills to the installed CLI version. ## Share an OpenKnowledge project with collaborators An OK project travels with its repository. To share one: 1. Commit the `.ok/` directory and whichever project-local `/skills/open-knowledge/` directories `ok init` created, along with your `.md` content. 2. Collaborators clone the repo and run `ok init` once — that registers the MCP server on their machine and refreshes the project skill. 3. Start the editor + preview with `ok start` (or open the project in OK Desktop). Collaboration is real-time once two writers have the project open against the same content directory. ## `ok cowork` — Claude Chat & Cowork `ok init`'s editor wiring does not reach Claude Chat or Cowork — those read a separate Skills list inside the Claude Desktop App. Run `ok cowork` to build `openknowledge.skill` and open Claude Desktop so the user can upload it (Customize → Skills → + → Create skill → Upload skill). ## OK Desktop OK Desktop is the standalone macOS app (`@inkeep/open-knowledge-desktop`). It bundles its own CLI, opens a project as an editor + preview window, and keeps the project's MCP wiring and skills current on every launch. Download DMGs from the releases page. ## Opening a file outside a project OpenKnowledge can open a single markdown file that is **not** part of an OK project — a loose `.md` / `.mdx`, **or a file that lives inside a regular repo/folder which was never `ok init`'d**. It opens in a throwaway session (a temp project in the OS temp dir — your repo is never touched, no `.ok/` is written into it) with the same live preview you get inside a project. **Never run `ok init` just to view or open a file.** `ok init` turns a repo into a shared OpenKnowledge project; it is not a prerequisite for opening one file. Opening a file needs no project, no `.ok/`, and no server already running — each path below boots the session itself. When asked to open or preview such a file, **decide by the viewing surface you actually have** — check the tool, not the host name. Only open a browser when you genuinely have one; never pop a browser tab on a host that has none. - **You have an in-app / built-in browser** (Claude Code Desktop's Browser pane, Cursor, Codex, and similar) — this is the default: call the **`preview_url` MCP tool** with `file` set to the absolute path (it finds, or boots on demand, the session and returns a full `url`), then **immediately open that `url` in your in-app browser**. "Open it" means navigate your browser — don't just print the URL and stop. This is also the only way to view it in a browser when the OK Desktop app is installed (`ok open` prefers the Desktop app). Get the URL from `preview_url` only — never hunt for it via `ok ps` / `ok status` / `ok start` or a guessed port. - **No in-app browser** (a pure-stdio CLI) — run `ok open /abs/path/to/file.md`: it opens the Desktop app when installed, else a browser, and boots the session itself. Don't force a browser tab the user didn't ask for; `ok open` is the right default here. If `ok` isn't on PATH, `npx @inkeep/open-knowledge open /abs/path/to/file.md` does the same. If the OK MCP server isn't wired into this host there is no `preview_url` to call — use the `ok open` path above. Don't reconstruct what `preview_url` does by hand (spawning `ok mcp` yourself, scraping ports from `ok ps`). Give an absolute path. `ok open` prints the absolute project root it resolved for that path, and names the enclosing project too when the resolved root sits inside another one. Read that line rather than assuming which project you got. To name the project yourself, pass `--project `. It is honored wherever it appears: `--project ` or `--project=`, before or after the path, with or without the `.md` extension. If it cannot be honored the command exits non-zero and says why, so you never need a second command to find out where it landed, and never need to stop a server to correct it. Re-opening the same file lands on the same session. Never construct or guess the URL — use the one `preview_url` returns. ## What else OK does This skill does not enumerate OK's capabilities, and they change between releases. When asked whether OK supports something, read rather than guess: - **Docs** — - **Source** — ## Working inside a project — use the project-local skill, not this one Do **not** use this skill to perform OpenKnowledge reads or writes. The runtime contract — STOP rules for native file tools on in-scope markdown, the preview-attach handshake, grounding and linking rules, the MCP tool routing table — lives in a **separate project-local skill** installed into each detected agent's skills dir (`/skills/open-knowledge/SKILL.md`) whenever `ok init` runs. If the user is editing markdown inside a project that has a `.ok/` directory and this discovery skill is the only OpenKnowledge skill loaded, the project-local skill is missing (the repo was never `ok init`'d, or the skill directory was not committed). Advise the user to run `ok init` to install it. ## Learn more - Run `ok --help` for the full command list.

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…