Skip to main content
skill CX Codex

show-my-tools — Claude Code skill: what it does, how to install

show-my-tools audits the agent environment and lists loaded skills, memory files, plugins, hooks, and subagents. It also outputs a settings summary and dashboard links.

Apache-2.0 ★ 1,497 updated 2026-06-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ghostwright/phantom --skill show-my-tools -a claude-code
Open on GitHub

What show-my-tools does

The skill scans agent configuration files directly under /home/phantom/.claude/. Using Glob and Read, it parses YAML frontmatter from every SKILL.md to identify active skills. It also tracks markdown notes and rule files, recording their paths and byte sizes without loading file bodies into memory.

Next, it parses /home/phantom/.claude/settings.json. The prompt inspects enabled plugins, counts hooks per event, lists markdown definitions in agents/, and extracts key runtime flags. Those include the active model, permission mode, MCP server count, and autoMemoryEnabled. The output finishes with an exact URL for the operator dashboard.

Because all inspection steps point to /home/phantom/.claude/, running this outside the Phantom setup requires adjusting hardcoded paths in the skill file.

What it helps with

  • audit installed skills and active plugins in Claude Code
  • list memory and rule files along with file sizes
  • count configured event hooks without reading raw JSON
  • inspect current runtime flags and connected MCP servers

Example prompts for the agent

  • Show me your skills and active plugins
  • What memory files do you have in .claude?
  • Show my settings and dashboard URL

How to install show-my-tools

1Skills CLI (Vercel)

npx skills add ghostwright/phantom --skill show-my-tools -a claude-code

2Manually: put the files in place

~/.claude/skills/show-my-tools/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/show-my-tools/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about show-my-tools

How to install show-my-tools in Claude Code?

Run npx skills add ghostwright/phantom --skill show-my-tools -a claude-code. The definition file will be placed in ~/.claude/skills/show-my-tools/SKILL.md.

What does show-my-tools do?

It inspects agent directories on disk and returns a seven-part summary. The output lists skills, memory files, plugins, hooks, subagents, runtime settings, and the local dashboard address.

Which tools does the skill require?

It uses Read, Glob, and Bash to find markdown manifests and parse settings.json. It only inspects files and never modifies your configuration.

Source text

SKILL.md · Apache-2.0
---
name: show-my-tools
x-phantom-source: built-in
description: List the agent's current skills, memory files, plugins, subagents, hooks, and a settings summary plus dashboard URLs. The user-facing discovery path for everything the operator can edit.
when_to_use: Use when the user says "what can you do", "what skills do you have", "show me your skills", "what can I edit", "how do I customize you", "what memory files do you have", "what plugins do you have", "what subagents do you have", "what hooks do I have", "show my settings", "what is in your .claude", "where is the dashboard", or any similar discovery question.
allowed-tools:
  - Read
  - Glob
  - Bash
context: inline
---

# Show my tools

## Goal

Give the user a clear, accurate view of what is currently loaded: skills, memory files, and dashboard URLs. Honest about what is on disk, not a marketing list.

## Steps

### 1. List skills

Use Glob to find every `SKILL.md` file under `/home/phantom/.claude/skills/`. For each hit, Read the file and extract the YAML frontmatter's `name` and `description`.

**Success criteria**: you have a list of `(name, description)` pairs for every SKILL.md on disk.

### 2. List memory files

Use Glob to find every `.md` file directly under `/home/phantom/.claude/` (depth up to 3), excluding the `skills/` subtree and the `plugins/` and `agents/` subtrees. Do not read their content; just list the paths and sizes.

**Success criteria**: you have a list of memory file paths with sizes.

### 2.5 List plugins

Use Read to open `/home/phantom/.claude/settings.json`. Parse it as JSON. If there is no `enabledPlugins` field, skip this section. Otherwise, for each `key: value` in `enabledPlugins` where the value is truthy (true, an object, or a non-empty array), record the `plugin-id@marketplace-id` and a short fallback description.

**Success criteria**: you have a list of currently active plugin keys, or you know the list is empty.

### 2.6 List hooks

Use Read to open `/home/phantom/.claude/settings.json`. Parse it as JSON. If there is no `hooks` field, record the count as 0. Otherwise, for each event name in `hooks`, count the total number of hook definitions across all matcher groups for that event. Report the per-event counts and the grand total.

**Success criteria**: you have a number like "4 hooks across PreToolUse (2), PostToolUse (1), UserPromptSubmit (1)", or you know the list is empty.

### 2.7 List subagents

Use Glob to find every `*.md` file directly under `/home/phantom/.claude/agents/`. For each, Read the file and extract the YAML frontmatter's `name` and `description`.

**Success criteria**: you have a list of `(name, description)` pairs, or you know the list is empty.

### 2.8 Read a settings summary

Use Read to open `/home/phantom/.claude/settings.json`. Parse it as JSON. Produce a single-line summary covering: permissions.defaultMode (if set), model (if set), count of `enabledMcpjsonServers`, count of `allowedHttpHookUrls`, whether `autoMemoryEnabled` is true. Skip any field that is not present.

**Success criteria**: one sentence covering the live settings. Do not dump the full JSON.

### 3. Render as seven sections

Format the response like this:

> **Skills.** I have N skills loaded from /home/phantom/.claude/skills/:
>
> - **mirror** - weekly self-audit playback
> - **thread** - the evolution of thinking on a topic
> - **echo** - prior-answer surfacer before I answer substantive questions
> - **overheard** - promises audit from the last 14 days
> - **ritual** - turn latent patterns into scheduled jobs
> - **show-my-tools** - this one
>
> **Memory files.** I have M markdown files under /home/phantom/.claude/:
>
> - **CLAUDE.md** - top-level memory (N bytes)
> - **rules/...** - any rule files you have written
> - **memory/...** - any free-form notes you have written
>
> **Plugins.** I have K plugins enabled from claude-plugins-official:
>
> - **linear** - Linear issue tracking
> - **notion** - Notion workspace knowledge
> - **slack** - Slack workspace messages
> - **claude-md-management** - CLAUDE.md maintenance
>
> **Hooks.** I have H hooks loaded:
>
> - PreToolUse (2): bash precheck, write formatter
> - UserPromptSubmit (1): prompt audit
>
> **Subagents.** I have S subagents defined under /home/phantom/.claude/agents/:
>
> - **research-intern** - fetch a paper and summarize into five bullets
> - **qa-checker** - verify that unit tests ran and passed
>
> **Settings summary.** Permission mode: default. Model: claude-opus-4-7. 3 MCP servers enabled. Auto-memory: on. 2 allowed HTTP hook URLs.
>
> **Dashboard.** You can see and edit all of the above at `<public_url>/ui/dashboard/`. Six tabs are live: skills, memory files, plugins, subagents, hooks, settings. The other tabs (sessions, cost, scheduler, evolution, memory explorer) are coming in later releases.

If `public_url` is not available, use `http://localhost:<port>/ui/dashboard/` or whatever matches the operator's known URL.

**Success criteria**: the response shows the real current counts and names, the dashboard URL is accurate, and the user can act on it immediately.

## Rules

- Never fabricate a skill or memory file that is not actually on disk.
- Never use em dashes in the response. Regular hyphens are fine.
- Always list the dashboard URL.
- If a skill has invalid YAML frontmatter, show it in the list with a note "(parse error)" so the user can fix it.
- Keep the response under 500 words.

© ghostwright · Apache-2.0 · ghostwright/phantom

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set38

The whole set →
thread Trace how your thinking on a topic changed over time. The skill turns memory entries into a chronological account with marked turning points. CX Codex +1 ★ 1,497repo stars phase-10a-chat-pipeline-research phase-10a-chat-pipeline-research — a slash command that walks Phantom's chat pipeline from SDK events through SSE to React rendering. You get a file-grounded report, and no code is touched. GP ChatGPT ★ 1,497repo stars overheard overheard scans two weeks of stored memory to surface unfulfilled commitments and prepares followup drafts. CX Codex +1 ★ 1,497repo stars phase-10d-chat-ui-polish-research The phase-10d-chat-ui-polish-research prompt guides a review of Phantom’s chat UI using screenshots and project files, then asks for a design direction and an implementation plan. GP ChatGPT ★ 1,497repo stars ritual Detects recurring behaviors from your session history and transforms them into scheduled tasks. If you regularly do something on a cadence, ritual proposes automating it. CX Codex +1 ★ 1,497repo stars phase-10h-chat-integrity-builder The phase-10h-chat-integrity-builder prompt directs Claude Code to fix transcript integrity in the Phantom chat, including attachment handling and SDK errors. It targets an existing project. GP ChatGPT ★ 1,497repo stars phase-10a-activity-correctness-builder The phase-10a-activity-correctness-builder prompt for Claude Code governs activity visibility during long-running requests, showing users that work continues when the interface is quiet. GP ChatGPT ★ 1,497repo stars phase-10b-durable-timeline-builder phase-10b-durable-timeline-builder guides Claude Code to implement durable chat run timelines, redaction, and stream reconnect logic as a principal engineer. GP ChatGPT ★ 1,497repo stars

Project sponsors

Companies that keep this analytics open