Understand Dashboard
Start the Understand Anything web dashboard so you can explore an existing project knowledge graph instead of guessing module relationships from grep alone.
Overview
understand-dashboard is an agent skill most often used in Build (also Operate infra, Idea research) that launches the Understand Anything web UI for an existing codebase knowledge graph.
Install
npx skills add https://github.com/lum1104/understand-anything --skill understand-dashboardWhat is this skill?
- Launches interactive dashboard from packages/dashboard with multi-root path fallbacks
- Requires `.understand-anything/knowledge-graph.json` or directs user to run /understand first
- Accepts optional project-path argument; defaults to cwd
- Checks CLAUDE_PLUGIN_ROOT, ~/.understand-anything-plugin, and clone-based Codex/OpenCode paths
- Visualizes knowledge graph already built for the repo
Adoption & trust: 852 installs on skills.sh; 54.9k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You generated or inherited a codebase map file but still cannot see relationships without spinning up the dashboard yourself.
Who is it for?
Builders using the Understand Anything plugin who want a one-command browser view after /understand on the same repo.
Skip if: Repos with no prior /understand run or teams that forbid local dev servers for visualization.
When should I use this skill?
Launch the interactive web dashboard to visualize a codebase's knowledge graph; optional project-path argument.
What do I get? / Deliverables
The interactive knowledge-graph dashboard runs against your project after path resolution, assuming /understand already produced knowledge-graph.json.
- Running local dashboard session bound to project knowledge graph
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build agent-tooling because the command boots a dev visualization tied to `.understand-anything/knowledge-graph.json` produced by codebase analysis. It resolves plugin dashboard paths across Claude, Copilot, Codex, and OpenCode installs and requires prior graph generation—pure agent ergonomics for navigation.
Where it fits
Open the dashboard right after /understand on a new client repo to see service boundaries before you cut a feature branch.
Re-launch the graph UI during an incident to trace which packages own the failing integration without re-running full analysis.
Point the skill at a cloned OSS competitor to skim architecture hotspots before writing a validation spike.
How it compares
Agent workflow launcher for a project graph UI—not a static markdown architecture doc.
Common Questions / FAQ
Who is understand-dashboard for?
Solo developers and indie teams on Claude Code, Copilot, or Codex who already use Understand Anything and want the graph in a browser.
When should I use understand-dashboard?
In Build when exploring module structure after analysis; in Operate when revisiting production services; in Idea when mapping an unfamiliar clone—always after knowledge-graph.json exists.
Is understand-dashboard safe to install?
Check Prism’s Security Audits panel and review what local server the dashboard binds to before exposing it on shared networks.
SKILL.md
READMESKILL.md - Understand Dashboard
# /understand-dashboard Start the Understand Anything dashboard to visualize the knowledge graph for the current project. ## Instructions 1. Determine the project directory: - If `$ARGUMENTS` contains a path, use that as the project directory - Otherwise, use the current working directory 2. Check that `.understand-anything/knowledge-graph.json` exists in the project directory. If not, tell the user: ``` No knowledge graph found. Run /understand first to analyze this project. ``` 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: - `${CLAUDE_PLUGIN_ROOT}/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: ```bash SKILL_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 "") COPILOT_SKILL_REAL=$(realpath ~/.copilot/skills/understand-dashboard 2>/dev/null || readlink -f ~/.copilot/skills/understand-dashboard 2>/dev/null || echo "") COPILOT_SELF_RELATIVE=$([ -n "$COPILOT_SKILL_REAL" ] && cd "$COPILOT_SKILL_REAL/../.." 2>/dev/null && pwd || echo "") PLUGIN_ROOT="" for candidate in \ "${CLAUDE_PLUGIN_ROOT}" \ "$HOME/.understand-anything-plugin" \ "$SELF_RELATIVE" \ "$COPILOT_SELF_RELATIVE" \ "$HOME/.codex/understand-anything/understand-anything-plugin" \ "$HOME/.opencode/understand-anything/understand-anything-plugin" \ "$HOME/.pi/understand-anything/understand-anything-plugin" \ "$HOME/understand-anything/understand-anything-plugin"; 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." echo "Checked:" echo " - ${CLAUDE_PLUGIN_ROOT:-<unset CLAUDE_PLUGIN_ROOT>}" echo " - $HOME/.understand-anything-plugin" echo " - ${SELF_RELATIVE:-<unresolved path derived from ~/.agents/skills/understand-dashboard>}" echo " - ${COPILOT_SELF_RELATIVE:-<unresolved path derived from ~/.copilot/skills/understand-dashboard>}" echo " - $HOME/.codex/understand-anything/understand-anything-plugin" echo " - $HOME/.opencode/understand-anything/understand-anything-plugin" echo " - $HOME/.pi/understand-anything/understand-anything-plugin" echo " - $HOME/understand-anything/understand-anything-plugin" echo "Make sure you followed the installation instructions for your platform." exit 1 fi ``` 4. Install dependencies and build if needed: ```bash cd <dashboard-dir> && pnpm install --frozen-lockfile 2>/dev/null || pnpm install ``` Then ensure the core package is built (the dashboard depends on it): ```bash cd <plugin-root> && pnpm --filter @understand-anything/core build ``` 5. Start the Vite dev server pointing at the project's knowledge graph: ```bash