Skill Market

understand dashboard

Launch the interactive web dashboard to visualize a codebase's knowledge graph

GitHub
githubcommunityantigravity-skillsbusiness-knowledgeclaude-codeclaude-skillscodexcodex-skills
0.0
0 installs82.8K GitHub starsby Lum1104

Skill Introduction

Overview
Launch the interactive web dashboard to visualize a codebase's knowledge graph

Core value

Turns reusable Debugging know-how into an installable skill, helping users complete github, community, antigravity-skills, business-knowledge work faster.

Target users

  • Developers, testers, and maintainers who handle Debugging tasks in Focus Code.
  • Teams that already trust workflows or content from Lum1104.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community, antigravity-skills, business-knowledge that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Debugging, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, antigravity-skills, business-knowledge, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install understand-dashboard-aeea55
View source

Detail Preview

SKILL.md

Primary filemarkdown6 KB

name: understand-dashboard description: Launch the interactive web dashboard to visualize a codebase's knowledge graph argument-hint: [project-path]

/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:

    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:

    cd <dashboard-dir> && pnpm install --frozen-lockfile 2>/dev/null || pnpm install
    

    Then ensure the core package is built (the dashboard depends on it):

    cd <plugin-root> && pnpm --filter @understand-anything/core build
    
  5. Start the Vite dev server pointing at the project's knowledge graph:

    cd <dashboard-dir> && GRAPH_DIR=<project-dir> npx vite --host 127.0.0.1
    

    Run this in the background so the user can continue working.

  6. 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.

  7. 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_DIR environment variable tells the dashboard where to find the knowledge graph

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet