[FEATURE] Use # prefix for skills to distinguish from / commands

Status Closed — not planned
Maintainer reply None cached
Activity 15 comments · opened Jan 12, 2026 · closed Feb 28, 2026

Problem

Currently, both built-in commands and skills are invoked using the / prefix (e.g., /help, /commit). This creates ambiguity:

  • Users can't quickly tell if something is a built-in command or a user-defined skill
  • Both are highlighted the same way (blue) in the terminal, providing no visual distinction
  • As the ecosystem grows with more plugins and skills, this confusion will increase

Proposed solution

Credits to @mrgoonie - he first proposed this idea here.

  1. Use # prefix for skills: Change skill invocation from /skill-name to #skill-name
  • /help, /clear, /compact → remain as / (built-in commands)
  • /commit, /code-review, /create-pr → become #commit, #code-review, #create-pr (skills)
  1. Different syntax highlighting: Use a distinct color for # skills
  • Built-in commands (/): Keep current blue highlighting
  • Skills (#): Use a different color (e.g., purple, orange, or green) to visually distinguish them

Alternatives considered

  • Use a different symbol like @ or !: # feels more natural and is commonly associated with tags/categories
  • Add a prefix like /skill:commit: More verbose and less ergonomic
  • Status quo: Keeping both as / works but reduces discoverability and clarity

Priority

Medium

Category

Interactive mode (TUI)

View original on GitHub ↗

15 Comments

mrgoonie · 7 months ago

thanks mate, really appreciate this! 🙏

PaulRBerg · 7 months ago

No prob @mrgoonie - I generated the issue using my /oss:create-cc-issue command/skill. check it out!

thieung · 7 months ago

Up

huyhoangnhh98 · 7 months ago

Up

PaulRBerg · 7 months ago

@thieung @huyhoangnhh98 make sure to thumbs up 👍 the issue so that Anthropics detects activity

brentgreeff · 7 months ago

I think this is reasonable - but I would strongly suggest one addition.
at the moment - skills cannot be nested in directories - but commands can.

Allowing skills to be invoked from the command menu - solved a problem I had already solved:

.claude/commands/design/fal.md

---
description: fal.ai image generation (credentials, usage)
skill: .claude/skills/fal-context
---
Load the fal skill for image generation with fal.ai.

Then I had a SKILL.md that contained the meat and potatoes.

At the moment I am using this pattern with user-invocable: false - in the skill frontmatter.

Personally I think skills are kinda pointless. Have you ever tried to get claude to load a skill? - u have to be pretty specific before it clues up.
Thats why i create commands for everything.

If skills can be nested in directories - AND - they work just like commands - then lets do it - but... how about we just call them plugins ? - two thing that are the same but diff names, diff directories? - doesnt sound like this went through a planning meeting.

Also can we go back to the old command sort order? - where project-specific commands come up first in the / menu?

mrgoonie · 7 months ago

I dont know why but I have a feeling that they will get rid of commands soon 😂

PaulRBerg · 7 months ago

@mrgoonie indeed. I noticed that slash commands are executed withthe Skill() tool now, and Claude refers to them as skills.

PaulRBerg · 7 months ago
how about we just call them plugins ?

Plugins are already a separate concept:

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

two thing that are the same but diff names, diff directories? - doesnt sound like this went through a planning meeting.

See and thumbs up https://github.com/anthropics/claude-code/issues/16900

brentgreeff · 7 months ago
Plugins are already a separate concept:

I know, - https://github.com/getskillsdev/fit-skills ( thats mine )

but what is the fundamental difference between ( global ) - user-space - commands/skills and plugins?

Plugins have install mechanism that links to git repos. user-space don't have that.

Moving a plugin in my global-space to a plugin is just a matter of packaging.

If I compare it to the Ruby world - a gem is a gem. it could be a local private gem, or a hosted gem.

I just hope Anthropic thinks this though carefully before nixing commands or skills. - a LOT of people are putting a huge amount of effort into the ecosystem and if Anthropic keeps pulling the rug from under them its going to lose a lot of contributors. I have lost about 50 hours with changes to how command and skills work in the last 6 weeks. The worst part I think - is how claude seems clueless to these changes - stuff just stops working - and you have to explicitly ask claude to web-search its changelog - otherwise it just hallucinates nonsense.

PaulRBerg · 7 months ago

Alternatively, you could use $ (dollar sign) as a prefix. This is what Codex CLI does, and the UX is quite nice:

<img width="1495" height="236" alt="Image" src="https://github.com/user-attachments/assets/5ee9ae22-5169-48c5-bdc2-8dc81571b453" />

github-actions[bot] · 6 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

PaulRBerg · 6 months ago

Please reopen

mrgoonie · 6 months ago
Please reopen

I don't think they care 😂

github-actions[bot] · 5 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.