Agent skill · software engineering · lum1104
understand-dashboard
Launch the interactive web dashboard to visualize a codebase's knowledge graph
Why this skill is useful
Adds a script to launch a specific interactive dashboard for visualizing a codebase's knowledge graph, which is not commonly found in public documentation.
What it needs
Requires bash installed locally. About 3k tokens when loaded. Last updated 2026-07-30. 77,791 stars on the source repository.
What this skill does
/understand-dashboard Start the Understand Anything dashboard to visualize the knowledge graph for the current project. Instructions 1. Determine the project directory and data directory: If $ARGUMENTS contains a path, use that as the project directory Otherwise, use the current working directory Prefer the legacy .understand-anything/ data directory when it exists, otherwise use .ua/ Use the Bash tool to resolve: 2. Check that $UADIR/knowledge-graph.json exists in the project directory. If not, tell the user: Use the Bash tool to check: 3. Find the dashboard code. The dashboard is at packages/dashboard/ relative to this plugin's root directory. Check these paths in order and use the first that exists: ${CLAUDEPLUGINROOT}/packages/dashboard/ (Claude Code runtime root, highest priority) ~/.understand-anything-plugin/packages/dashboard/ (universal symlink, all installs) Two levels up from ~/.agents/skills/understand-dashboard real path (self-relative fallback) Two levels up from ~/.copilot/skills/understand-dashboard real path (Copilot personal skills fallback) Common clone-based install roots: ~/.codex/understand-anything/understand-anything-plugin/packages/dashboard/ ~/.opencode/understand-anything/understand-anything-plugin/packages/dashboard/ ~/.pi/understand-anything/understand-anything-plugin/packages/dashboard/ ~/understand-anything/understand-anything-plugin/packages/dashboard/ Use the Bash tool to resolve: 4. Fast path — try the prebuilt viewer first (no install, no build). Each release ships a self-contained viewer tarball; run it pinned to the installed plugin version: Run this in the background. It prints the same 🔑 Dashboard URL line as the dev server: If the line appears, skip steps 5-6 and continue at step 7. If the process exits without printing it (no release asset for this version, or no network), fall back to steps 5-6. 5. Fallback: install dependencies and build if needed: Then ensure the core package is built (the dashboard depends on it): 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills lum1104/understand-dashboard