[FEATURE] Surface usage info (descriptions, homepage link, README) in the /plugin detail view

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

After I install a plugin, I can't tell what it does or how to use it from inside Claude Code. The /plugin detail view lists only component names. For plugin-dev, for example, it shows:

Commands: create-plugin
Agents: agent-creator, plugin-validator, skill-reviewer
Skills: agent-development, command-development, hook-development, ...

— no description for any component, no link to the plugin's homepage/repo, and no way to read its README.

So after installing, my workflow is essentially "guess." The create-plugins docs tell authors to "include a README.md with installation and usage instructions," and the discover-plugins docs tell me to "visit its homepage for usage guidance" — but the TUI surfaces neither: no README, no homepage link. To actually learn how to use a plugin I have to either dig through the on-disk cache (~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/README.md) or run commands blind to see what they do, which burns tokens. Installing a plugin and being dropped at "now what?" is the problem.

Proposed Solution

Make the /plugin detail view answer "how do I use this?", not just "what's in it?". In the Installed/Discover detail pane:

1. Show each component's existing description next to its name (commands and skills already declare one in their frontmatter), instead of only the name.
2. Show a clickable homepage/repository link from the plugin manifest.
3. Add a way to view or open the plugin's README from the TUI (render it in-app, or open it in the browser/editor).

(Rough mockup in Additional Context.)

Alternative Solutions

• Browsing the plugin cache on disk (~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/README.md) — works, but requires knowing the path and leaving the tool.
• Running each command/skill to see what it does — trial-and-error, and it spends tokens.
• /help and claude plugin details give names plus sometimes a one-line description, but still no README, no homepage, and no usage depth.

None of these is reachable from where I install and use the plugin.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

1. I run /plugin and install plugin-dev from the official marketplace.
2. I open its detail view to figure out how to start using it.
3. I see only names: Commands: create-plugin, Agents: agent-creator, ..., Skills: agent-development, ....
4. I have no idea what agent-development or plugin-validator do, when they fire, or where to read more — and there's no homepage link and no README.
5. To learn, I leave Claude Code to find the repo, or open the README buried in ~/.claude/plugins/cache/..., or just run /plugin-dev:create-plugin blind.
6. With this feature, the detail view shows each component's description + a homepage link + "view README," so I know how to use the plugin immediately — no filesystem spelunking, no tokens spent just to discover behavior.

Additional Context

Related work / how this differs

• PR #15561 ("Add component metadata to plugin.json for improved discoverability") shares the motivation — "users only see name + description; no way to know... whether it fits their use case" — but proposes author-declared metadata in plugin.json, and the TUI already derives the component list + context cost. This request is a different layer: surfacing usage (descriptions, homepage, README), not just listing components.
• The detail pane is actively evolving: #60689 (pre-install component inventory) and #60402 (last-updated metadata) show it already lists components and context cost. This is the natural next step: from "what's in it" to "how to use it."

The docs already assume this should exist

• create-plugins: authors should ship a README "with installation and usage instructions."
• discover-plugins: users should "visit its homepage for usage guidance."

The TUI links to neither.

Rough mockup of the improved detail view

plugin-dev @ claude-plugins-official [ Open homepage ↗ ]
Plugin development toolkit ...

Commands
create-plugin Guided end-to-end plugin creation workflow
Agents
agent-creator Generates agent configs from a description
plugin-validator Validates plugin structure / manifest
skill-reviewer Reviews skill quality and descriptions
Skills
hook-development Guidance for creating Claude Code hooks
...

[ View README ] [ Open homepage ]

Environment

• Claude Code 2.1.152
• Windows 11
• Marketplace: claude-plugins-official