list-plugins — Claude Code skill: list active plugins
list-plugins reads settings.json and reports active Claude Code plugins with their marketplace IDs. Use it to check which plugins are currently enabled.
Apache-2.0 ★ 1,497 updated 2026-06-16
npx skills add ghostwright/phantom --skill list-plugins -a claude-codeWhat list-plugins does
list-plugins reads /home/phantom/.claude/settings.json, parses enabledPlugins, and reports active entries only. It treats true, non-empty arrays, and non-empty objects as active; false values are skipped. The output includes plugin keys and short descriptions. For an unfamiliar plugin, the skill uses its marketplace ID rather than inventing a description.
If the file is missing or lacks enabledPlugins, the skill returns a corresponding empty-state message with a link to the plugin dashboard. The dashboard URL also appears in the regular listing. Responses stay under 100 words. The skill relies on the Read tool, so it needs access to the settings file at the specified path.
What it helps with
- check which Claude Code plugins are active
- identify the marketplace for an enabled plugin
- separate active entries from disabled ones
- get the plugin management dashboard link
Example prompts for the agent
- Show me the plugins currently active in Claude Code.
- Check my plugin list and include each marketplace ID.
- Are any plugins enabled in my Claude Code settings?
How to install list-plugins
1Skills CLI (Vercel)
npx skills add ghostwright/phantom --skill list-plugins -a claude-code2Manually: put the files in place
~/.claude/skills/list-plugins/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/list-plugins/
1Skills CLI (Vercel)
npx skills add ghostwright/phantom --skill list-plugins -a codex2Manually: put the files in place
.agents/skills/list-plugins/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ghostwright/phantom --skill list-plugins -a cursor2Manually: put the files in place
.cursor/skills/list-plugins/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ghostwright/phantom skills-builtin/list-plugins/SKILL.md2Manually: put the files in place
.github/skills/list-plugins/SKILL.md1Skills CLI (Vercel)
npx skills add ghostwright/phantom --skill list-plugins -a gemini-cli2Platform CLI
gemini skills install https://github.com/ghostwright/phantom --path skills-builtin/list-pluginsManually: put the files in place
.devin/skills/list-plugins/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about list-plugins
How do I install list-plugins in Claude Code?
Run npx skills add ghostwright/phantom --skill list-plugins -a claude-code.
What does list-plugins do?
It reads enabledPlugins from /home/phantom/.claude/settings.json and lists active plugins with their marketplace IDs. The response also includes the management dashboard link.
How does list-plugins decide whether a plugin is active?
It treats true, non-empty arrays, and non-empty objects as active values. Entries set to false are excluded.
Source text
SKILL.md · Apache-2.0
--- name: list-plugins x-phantom-source: built-in description: List the Claude Code plugins currently enabled for the agent, read straight from settings.json. when_to_use: Use when the operator asks "what plugins are installed", "which plugins are active", "show plugins", "list plugins", "show me the marketplace state", or any narrow question specifically about the current plugin set. allowed-tools: - Read context: inline --- # List plugins ## Goal Tell the operator which plugins are currently active for this agent, with their marketplace ids and a short description, in under 100 words. ## Steps ### 1. Read settings.json Use Read on `/home/phantom/.claude/settings.json`. Parse it as JSON. If the file does not exist, return: "No settings.json yet. The dashboard plugins tab is at /ui/dashboard/#/plugins." If the file exists but has no `enabledPlugins` field, return: "No plugins enabled yet. Browse the marketplace at /ui/dashboard/#/plugins." **Success criteria**: you have either a parsed `enabledPlugins` map or a clear empty-state message ready. ### 2. Filter active entries For each `key: value` in `enabledPlugins`, treat the entry as active when value is `true`, a non-empty array, or a non-empty object. Treat `false` and missing entries as inactive. **Success criteria**: you have a list of `plugin@marketplace` keys for active plugins only. ### 3. Render the list Format the response like this: > You have N plugins enabled: > > - **linear** at claude-plugins-official - Linear issue tracking > - **notion** at claude-plugins-official - Notion workspace > - **slack** at claude-plugins-official - Slack workspace messages > - **claude-md-management** at claude-plugins-official - CLAUDE.md maintenance > > Manage plugins at /ui/dashboard/#/plugins. For each row, the descriptor after the dash is a short fallback string based on the plugin name. If you do not recognize a plugin id, use just the marketplace id as the descriptor. **Success criteria**: the response shows the real current keys, the descriptors are honest (no fabricated descriptions for unknown plugins), and the dashboard URL is included. ## Rules - Never fabricate a plugin that is not in settings.json. - Never use em dashes in the response. Regular hyphens are fine. - Always include the dashboard URL. - Keep the response under 100 words.
© ghostwright · Apache-2.0 · ghostwright/phantom