Skills from marketplace plugins don't appear in slash command autocomplete

Open 💬 15 comments Opened Jan 18, 2026 by allen-hsu

Description

Skills installed via marketplace plugins (registered in extraKnownMarketplaces) do not appear in the slash command autocomplete menu, even though:

  1. The skills are correctly loaded (visible in the available skills list)
  2. The skills can be invoked via the Skill tool programmatically
  3. The skills have proper SKILL.md frontmatter with name and description

In contrast, skills installed directly in ~/.claude/skills/ do appear in the autocomplete menu.

Steps to Reproduce

  1. Create a local marketplace with a plugin containing a skill:

``
my-marketplace/
├── .claude-plugin/
│ └── marketplace.json
└── plugins/
└── my-plugin/
└── skills/
└── my-skill/
└── SKILL.md
``

  1. Register the marketplace in ~/.claude/settings.json:

``json
{
"extraKnownMarketplaces": {
"my-marketplace": {
"source": {
"source": "directory",
"path": "/path/to/my-marketplace"
}
}
},
"enabledPlugins": {
"my-plugin@my-marketplace": true
}
}
``

  1. Restart Claude Code
  1. Try typing /my-skill or /my-plugin:my-skill in the input - it doesn't appear in autocomplete
  1. However, the skill IS loaded and can be invoked via the Skill tool

Expected Behavior

Skills from marketplace plugins should appear in the slash command autocomplete menu, just like skills installed directly in ~/.claude/skills/.

According to the documentation, user-invocable defaults to true, which should make skills visible in the autocomplete menu.

Actual Behavior

  • Skills in ~/.claude/skills/ → ✅ Appear in autocomplete
  • Skills from marketplace plugins → ❌ Do not appear in autocomplete (but are loaded and functional)

Workaround

Creating a symlink from the marketplace skill to ~/.claude/skills/ makes it appear in autocomplete:

ln -s /path/to/marketplace/plugins/my-plugin/skills/my-skill ~/.claude/skills/my-skill

Environment

  • OS: macOS (Darwin 24.6.0)
  • Claude Code: Latest version

View original on GitHub ↗

This issue has 15 comments on GitHub. Read the full discussion on GitHub ↗