add-understand-anything

Solid

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.

AI & Automation 48 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
56
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

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

Details

Author
sliamh11
Repository
sliamh11/Deus
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

super-claudioai-and-agents

AI integration and agent building skill. Use when the user wants to use the Claude API, build AI-powered apps, create Claude Code skills or agents, connect MCP servers, or improve their prompts and AI workflows. Trigger on: "use the Claude API", "Anthropic API", "build an AI app", "create a Claude skill", "write a skill for Claude Code", "build an agent", "MCP server", "Model Context Protocol", "connect Claude to X", "prompt engineering", "improve my prompt", "system prompt", "AI workflow", "LLM integration", "build a chatbot", "fine-tuning", "Claude Code plugin", "create a plugin", "AI pipeline", "multi-agent", "tool use", "function calling". Also trigger when the user mentions: superpowers, skill-creator, claude-md-management, pr-review-toolkit, context7, or any Claude Code plugin by name. Do NOT trigger for: general code questions without AI integration (use software-development).

3 Updated yesterday
toolbox-playground
AI & Automation Solid

claude-code-plugin-reference

Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.

323 Updated today
athola
AI & Automation Listed

claude-plugin-authoring

Basics of authoring a Claude Code plugin — the plugin.json manifest, the .claude-plugin/ directory layout, the component types (skills, agents, commands, hooks, MCP), and the validate/install workflow. Use when creating a new Claude Code plugin or wiring one into a marketplace.

0 Updated yesterday
glitchwerks