I am experimenting with knowledge management, see
During a linting session i noticed my skill was verbose and inefficient so i thought:
"i wish i had a way to manage knowledge for skill....wait.lol, i do have it"
So my question is:
Did any of you tried to create a wrapper skill that route subskills when needed to prevent context bloating?
is the same principle over and over but i never applied to skills.