claude-code - 💡(How to fix) Fix Skill picker: display argument-hint inline and make (plugin-name) annotation suppressible [1 comments, 2 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#52968Fetched 2026-04-25 06:15:57
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×5commented ×1

In Claude Code 2.1.119, plugin-provided skills render differently from slash commands in the / autocomplete picker in two ways that seem inconsistent / undocumented:

  1. argument-hint: is not shown inline for skills. A slash command displays /color <red|blue|green|yellow|...> — the arg-hint is inline on the same line. A plugin skill with identical argument-hint: frontmatter only shows its description:. The hint value is ignored by the picker.

  2. The (plugin-name) annotation on plugin skills is not suppressible. Plugin skills render as /skill-name (plugin-name) description…. There is no frontmatter option to hide the annotation. The skills docs reference argument-hint as "Hint shown during autocomplete" but don't describe this difference from commands, and the (plugin-name) annotation isn't documented in the skills frontmatter reference.

Root Cause

In Claude Code 2.1.119, plugin-provided skills render differently from slash commands in the / autocomplete picker in two ways that seem inconsistent / undocumented:

  1. argument-hint: is not shown inline for skills. A slash command displays /color <red|blue|green|yellow|...> — the arg-hint is inline on the same line. A plugin skill with identical argument-hint: frontmatter only shows its description:. The hint value is ignored by the picker.

  2. The (plugin-name) annotation on plugin skills is not suppressible. Plugin skills render as /skill-name (plugin-name) description…. There is no frontmatter option to hide the annotation. The skills docs reference argument-hint as "Hint shown during autocomplete" but don't describe this difference from commands, and the (plugin-name) annotation isn't documented in the skills frontmatter reference.

Fix Action

Fix / Workaround

The skills docs say "Custom commands have been merged into skills" and that a commands/foo.md and skills/foo/SKILL.md "both create /foo and work the same way." Plugin authors are migrating commands/skills/ based on this guidance, but the picker UX regresses: users lose the inline argument hint they relied on.

Code Example

plugins/myplugin/skills/foo/SKILL.md
---
name: foo
description: Do the foo thing.
argument-hint: "[target] [--flag]"
---
RAW_BUFFERClick to expand / collapse

Summary

In Claude Code 2.1.119, plugin-provided skills render differently from slash commands in the / autocomplete picker in two ways that seem inconsistent / undocumented:

  1. argument-hint: is not shown inline for skills. A slash command displays /color <red|blue|green|yellow|...> — the arg-hint is inline on the same line. A plugin skill with identical argument-hint: frontmatter only shows its description:. The hint value is ignored by the picker.

  2. The (plugin-name) annotation on plugin skills is not suppressible. Plugin skills render as /skill-name (plugin-name) description…. There is no frontmatter option to hide the annotation. The skills docs reference argument-hint as "Hint shown during autocomplete" but don't describe this difference from commands, and the (plugin-name) annotation isn't documented in the skills frontmatter reference.

Reproduction

Create a plugin skill:

plugins/myplugin/skills/foo/SKILL.md
---
name: foo
description: Do the foo thing.
argument-hint: "[target] [--flag]"
---

Type / in the picker and observe /foo (myplugin) Do the foo thing. — the argument-hint is absent. Compare to a local slash command with the same frontmatter in .claude/commands/foo.md which does render the hint inline.

Why it matters

The skills docs say "Custom commands have been merged into skills" and that a commands/foo.md and skills/foo/SKILL.md "both create /foo and work the same way." Plugin authors are migrating commands/skills/ based on this guidance, but the picker UX regresses: users lose the inline argument hint they relied on.

Requests

  1. Render argument-hint: inline in the picker for skills, matching slash-command behavior. This is what the docs imply ("hint shown during autocomplete") and what plugin authors expect after the commands→skills merge.
  2. Document the (plugin-name) annotation in the skills frontmatter reference, and consider an opt-out (frontmatter flag like show-plugin-name: false, or a per-plugin setting). The annotation is useful for distinguishing sources but shouldn't be the only thing that differentiates a skill from a command visually.

Environment

  • Claude Code: 2.1.119 (native install, macOS Darwin 25.3.0)
  • Plugin: published via marketplace (git source), 18 skills + 1 command migrated to skills-only
  • Behavior confirmed in the / picker on fresh sessions

extent analysis

TL;DR

The issue can be addressed by modifying the plugin skill's frontmatter to render the argument-hint inline and documenting the (plugin-name) annotation.

Guidance

  • Verify that the argument-hint frontmatter is correctly formatted and included in the plugin skill's markdown file.
  • Check the skills documentation for any updates or clarifications on rendering argument-hint inline for plugin skills.
  • Consider adding a feature request to the Claude Code issue tracker for an opt-out option to suppress the (plugin-name) annotation.
  • Review the plugin's skills and commands to ensure consistency in formatting and frontmatter usage.

Example

No code snippet is provided as the issue is related to the rendering of frontmatter values in the Claude Code picker.

Notes

The issue is specific to Claude Code version 2.1.119 and may be addressed in future updates. The requested changes are related to the rendering of plugin skills in the / picker and may require updates to the Claude Code documentation and frontmatter parsing.

Recommendation

Apply a workaround by manually formatting the argument-hint in the skill's description until the issue is addressed in a future version of Claude Code.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Skill picker: display argument-hint inline and make (plugin-name) annotation suppressible [1 comments, 2 participants]