Skip to content

[FEATURE]: Fine Control of Skill Discovery / HST #28485

Closed as not planned
Closed as not planned

Description

@yuichiinumaru

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

What: User can control levels of subdirectory or simply disable subdirectory lookup for skills.md files.
Opencode can be set to not look for external skills, but no switch available if I only want it look inside a specific folder level and NOT any subdirectory of it (sub-skills).

Why: Like so many, 'browser-harness' skill has 50+ domain-skills inside it, with main SKILL.md serving as a router / index (in short). This is done intentionally to prevent context blowup, while still leaving options/tools to agent.
When discovery find subdir skill.md files and inject into context, breaks scheme and crush tokens. Opencode afaik only harness to do this.

Solution: A little finer control of how/which skills are loaded would be sufficient.

Best version: While I understand not everyone adopts hierarchical skill trees (HST) as a standard, I advocate in favour of it fiercely. I dedicated many hours building them for when thousands of skills are needed, and it works beautifully. It's also simple, everyone can understand and build on top. (yes, it's somewhat Karpathy wiki related).

Suggestion:

  1. Index and inject only main skills front into context
  2. Instruct model about subskills existing in simplest terms
  3. Optional: add hidden subagent for skills w/ small model, maximum skill context budget (compressed), subagent passes compressed index to fit budget, response stored in cache, subagent only called again if index changed
  4. Optional: add field 'subskills' as part of main skill context, list names only (best with 3)

Activity

  1. github-actions commented on May 20, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

  2. yuichiinumaru commented on May 20, 2026

    @yuichiinumaru
    Author

    Partially

    This issue might be a duplicate of existing issues. Please check:

  3. github-actions commented on Jul 20, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions