Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Skills command docs missing type-to-filter search box [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#54160•Fetched 2026-04-29 06:34:41
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 reference and related skill-browsing guidance

Current Documentation

The docs currently say:

Type / to see every command available to you, or type / followed by letters to filter.

and the /skills entry in the commands reference says:

| /skills | List available skills. Press t to sort by token count |

Desktop guidance also says:

Skills extend what Claude can do. Claude loads them automatically when relevant, or you can invoke one directly: type / in the prompt box or click the + button and select Slash commands to browse what's available.

None of the current docs mention that the dedicated /skills picker now includes its own type-to-filter search box.

What's Wrong or Missing?

Changelog v2.1.121 added a new /skills capability:

Added a type-to-filter search box to /skills so you can find a skill in long lists without scrolling

The current documentation still describes /skills as a simple list with token-count sorting, but it does not tell users that they can now search within the /skills picker itself.

That leaves an important usability improvement undiscoverable, especially for users with many bundled, personal, project, and plugin skills.

Suggested Improvement

Update the /skills command documentation to mention the new filter workflow explicitly.

For example, the commands reference could say:

/skills — List available skills. Type to filter the list by skill name, then press t to sort by token count.

Related browsing pages such as interactive-mode and desktop could also add a short note that the dedicated /skills picker supports type-to-filter search for long skill lists.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/commands/skills is documented here, but only mentions listing skills and pressing t to sort by token count
https://code.claude.com/docs/en/interactive-modeDocuments filtering in the general / command menu, but not the dedicated /skills picker search box
https://code.claude.com/docs/en/desktopExplains how to browse available skills from the UI, but not that /skills supports in-picker filtering
https://code.claude.com/docs/en/desktop-quickstartQuickstart browsing guidance has the same omission

Total scope: 4 pages affected

Source: Changelog v2.1.121

Exact changelog entry:

Added a type-to-filter search box to /skills so you can find a skill in long lists without scrolling

extent analysis

TL;DR

Update the /skills command documentation to mention the new filter workflow explicitly, including type-to-filter search box functionality.

Guidance

  • Review the current documentation for /skills on the affected pages (commands, interactive-mode, desktop, and desktop-quickstart) to identify areas where the type-to-filter search box is not mentioned.
  • Update the commands reference to include a description of the type-to-filter search box, such as: /skills — List available skills. Type to filter the list by skill name, then press t to sort by token count.
  • Consider adding a short note to related browsing pages (interactive-mode and desktop) to inform users about the dedicated /skills picker's support for type-to-filter search.
  • Verify the updates by checking the documentation on each of the 4 affected pages to ensure the new filter workflow is accurately described.

Example

The updated commands reference could include the following description:

| `/skills` | List available skills. Type to filter the list by skill name, then press `t` to sort by token count |

Notes

The updates should be made to the documentation on all 4 affected pages to ensure consistency and completeness.

Recommendation

Apply workaround: Update the documentation to reflect the new /skills capability, as this will improve usability and discoverability of the feature.

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#ssr#authentication issue#prompt issue#agent setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING