← ClaudeAtlas

add-understand-anythinglisted

Install the Understand-Anything plugin so the agent gains /understand, /understand-chat, /understand-dashboard and related codebase-analysis skills (interactive knowledge graphs, guided tours, deep-dive explanations). Claude Code backend only — adds the plugin from its GitHub marketplace end-to-end; non–Claude-Code backends use the upstream install.sh fallback.
sliamh11/Deus · ★ 43 · AI & Automation · score 80
Install: claude install-skill sliamh11/Deus
# Add Understand-Anything This skill installs [**Understand-Anything**](https://github.com/Lum1104/Understand-Anything) — an LLM-powered codebase-analysis tool that produces interactive knowledge graphs, guided tours, and deep-dive explanations of any project. Once installed, the agent gains the `/understand*` family of skills. It ships as a **Claude Code plugin** distributed through a GitHub plugin marketplace. This skill runs the whole marketplace flow (add marketplace → install plugin → verify) end-to-end so a single `/add-understand-anything` completely integrates it — no manual `/plugin` steps. > **Backend note:** This is a Claude Code installer. The `claude plugin …` > commands below only exist when Claude Code is the active backend (Deus's > default). On non–Claude-Code backends (Codex, opencode, gemini, …) use the > upstream `install.sh` fallback in Phase 0 instead. ## Phase 0: Backend guard Confirm the Claude Code CLI is available before doing anything else: ```bash command -v claude >/dev/null 2>&1 && echo "claude CLI found" || echo "NO claude CLI" ``` If the `claude` CLI is **not** found, this backend can't use the plugin marketplace. Stop here and tell the user to install via the upstream script instead (it symlinks the skills into the right place for their runtime): ```bash # Replace <platform> with one of: codex, opencode, gemini, pi, vscode, ... curl -fsSL https://raw.githubusercontent.com/Lum1104/Understand-Anything/main/install.sh | bash -s <platform>