>- Render an Open Knowledge Format (OKF) bundle as a single self-contained, interactive HTML graph (viz.html) — concepts as nodes coloured/sized by type, markdown links and bundle-internal `sources` as edges, a wiki-style detail panel with rendered markdown, v0.2 trust/lifecycle/provenance metadata, and "Links to" / "Cited by" backlinks, layout switching, per-type filter and search. Use when asked to visualize, graph, preview, or explore an OKF bundle.
npx skills add https://github.com/scaccogatto/okf-skills --skill visualize
Generate a self-contained HTML graph of the target bundle (default the project's
.okf/). No backend, no install on the viewing side, no data leaves the page.
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 status, generated, verified,
stale_after, and sources (with their credibility signals, a usage_count
alongside the usage_window that frames it); 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.
The output defaults to <bundle>/viz.html. Pass -o <path> to write elsewhere.
Bundles above 1,000 concepts default to the linear concentric layout (the
force layout freezes the page at that size — --layout cose overrides), and
--max-nodes N refuses oversized bundles, e.g. for CI.
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.
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
Take scaccogatto/visualize from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference pip.
Without those the skill loads but fails at the first command.