菜单
Render a knowledge bundle as an interactive graph — native UI where the host supports it, otherwise a self-contained HTML artifact.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Portable OKF knowledge bundle for coding-agent memory and LLM wikis. Use when the user wants to start a wiki, ingest a source, query project knowledge with citations, lint for drift, or visualize connections; whenever a repo has a knowledge/ bundle that should inform the task; and when another kb-* skill needs the shared spec, glossary, templates, or trust model.
Ingest a source into the knowledge bundle. Use when the user wants to capture, ingest, file, process, or "add this" — a note, transcript, email, PDF, image, web page, or any raw source — into a knowledge/ bundle, or drops content for processing. Reads the source once, extracts its signal, and integrates it across the bundle under the trust model so knowledge compounds instead of being re-derived per query.
Scaffold a new OKF knowledge bundle in this project — run when starting a wiki or adding a bundle under knowledge/.
Health-check a knowledge bundle for conformance and drift; optionally auto-fix safe issues.
Answer from the knowledge bundle. Use when the user asks what they/the project know about something, wants to look something up, explore connections, or compare things that live in a knowledge/ bundle — and when any task would be informed by an existing bundle, consult it here before answering from scratch. Navigates by progressive disclosure and files valuable answers back so the bundle compounds.
| name | kb-visualize |
| description | Render a knowledge bundle as an interactive graph — native UI where the host supports it, otherwise a self-contained HTML artifact. |
| disable-model-invocation | true |
Render a bundle as an interactive force-directed graph of its concepts, so a human can see its shape — hubs, clusters, orphans, and how concepts connect. You author the view from a deterministic graph model, so it can adapt to the request (a whole-bundle map, or a subgraph around one concept); it is not a fixed template.
Run the bundled extractor against the target bundle (default knowledge/):
python3 "${CLAUDE_SKILL_DIR}/scripts/graph.py" <bundle-dir>
It prints JSON: nodes (each with id, type, title, description, tags, resource,
status, body, links, cited_by), the distinct types, and edges. Backlinks (cited_by) and
edges are already computed from the cross-links in concept bodies. If the user scoped the request to
one concept/area, filter the model to that node plus its neighbors.
Completion criterion: you have the graph model, and (if scoped) filtered it to the requested subgraph.
If unsure whether the host renders UI, default to the HTML file — it works everywhere.
Completion criterion: the output form matches the host's capability.
Whichever form, the view must show (mirroring a conformant OKF viewer):
type, directed edges from
each cross-link. A layout the user can switch (e.g. cose / concentric / breadth-first / grid) is a
plus.description, resource as a link,
tags) and its rendered markdown body, with internal concept links rewired to navigate within
the view (select that node) rather than following a file path.cited_by (the reverse link graph).For the HTML form, a proven stack is Cytoscape.js (graph) + marked (markdown) from a CDN, with the graph model inlined as a JSON literal so the file is self-contained and nothing leaves the page. All node data is already in the model from step 1 — do not re-read the bundle.
Completion criterion: the rendered view shows the graph (colored by type), a working detail panel with in-view link navigation, backlinks, search, and type filter.
Hand over the result: for UI, the live view; for HTML, the file path (and note it can be committed next to the bundle, shared as an artifact, or hosted on any static file server). This is a read-only consumer — it never modifies the bundle, so no log entry.
Completion criterion: the user has the view or its path.