Document-skills (pdf, docx, xlsx, pptx) are nearly invisible to users — discoverability and naming problem

## Summary

The `document-skills` plugin contains some of the most useful skills (pdf, docx, xlsx, pptx) but they are practically invisible to users due to multiple compounding discoverability barriers. I spent **two full sessions** doing heavy PDF work (filling forms, placing signatures, merging documents) using raw Python scripts before discovering the PDF skill existed — and even Claude itself told me it didn't exist.

## The experience (real session transcript)

1. I needed to fill PDF forms (wire transfer applications), extract signatures from signed PDFs, place them on new forms, and clean scanned documents
2. Claude helped me do all this using pypdf, reportlab, PyMuPDF — raw Python, no skill
3. After multiple sessions I asked: "why didn't the PDF skill trigger?"
4. Claude searched and confidently said: **"No PDF skill exists"** — twice
5. I pushed back ("something's off, pdf is a highly popular skill")
6. It took **3 rounds of web searching** to find it on GitHub
7. Installation required two non-obvious steps I'd never encountered before

## The barriers (each one alone might be fine, but they compound)

### 1. Hidden marketplace
The `anthropics/skills` marketplace is **not added by default**. Only `claude-plugins-official` ships out of the box. Users must know to run `/plugin marketplace add anthropics/skills` first — but how would they know this marketplace exists?

### 2. Bundle naming
The skill is inside `document-skills`, not `pdf`. No user searching for "pdf skill" will find something called "document-skills". The bundle name describes nothing about its contents.

### 3. No in-CLI search or catalog
There's no `/plugin search pdf` command. Users can't discover what's available without going to GitHub.

### 4. No auto-suggestion
Claude Code watched me write pypdf/reportlab/fitz code for hours across sessions and never suggested the PDF skill. If the system detected common library imports, it could say "hey, there's a skill for this."

### 5. Even Claude doesn't know
The AI assistant itself couldn't find the skill. It searched the local plugin directory, found no match, and concluded it didn't exist. If Claude can't find it, users definitely won't.

## Suggested improvements

1. **Ship `anthropics/skills` marketplace by default** (or surface it during onboarding)
2. **Allow individual skill install** — `claude plugin install pdf` instead of requiring the full bundle
3. **Add `/plugin search `** — browse available skills from within the CLI
4. **Rename for discoverability** — "document-skills" should at minimum list its contents (pdf, docx, pptx, xlsx) in the description
5. **Auto-suggest skills** — if Claude Code detects relevant library imports (pypdf, python-docx, openpyxl), suggest the corresponding skill
6. **Better plugin listing** — `/plugin list --available` to show what's installable, not just what's installed

## Related issues
- #138 — alias when installing plugins
- #67 — plugin skills not loaded when installed via marketplace
- #189 — document-skills and example-skills install duplicate content
- #667 — non-standard directory naming

## Environment
- Claude Code 2.1.78
- Windows 11
- Model: Claude Opus 4.6