Agent skill
understand-dashboard
Launch the interactive web dashboard to visualize a codebase's knowledge graph
Install this agent skill to your Project
npx add-skill https://github.com/Lum1104/Understand-Anything/tree/main/understand-anything-plugin/skills/understand-dashboard
SKILL.md
/understand-dashboard
Start the Understand Anything dashboard to visualize the knowledge graph for the current project.
Instructions
-
Determine the project directory:
- If
$ARGUMENTScontains a path, use that as the project directory - Otherwise, use the current working directory
- If
-
Check that
.understand-anything/knowledge-graph.jsonexists in the project directory. If not, tell the user:No knowledge graph found. Run /understand first to analyze this project. -
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:~/.understand-anything-plugin/packages/dashboard/(universal symlink, all installs)${CLAUDE_PLUGIN_ROOT}/packages/dashboard/(Claude Code plugin)- Two levels up from this skill file's real path:
../../packages/dashboard/(self-relative fallback)
Use the Bash tool to resolve:
bashSKILL_REAL=$(realpath ~/.agents/skills/understand-dashboard 2>/dev/null || readlink -f ~/.agents/skills/understand-dashboard 2>/dev/null || echo "") SELF_RELATIVE=$([ -n "$SKILL_REAL" ] && cd "$SKILL_REAL/../.." 2>/dev/null && pwd || echo "") PLUGIN_ROOT="" for candidate in \ "$HOME/.understand-anything-plugin" \ "${CLAUDE_PLUGIN_ROOT}" \ "$SELF_RELATIVE"; do if [ -n "$candidate" ] && [ -d "$candidate/packages/dashboard" ]; then PLUGIN_ROOT="$candidate"; break fi done if [ -z "$PLUGIN_ROOT" ]; then echo "Error: Cannot find the understand-anything plugin root. Make sure you followed the installation instructions and that ~/.understand-anything-plugin exists." exit 1 fi -
Install dependencies and build if needed:
bashcd <dashboard-dir> && pnpm install --frozen-lockfile 2>/dev/null || pnpm installThen ensure the core package is built (the dashboard depends on it):
bashcd <plugin-root> && pnpm --filter @understand-anything/core build -
Start the Vite dev server pointing at the project's knowledge graph:
bashcd <dashboard-dir> && GRAPH_DIR=<project-dir> npx vite --host 127.0.0.1 --openRun this in the background so the user can continue working.
-
Capture the access token URL from the server output. The Vite server prints a line like:
🔑 Dashboard URL: http://127.0.0.1:<PORT>?token=<TOKEN>Extract the full URL including the
?token=parameter. The token is required to access the knowledge graph data — without it the dashboard will show an "Access Token Required" gate. -
Report to the user, including the full tokenized URL:
Dashboard started at http://127.0.0.1:<PORT>?token=<TOKEN> Viewing: <project-dir>/.understand-anything/knowledge-graph.json The dashboard is running in the background. Press Ctrl+C in the terminal to stop it.Important: Always include the
?token=parameter in the URL you share. If you omit it, the user will be blocked by the token gate and have to manually find the token in the terminal output.
Notes
- The dashboard auto-opens in the default browser via
--open - If port 5173 is already in use, Vite will pick the next available port
- The
GRAPH_DIRenvironment variable tells the dashboard where to find the knowledge graph
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
understand-chat
Use when you need to ask questions about a codebase or understand code using a knowledge graph
understand
Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships
understand-explain
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase
understand-knowledge
Analyze a Karpathy-pattern LLM wiki knowledge base and generate an interactive knowledge graph with entity extraction, implicit relationships, and topic clustering.
understand-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks
understand-onboard
Use when you need to generate an onboarding guide for new team members joining a project
Didn't find tool you were looking for?