Skip to content

Clarify whether auxiliary.skills_hub is reserved or stale #40703

@lsaether

Description

@lsaether

Problem or Use Case

auxiliary.skills_hub is exposed like a configurable auxiliary LLM slot, but I can't find a runtime call site using call_llm(task="skills_hub") or async_call_llm(task="skills_hub").

Current code appears to route Skills Hub through deterministic/library paths (tools/skills_hub.py + hermes_cli/skills_hub.py), so changing auxiliary.skills_hub.provider/model looks like a no-op.

Proposed Solution

Clarify the intended status of this slot:

  1. reserved for a future LLM-backed Skills Hub operation,
  2. an incomplete/dropped feature from the aux-client migration, or
  3. stale config/UI/docs surface that should be removed.

If reserved, a short comment/docs note would help. If stale, remove it from DEFAULT_CONFIG["auxiliary"], aux model pickers, docs, and the plugin reserved built-in aux keys.

Notes

Related precedent: session_search was removed from aux config after PR #27590 made it DB-backed/no-LLM, and PR #30382 cleaned up the stale picker slot.

Feature Type

Configuration option / developer experience

Scope

Small

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Low — cosmetic, nice to havearea/configConfig system, migrations, profilestype/featureNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions