You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our match predicates for when to load skills is based on crate dependencies. And, we are discussing discovering based on binary names in PATH - zulip.
For error-battery-pack, it's not such a big deal since we would expect to see error related dependencies. This lets us load skills via crate match.
However, i'm also working on skills for ci-battery-pack, which is more awkward since very few of them have corresponding crate dependencies. The pack is mostly CI templates. However, having skills for how to set up trusted publishing is very useful (since it requires actions on crates.io, etc).
Proposal
We should also respect battery-pack.toml as a skill source and then load from a given battery-pack's crates.io crate tarball.
This was proposed in relation to PATH dependencies in zulip
Activity
[-]Add support for discovering battery pack skills[/-][+]Add support for loading battery pack skills[/+]krushiraj commentedon Aug 19, 2026
Should we close this as #128 seems to address this