One question I have on the `tool boundary` methodology -- does this penalize a skill for having any sort of scripts/ embedded? I've found it really helpful to take larger skills, like ones I've built at Snyk which handle data processing, and encode the process in the SKILL.md, but also ship it with python/go code in scripts/ to deterministically handle a lot of data validation/etc. For data analysis skills I feel like it's really hard to just encode teaching logic without costing a fortune in inference.
Nice project!
One question I have on the `tool boundary` methodology -- does this penalize a skill for having any sort of scripts/ embedded? I've found it really helpful to take larger skills, like ones I've built at Snyk which handle data processing, and encode the process in the SKILL.md, but also ship it with python/go code in scripts/ to deterministically handle a lot of data validation/etc. For data analysis skills I feel like it's really hard to just encode teaching logic without costing a fortune in inference.