Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] /skills command docs missing prompt-prefill selection behavior [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52621•Fetched 2026-04-24 06:02:14
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×4
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/commands

Section/Topic

/skills command entry and the skill-picker workflow for inserting a selected skill into the prompt

Current Documentation

The commands reference currently says:

/skills | List available skills

The Desktop guide also says:

Select one and it appears highlighted in the input field. Type your task after it and send as usual.

But the docs do not explain that /skills opens a selectable picker and that accepting a skill pre-fills /<skill-name> in the prompt so you can continue typing arguments or task text before sending.

What's Wrong or Missing?

Changelog v2.1.119 includes this entry:

Fixed /skills Enter key closing the dialog instead of pre-filling /<skill-name> in the prompt

That fix confirms an intended user-facing workflow: /skills is not just a passive list. Users can choose a skill from the dialog, have /<skill-name> inserted into the prompt, then add arguments or a task before submitting.

The current docs do not describe that /skills picker behavior. The commands reference reduces /skills to "List available skills," and the broader desktop guidance mentions selected skills appearing in the input field without connecting that behavior to the /skills command itself. That leaves the keyboard-driven /skills workflow undocumented.

Suggested Improvement

Expand the /skills entry in the commands reference to describe the actual interaction model, for example:

Opens the skills picker. Select a skill to insert /<skill-name> into the prompt, then add arguments or task text and send as usual.

Also add a short note in the Desktop or interactive-command docs that this same prefill flow applies when browsing skills through /skills, not only when opening slash commands from the + menu.

If Anthropic documents keyboard behavior for this picker, note that pressing Enter accepts the highlighted skill and returns you to the prompt with the skill name pre-filled.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageLine(s)Context
https://code.claude.com/docs/en/commands82/skills is documented only as "List available skills"
https://code.claude.com/docs/en/desktop344Explains that selected skills appear highlighted in the input field, but does not tie that workflow to /skills
https://code.claude.com/docs/en/claude-directory1457/skills is described only as showing available skills from project, user, and plugin sources

Total scope: 3 pages affected

Source: Changelog v2.1.119

Exact changelog entry:

Fixed /skills Enter key closing the dialog instead of pre-filling /<skill-name> in the prompt

extent analysis

TL;DR

Update the documentation for the /skills command to describe its interactive behavior, including the skill picker and pre-filling of the prompt.

Guidance

  • Review the current documentation for /skills on the affected pages (commands reference, desktop guide, and claude directory) to identify areas where the interactive workflow is not clearly described.
  • Expand the /skills entry in the commands reference to include a description of the skill picker and how selecting a skill pre-fills the prompt, as suggested in the issue.
  • Consider adding a note to the desktop or interactive-command docs to clarify that the prefill flow applies when browsing skills through /skills, not just when opening slash commands from the + menu.
  • Verify that the updated documentation accurately reflects the intended user-facing workflow, as confirmed by the changelog entry for v2.1.119.

Example

The suggested improvement provides an example of how the /skills entry in the commands reference could be updated:

Opens the skills picker. Select a skill to insert /<skill-name> into the prompt, then add arguments or task text and send as usual.

Notes

The issue highlights a specific gap in the documentation, and addressing this should improve the user experience. However, it's essential to review the entire documentation set to ensure consistency and accuracy.

Recommendation

Apply the suggested workaround by updating the documentation to reflect the interactive behavior of the /skills command, as this directly addresses the identified issue and improves the user experience.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#API rate limit#retriever error#indexing error#inference speed#output truncation

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING