How should OpenSpace organize skills at scale? hierarchy, routing, and personalization

[Dennis-yxchen]

As raised in #38, and from patterns we've been noticing ourselves, a flat skill space may become harder to scale over time.

As the number of skills grows:

• The agent may get more confused about which skill to use
• Token usage may increase because more skills need to be considered

This raises a broader design question for OpenSpace:

How should skills be organized at scale?

Possible directions include:

• a more hierarchical skill system
• more personalized skill views for different users
• or a combination of both
• other ideas

This feels relevant not only for the current issue, but also for OpenSpace’s longer-term roadmap as the skill ecosystem keeps growing.

Curious what others think.

CC @kevbook — would love your thoughts, and welcome everyone else to join the discussion as well :-)