Skills/Plugins not proactively surfaced to model or user on first use

Problem

When plugins with skills are installed via the marketplace, neither the user nor the model (Claude) is proactively informed about their existence. The model doesn't know what skills/plugins are available until the user explicitly asks or invokes them.

Current Behavior

1. Plugins are installed via /plugin and skills are placed in ~/.claude/plugins/...
2. Skill descriptions are injected into the Skill tool's description via <available_skills> list
3. However, the model never proactively explores or announces available skills to the user
4. The user must either:

• Type / to see autocomplete
• Ask "What skills are available?"
• Already know the skill exists

Expected Behavior

• On first session (or after new plugin installation), Claude should be aware of and optionally surface available skills to the user
• The model should proactively mention relevant skills when the user's request matches a skill's description
• A brief onboarding message like "You have X skills available, type /skills to see them" would help discoverability

Why This Matters

• Users install plugins but never discover the skills they provide
• The lazy-loading design (description in context, full content on invoke) works well technically, but the discoverability UX is lacking
• Even the model itself doesn't proactively check what tools/skills it has access to

Environment

• Claude Code v2.1.59
• Multiple plugins installed from official marketplace (skill-creator, frontend-design, code-review, etc.)

Suggestion

1. Add a "skill discovery" step during plugin installation that lists new skills added
2. Consider a system-level instruction that tells Claude to check available skills on new sessions
3. Add a /skills built-in command to list all available skills with descriptions