Feature Request: Claude Code should have self-awareness of its own plugin ecosystem

Summary

Claude Code CLI now has 63 built-in plugins available via /plugin command, but when asked about available plugins, Claude only reports 13 plugins from outdated information. This creates a disconnect between Claude Code's actual capabilities and its self-knowledge.

Problem Description

1. Current behavior: When users ask Claude Code "what plugins are available?", it searches the web and returns outdated information (only 13 plugins from the GitHub repo's /plugins directory)

1. Expected behavior: Claude Code should be aware of all 63+ plugins currently available in its own plugin marketplace and be able to describe their functionality

1. Impact: Users cannot leverage Claude's help to discover and choose appropriate plugins because Claude itself doesn't know what's available

Suggested Solution

Please consider one of the following approaches:

1. Built-in plugin registry: Include a machine-readable plugin catalog that Claude can access to provide accurate information about available plugins

1. Self-introspection capability: Allow Claude to query its own plugin system programmatically (e.g., a tool like GetAvailablePlugins())

1. Documentation sync: Ensure Claude's training/context includes up-to-date information about all available plugins and their descriptions

Use Case

As a user, I want to ask Claude:

• "What plugins are available for code review?"
• "Which plugin should I use for Git workflow automation?"
• "List all plugins related to security"

And receive accurate, current answers based on the actual 63+ plugins available.

Environment

• Claude Code CLI version: 2.1.x (latest)
• Platform: Windows 11

---

This issue was submitted via Claude Code CLI