Skip to content

feat(curator): add hermes curator usage — all-skills usage view - #36727

Merged
teknium1 merged 1 commit into
mainfrom
hermes/curator-usage-cli
Jul 6, 2026
Merged

feat(curator): add hermes curator usage — all-skills usage view#36727
teknium1 merged 1 commit into
mainfrom
hermes/curator-usage-cli

Conversation

@teknium1

@teknium1 teknium1 commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds hermes curator usage — the user-facing surface for the all-skills usage telemetry shipped in #36701.

hermes curator status is curator-scoped: it only shows agent-created candidates. This new command lists every skill on disk — bundled built-ins and hub-installed included — so you can see how often each is actually used, independent of whether it's ever curated.

Command

hermes curator usage [--sort {activity,recent,name}] [--provenance {agent,bundled,hub}] [--json]
  • Default table is sorted by activity (most-used first), with a use / view / patch / act breakdown and an agent / bundled / hub provenance tag per row.
  • --provenance filters to one origin; --sort recent orders by last activity; --json emits the full usage_report() payload for scripting.
  • Header shows a quick tally: skills: N total (agent=… bundled=… hub=…).

Why

#36701 decoupled telemetry from curation (every skill now accrues usage counts) and added usage_report() + provenance() as a data layer, but left no way to view it. This closes that loop.

Validation

6 new tests (test_curator_usage.py): lists all provenances, activity-sort ordering, --provenance filter, --json shape, empty case, and argparse registration. Plus existing test_curator_status + test_skill_usage suites pass (53 total green). Wiring confirmed live: register_cli resolves usage_cmd_usage.

Infographic

hermes-curator-usage-all-skills-view

@github-actions

github-actions Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

🔎 Lint report: hermes/curator-usage-cli vs origin/main

ruff

Total: 0 on HEAD, 0 on base (➖ 0)

🆕 New issues: none

✅ Fixed issues: none

Unchanged: 0 pre-existing issues carried over.

ty (type checker)

Total: 9582 on HEAD, 9582 on base (➖ 0)

🆕 New issues: none

✅ Fixed issues: none

Unchanged: 4966 pre-existing issues carried over.

Diagnostics are surfaced as warnings — this check never fails the build.

@alt-glitch alt-glitch added type/feature New feature or request comp/cli CLI entry point, hermes_cli/, setup wizard telemetry Touches outbound telemetry, usage attribution, or analytics — needs opt-in gating before merge P3 Low — cosmetic, nice to have labels Jun 1, 2026

@mxnstrexgl mxnstrexgl left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated PR Review

Security Scan

  • ✓ No hardcoded secrets, injection sinks, unsafe deserialization, or dependency red flags found by this automated scan.

Code Quality

  • ✓ No blocking code-quality issues found by this automated scan.

Summary

Status: APPROVE — security findings: 0, quality suggestions: 0.

Automated review; raw diff content intentionally omitted.

Surfaces the usage_report()/provenance() data layer added in #36701 as a
user-facing CLI command. Unlike `hermes curator status` (scoped to
curator-managed agent-created candidates), `usage` lists every skill on disk
— bundled built-ins and hub-installed included — with per-skill use/view/patch
counts and an agent/bundled/hub provenance tag.

Flags: --sort {activity,recent,name}, --provenance {agent,bundled,hub} filter,
--json for machine-readable output.
@teknium1
teknium1 force-pushed the hermes/curator-usage-cli branch from 762b681 to 21a78b0 Compare July 6, 2026 11:51
@teknium1
teknium1 merged commit 586acf5 into main Jul 6, 2026
31 checks passed
@teknium1
teknium1 deleted the hermes/curator-usage-cli branch July 6, 2026 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/cli CLI entry point, hermes_cli/, setup wizard P3 Low — cosmetic, nice to have telemetry Touches outbound telemetry, usage attribution, or analytics — needs opt-in gating before merge type/feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants