Skip to content

Rank the slash menu by the skills you actually use - #73704

Merged
OutThisLife merged 2 commits into
mainfrom
bb/slash-skills-by-usage
Jul 29, 2026
Merged

Rank the slash menu by the skills you actually use#73704
OutThisLife merged 2 commits into
mainfrom
bb/slash-skills-by-usage

Conversation

@OutThisLife

Copy link
Copy Markdown
Collaborator

The / menu listed skills alphabetically, which means the ordering carries no information about what the user actually does. On a 200-skill install that buries the handful of skills someone invokes daily under a wall of skills that shipped with Hermes and were never opened — /research-paper-writing (0 activity) sorted above /research (60 invocations).

Hermes already tracks per-skill activity in ~/.hermes/skills/.usage.json and surfaces it on the Capabilities page; the slash menu just never saw it. This plumbs that number into the command catalog and ranks on it.

Gateway. commands.catalog gains a skills map keyed by slash command, each entry carrying usage (use + view + patch, the same count Capabilities shows) and origin (hub / bundled / local, matching /api/skills provenance). Both come from sidecar files read once per catalog build. The field is additive — older clients ignore it — and an unreadable sidecar degrades to zero usage rather than failing the catalog.

Desktop. The Skills section sorts most-used first, A–Z within a tie. On a bare / — browsing, not searching — bundled skills with no recorded activity are dropped: shipped-and-ignored is noise, but the user's own unused skills and anything the catalog hasn't classified stay. Typing a query only reorders and never hides, because a search that drops a match is broken. The usage map rides along on the catalog response the popover has already fetched, so ranking a typed query costs no extra round trip.

Measured against a real 200-skill install: 125 skills used at least once, 75 never — 38 of which are bundled and now stay out of the browse list.

The catalog advertises every skill command but nothing about which ones
the user actually reaches for, so consumers can only sort them
alphabetically. Add a `skills` map keyed by slash command carrying the
activity count and origin (hub / bundled / local) already tracked in the
skills sidecars, read once per catalog build.

Additive: older clients ignore the field, and an unreadable sidecar
degrades to zero usage rather than failing the catalog.
The `/` popover listed skills alphabetically, so on a 200-skill install
the ones invoked daily sat below a wall of skills that shipped with
Hermes and were never opened — /research-paper-writing (never used)
outranked /research (60 invocations).

Sort the Skills section most-used first, A-Z within a tie, and on a bare
`/` drop bundled skills with no recorded activity. Typing a query keeps
every match: a search that hides a result is broken, so a typed `/re`
only reorders.
@OutThisLife
OutThisLife enabled auto-merge July 29, 2026 00:18
@github-actions

github-actions Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

૮ >ﻌ< ა ci review

ran on 959d299

ℹ️ Info

Desktop E2E visual evidence · View test artifacts · View job

1 visual diff.

inline evidence is publishing...

@OutThisLife
OutThisLife merged commit 9b6d910 into main Jul 29, 2026
45 checks passed
@OutThisLife
OutThisLife deleted the bb/slash-skills-by-usage branch July 29, 2026 00:20
@alt-glitch alt-glitch added type/feature New feature or request P3 Low — cosmetic, nice to have comp/desktop Electron desktop app (apps/desktop/*) comp/tui Terminal UI (ui-tui/ + tui_gateway/) tool/skills Skills system (list, view, manage) labels Jul 29, 2026
randlee pushed a commit to randlee/hermes-agent that referenced this pull request Aug 11, 2026
…ls-by-usage

Rank the slash menu by the skills you actually use
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/desktop Electron desktop app (apps/desktop/*) comp/tui Terminal UI (ui-tui/ + tui_gateway/) P3 Low — cosmetic, nice to have tool/skills Skills system (list, view, manage) type/feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants