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

Status Open
Maintainer reply None cached
Activity 16 comments · opened Jan 18, 2026

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 ↗

15 Comments

github-actions[bot] · 7 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/18365
  2. https://github.com/anthropics/claude-code/issues/17271
  3. https://github.com/anthropics/claude-code/issues/17524

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

mklobucaric · 7 months ago

Adding another data point: Even within the official superpowers@claude-plugins-official plugin (v4.0.3), autocomplete behavior is inconsistent:

Works: /brainstorming, /systematic-debugging, /test-driven-development
Doesn't work: /using-superpowers, /using-git-worktrees

All skills ARE listed in /help and work when typed fully. The autocomplete just doesn't surface them.

Environment: Claude Code 2.1.12, macOS

vinnymeller · 7 months ago

just confirming exact same behavior as @mklobucaric on CC v2.1.19

kylesnowschwartz · 7 months ago

Tested with a local plugin using --plugin-dir (not marketplace):

  • Commands in commands/*.md → ✅ appear in fuzzy finder
  • Skills in skills/*/SKILL.md → ❌ don't appear

Ruled out:

  • YAML quoting (quoted name: and description: fields)
  • Hyphens in skill names (tried plugindevguide vs plugin-dev-guide)
  • Plugin cache (cleared ~/.claude/plugins/cache/)
  • user-invocable: true frontmatter

Conclusion: The fuzzy finder appears to only index the commands/ directory for plugins, ignoring skills/ entirely. This contradicts the documentation stating that commands and skills are now unified.

Environment: Claude Code 2.1.19, macOS Darwin 24.6.0

boshu2 · 7 months ago

Additional data point (regression):

Confirmed on Claude Code v2.1.19, macOS Darwin 25.2.0.

Key finding: This is a regression for my plugin. Skills WERE appearing in autocomplete before an uninstall/reinstall cycle. After reinstalling:

  • claude plugin list shows plugin enabled ✓
  • claude plugin validate passes ✓
  • Skills execute correctly when typed directly (e.g., /vibe works) ✓
  • Skills appear in Claude's Skill tool context ✓
  • Skills do NOT appear in autocomplete ✗

Interesting: The superpowers plugin (installed from a different marketplace) shows in autocomplete fine. My plugin (agentops) with identical skills/*/SKILL.md structure does not.

This suggests the autocomplete index may not be rebuilt/refreshed properly after plugin reinstalls, or there's marketplace-specific behavior.

harigovindarajan · 7 months ago

I am seeing the same issue and I reckon the model used in the slash command/skills could be an issue

Tool search disabled for model 'claude-haiku-4-5-20251001': model does not support tool_reference blocks. This feature is only available on Claude Sonnet 4+, Opus 4+, and newer models.

burneyhoel-knsl · 7 months ago
I am seeing the same issue and I reckon the model used in the slash command/skills could be an issue Tool search disabled for model 'claude-haiku-4-5-20251001': model does not support tool_reference blocks. This feature is only available on Claude Sonnet 4+, Opus 4+, and newer models.

This is interesting.

I set export ANTHROPIC_DEFAULT_HAIKU_MODEL="claude-sonnet-4-5-20250929" in an attempt to force the index to use sonnet and the results where the same.

copyx · 7 months ago
Tested with a local plugin using --plugin-dir (not marketplace): Commands in commands/*.md → ✅ appear in fuzzy finder Skills in skills/*/SKILL.md → ❌ don't appear Ruled out: YAML quoting (quoted name: and description: fields) Hyphens in skill names (tried plugindevguide vs plugin-dev-guide) Plugin cache (cleared ~/.claude/plugins/cache/) user-invocable: true frontmatter Conclusion: The fuzzy finder appears to only index the commands/ directory for plugins, ignoring skills/ entirely. This contradicts the documentation stating that commands and skills are now unified. Environment: Claude Code 2.1.19, macOS Darwin 24.6.0

## Additional Evidence: Multiple plugins with both commands/ and skills/

Here are plugins that have both directories, which can be used to verify the bug consistently:

| Plugin | commands/ (✅ works) | skills/ (❌ broken) |
|--------|---------------------|---------------------|
| claude-md-management | 1 | 1 |
| hookify | 4 | 1 |
| Notion | 6 | 1 |
| plugin-dev | 1 | 7 |
| superpowers | 3 | 14 |
| session-wrap | 1 | 3 |

### Reproduction steps

  1. Install any of these plugins from the marketplace
  2. Type / followed by the plugin name (e.g., /hookify:)
  3. Observe that only commands/*.md files appear in autocomplete
  4. skills/*/SKILL.md entries are missing from autocomplete

### Expected vs Actual

  • Expected: Both commands and skills should appear in autocomplete
  • Actual: Only commands appear; skills are missing

This confirms that the bug is specifically in how skills/ directories are registered to the autocomplete system, while commands/ handling works
correctly.

harigovindarajan · 7 months ago

Thanks for confirming — yes, this does not appear to be model-related.

The issue seems to be specific to skills distributed via plugins. I narrowed this down by copying a skill (any skill originally distributed through a plugin) into the project/.claude/skills folder and restarting Claude.

Observed behavior:
• The skill copied into the project folder does appear in autocomplete.
• The same skill, from the plugin, does not appear in autocomplete.
• Running /skills confirms that both skills are available to Claude.

This suggests that autocomplete is not picking up skills that are distributed via plugins, even though they are successfully registered and invokable.

jaodsilv · 6 months ago

It seems to be working for me since 2.1.29, but not prior to this.

vinnymeller · 6 months ago

just updated, seems to be working as expected for me now too

davefollett · 6 months ago

I havent tried again yet, but its odd its not in the change log

https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md#2129

Also, are even numbers no longer being released? 2.1.24, 2.1.26, and 2.1.28 arent listed.

devondragon · 5 months ago

Additional data point on Claude Code v2.1.71, macOS Darwin 25.3.0

I maintain ccmagic, a Claude Code plugin with 40 skills distributed via marketplace. Confirming that plugin skills still do not appear in slash command autocomplete or resolve when typed directly.

What we tested

  • Plugin installed via marketplace (extraKnownMarketplaces in settings.json)
  • Plugin correctly cached at ~/.claude/plugins/cache/ccmagic/ccmagic/2.2.0/
  • All skills have user-invocable: true in frontmatter
  • /reload-plugins shows the plugin loaded: 17 plugin(s) · 11 command(s) · 31 agent(s)

Results

  • Typing /ccmagic:push"Unknown skill: ccmagic:push"
  • No ccmagic skills appear in / autocomplete at all
  • The model CAN see and invoke all 40 skills via the Skill tool (they appear in the system prompt's available skills list)
  • This confirms the issue is specifically in the client-side slash command resolver, not the model-side Skill tool

Impact

Because users can't invoke plugin skills via /, we had to remove disable-model-invocation: true from all 25 of our action skills (push, merge, deploy, etc.). Without the / path working, the only way for users to trigger these skills is to ask the model — which requires the model to be able to see them. This means we lost the ability to prevent auto-invocation of destructive skills.

See our tracking issue: https://github.com/devondragon/ccmagic/issues/9

Environment

  • Claude Code: 2.1.71
  • macOS Darwin 25.3.0
  • Plugin source: GitHub marketplace (devondragon/ccmagic)
FrankLedo · 5 months ago

One more note: It appears that the skills are available if you install on the command line instead of with /plugin

yurukusa · 5 months ago

Until marketplace skills get proper autocomplete support, here are workarounds:
Workaround 1 — Symlink plugin skills to the local skills directory:

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

Skills in ~/.claude/skills/ get autocomplete. Symlinks make the same skill appear in both the marketplace (for distribution) and the local directory (for autocomplete).
Workaround 2 — Invoke via the Skill tool directly:
Since the skills load correctly, you can invoke them by typing the full name or asking Claude:

Use the my-skill skill

or

/my-plugin:my-skill

The skill runs — it just won't autocomplete when you start typing /my.
Workaround 3 — Create a thin wrapper skill locally:

mkdir -p ~/.claude/skills/my-skill
cat > ~/.claude/skills/my-skill/SKILL.md << 'EOF'
---
name: my-skill
description: "Wrapper for marketplace my-skill"
---
Use the Skill tool to invoke `my-plugin:my-skill`.
EOF

This gives you autocomplete for a local skill that delegates to the marketplace skill. Slightly redundant but functional.

Showing cached comments. Read the full discussion on GitHub ↗