A Claude Code skill that generates a visual dashboard of your Claude setup — agents, skills, hooks, and MCP servers — as a styled HTML file you can open in any browser.

A single HTML file (claude-code-capabilities-styled_1.html) with up to six sections:
- Agents — all agents available to you, grouped by plugin or custom
- Skills — all slash commands (
/skill-name), grouped and categorised - Hooks — automated behaviors that run before/after tool use or on session events
- MCP Servers — connected tools and integrations (local, claude.ai connectors, plugins)
- Scripts — local automation scripts, what each one does, what invokes it, and whether it's actually scheduled (checked against the live scheduler, not just a comment in the file) (optional, see below)
- Knowledge Library — explanatory notes about how Claude Code works (optional, see below)
The dashboard supports dark mode, light mode, and system preference, with a toggle in the header.
- Copy
SKILL.mdinto your Claude skills folder:
mkdir -p ~/.claude/skills/dashboard-refresh
cp SKILL.md ~/.claude/skills/dashboard-refresh/SKILL.md- Restart Claude Code (or start a new session). The skill is picked up automatically.
In any Claude Code session, run:
/dashboard-refresh
Claude will scan your live setup and write two files to ~/Desktop/Claude Capabilities Dashboard/:
| File | Purpose |
|---|---|
claude-code-capabilities.md |
Plain text source — easy to read and version |
claude-code-capabilities-styled_1.html |
Styled visual dashboard — open in a browser |
If the folder doesn't exist yet, it's created automatically. No existing files required — works on first run.
If you have local automation scripts — things invoked by a skill's instructions, or scheduled to run unattended via launchd/cron/etc. — the dashboard will include a Scripts section documenting each one: what it does, what invokes it, and whether it's actually scheduled.
That last part matters: the skill checks the live scheduler state (launchctl list <label>, crontab -l, the plist's own StartCalendarInterval) rather than trusting a script's own header comment about when it runs. A script that documents itself as "runs daily via cron" but was never actually installed anywhere gets flagged with ⚠ no active trigger found instead of being reported as working.
If you have no such scripts, the section is simply omitted — nothing breaks.
If you create a ~/.claude/knowledge/ folder, the dashboard will automatically include a Knowledge Library section listing all .md files inside it.
This folder is meant for explanatory notes about how Claude Code works — concepts, comparisons, mental models. Not rules (that's memory) or prompts (that's skills). Just reference notes you want to be able to look up.
mkdir -p ~/.claude/knowledgeAdd any .md file with a # Title heading and it will appear in the dashboard on the next /dashboard-refresh. If the folder doesn't exist, the section is simply omitted — nothing breaks.
Re-run /dashboard-refresh any time you:
- Install a new plugin, add an MCP server, or create a custom skill
- Add files to
~/.claude/knowledge/
Claude will diff against the existing dashboard and update only what changed.
- MCP servers configured in Claude's developer settings must be added to the dashboard manually — they can't be auto-detected
- claude.ai connected connectors (Zapier, Notion, Gamma, etc.) are detected automatically from your session context.