Skip to content

Optimisation: 40 skills => less skills + references #82

@IgorWarzocha

Description

@IgorWarzocha

Hi! I love skills. But I also hate how they create issues for agents.

Context pollution is real and I can already see that some of skills included in the repo cross-reference other skills. Problem with this is that the top level skills all get loaded into <available_skills>, and 40 of them, added to any other skills that people use, will make for a really bad experience.

Obviously, one might say that not all of them need to be installed at once, but with how heavy the cross-references are, basically none of them are skippable.

Proposal:

Even if it costs some duplication, bundle the granular skills in a top level structure, with /references/ folder.

I believe this will save both the users and the devs a lot of headaches, and it will be easier for users to manage a situation where they might only need parts of the included skills.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions