Visualize an OKF bundle

Generate a self-contained HTML graph of the target bundle. The bundle directory is required, so pass .okf explicitly when no path is given. No backend, no install, no bundle content leaves the page. The viewer does need network access: cytoscape, marked and dompurify load from cdn.jsdelivr.net.

uv run "${CLAUDE_SKILL_DIR}/scripts/okf_visualize.py" $ARGUMENTS

If uv is unavailable:

python3 -m pip install --quiet pyyaml && \
python3 "${CLAUDE_SKILL_DIR}/scripts/okf_visualize.py" $ARGUMENTS

The detail panel shows each concept's type, description, tags, status, generated, verified, stale_after, sources (with their credibility signals, a usage_count alongside the usage_window that frames it), and rendered body; a sources entry pointing at another concept in the bundle also becomes a graph edge. A v0.1 timestamp is read as generated.at, so legacy bundles still render fully.

Two badges are derived, not read: the §5.3 trust tier (unverified / machine-confirmed / human-reviewed, keyed off the human: prefix in verified[].by) and staleness (today >= stale_after). They are advisory signals — when reporting on a bundle, say which tier a concept is in rather than treating any of them as a gate.

Above 1,000 concepts the default switches to concentric (force freezes the page; --layout cose overrides, and the in-page picker asks first). Above 5,000 it warns that the page loads slowly and reads as a hairball, and suggests rendering a subdirectory.

Open it in any browser; ${CLAUDE_SKILL_DIR} resolves whether this runs as part of the okf plugin or as a standalone skills.sh skill. The page is deep-linkable: ?select=<concept-id> or #<concept-id> opens that concept, ?layout=<name> presets the layout.