#Progressive disclosure on skill groups

1 messages · Page 1 of 1 (latest)

minor bronze
#

Is there a way to do progressive disclosure on skills? Like I have a document ingestion skill which dispatches to specific ingestors like PDF, epub and their techniques, but often it skips steps and goes directly to the concrete skills instead of the dispatcher. Is there a way to do progressive disclosure on those skills?

I know a skill specifically does progressive disclosure by just having the name and the description on the system prompt, but all of them are shown every time, which it seems that it confuses the model. I would like a way to hide skills behind the activation of one dispatcher skill.

#

I think it's just skill issue (haha) on my part

Perhaps that bunch of skills could be just references

wintry wren
#

there is not really a built-in “hidden child skills behind a dispatcher skill” feature right now

Hermes does progressive disclosure for loading the contents of a skill, but separate installed skills are still all exposed at the top level, so the model can skip past your dispatcher and go straight to pdf, epub, and similar skills

so your idea of turning those concrete ingestors into supporting references/scripts under one document-ingestion skill is probably the cleaner pattern here

in other words:

  • keep document-ingestion as the visible top-level skill
  • move pdf, epub, and technique-specific instructions into that skill’s references/scripts
  • let the dispatcher decide which internal reference to load next

the current built-in visibility controls are things like requires_*, fallback_for_*, and platform restrictions, but not hierarchical skill groups