メニュー
Use when the user reports a problem with Open Knowledge, asks for help debugging OK, or wants to file a bug report. This skill guides the agent to capture diagnostic information via the ok bug-report CLI command.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/inkeep/open-knowledge-legacy --skill open-knowledge-bug-reportコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
| name | open-knowledge-bug-report |
| description | Use when the user reports a problem with Open Knowledge, asks for help debugging OK, or wants to file a bug report. This skill guides the agent to capture diagnostic information via the ok bug-report CLI command. |
| compatibility | Any MCP host (Claude Code, Cursor, Codex, Windsurf) with Open Knowledge MCP server registered. |
| metadata | {"version":"0.6.0","author":"Inkeep","repository":"https://github.com/inkeep/open-knowledge"} |
When a user reports a problem with Open Knowledge or asks for debugging help, use the ok bug-report command to capture a structured diagnostic bundle.
ok bug-report --no-reveal
The --no-reveal flag suppresses the Finder reveal (use it when running as an agent — you want the file path, not a Finder window).
~/.ok/logs/ (NDJSON format, pino)~/.ok/bug-reports/<timestamp>-bugreport.zip<timestamp>-bugreport.zip
├── MANIFEST.json — what's inside, redaction audit report
├── sysinfo.json — versions, locale, disk, build channel
├── README.md — what's safe to share, discipline version
├── logs/ — NDJSON log files (auto-redacted)
├── lockdir/ — server.lock, spawn-error-log (if project)
└── recent-ipc-errors.json — last 50 structured IPC errors
ok bug-report --no-reveal in the user's project directory (or home if no project)unzip -o <path> -d /tmp/ok-diag-<timestamp>/MANIFEST.json — check the redactions array (if non-empty, some content was scrubbed)sysinfo.json — check versions, disk space, build channelgrep '"level":50' logs/*.log | head -20 (level 50 = error in pino)recent-ipc-errors.json for IPC-layer failuresThe ok bug-report command ships with @inkeep/open-knowledge >= 0.7.0. If the user's version is older:
ok --versionnpm install -g @inkeep/open-knowledge@latest to update~/.ok/logs/ for recent .log files (NDJSON format, greppable)The bundle auto-redacts:
/Users/<name>/ → ~/)ghp_, gho_, ghu_, ghs_, ghr_)The MANIFEST.json redactions array lists every file and pattern that was scrubbed. The bundle is safe for the user to attach to a GitHub issue.
Read when the user asks what Open Knowledge is, wants to install it on a repository, wants to share an Open Knowledge project with collaborators, or asks how `ok init` / `ok install-skill` / OK Desktop set up a project. Do NOT load to perform Open Knowledge reads/writes — the runtime guidance for editing markdown inside an initialized OK project ships as a separate project-local skill at `.claude/skills/open-knowledge/` whenever `ok init` runs. If the user appears to be editing markdown inside a `.ok/` project and this is the only OK skill loaded, advise them to re-run `ok init` to install the project-local skill.
MUST invoke before reading or editing any `.md` / `.mdx` file, and before any `mcp__open-knowledge__*` tool call (`exec`, `search`, `write_document`, `edit_document`, and the rest). This skill is installed into the repository by `ok init`, so its presence alone means this is an Open Knowledge project — its runtime contract governs every markdown file here, with no need to probe for a `.ok/` directory. Authoritative agent-runtime contract; supersedes the overlapping MCP server `instructions` echo.