[FEATURE] Allow custom skills to appear before built-in commands in the / menu

Resolved 💬 1 comment Opened May 30, 2026 by krishbiswas Closed Jul 3, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Power users who define custom skills spend most of their time invoking those skills via /, but built-in commands always appear first, pushing custom skills down the list.

Proposed Solution

Add an option to prioritise custom skills at the top of the / menu — either by default, or via a setting in .claude/settings.json.

  1. Surface custom skills before built-ins by default
  2. Add a preferCustomSkills: true setting to control ordering
  3. Allow manual ordering of skills in settings

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

  • I have 20+ custom skills covering daily workflows (meeting notes, status briefs, talking points,

team reviews, etc.)

  • Built-in commands I rarely use (e.g. /help, /clear) consistently appear above the skills I use

every session

  • This adds unnecessary scrolling and friction in a tool designed for speed

Additional Context

Impact - Low implementation effort, high daily-use quality-of-life improvement for power users.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗