Hi 👋,
I worked on the new gh skills installation flow for agent skills and there are two issues I wanted to bring to attention for this repo.
The first is that, if you are using installation directories, you can use less folders now as .agents/skills is fairly widely supported. Claude still does not support it, but 🤷 might as well encourage the standard.
The second is, right now you publish skills in installation directories, which I think is not an ideal way to publish them (awesome-copilot publishes both a plugins marketplace and agent skills in a more publisher centric way, and I'd love it if you'd consider it.
Why it matters to me:
The gh skills command can find skills in repos, but we omit the use installation directories explicitly, as they are used across GitHub for people sharing skills across team for their repos, and we allow for updates, attribution and pinning etc. by editing the frontmatter on installation (we strip it on publish too), but with a goal that if people copy or share skills installed with gh locally or via repos, they continue to get updates and reference the original source.
Publishing skills in directories for consumers of skills kind of breaks this contract (I can see it might be convenient dev loop, although gh can install local skills too, so that's not too hard to resolve).
It was mentioned to me here; https://github.com/orgs/community/discussions/192851 and also http://github.com/orgs/community/discussions/192851 is similar.
What we are planning to do is allow gh to install from a user-specified remote directory, so that these skills and others published like it can still be installed, but we are unlikely to promote it to a first class installation path due to the overlap between publication and installation.
🙏 thank you!
Hi 👋,
I worked on the new
gh skillsinstallation flow for agent skills and there are two issues I wanted to bring to attention for this repo.The first is that, if you are using installation directories, you can use less folders now as
.agents/skillsis fairly widely supported. Claude still does not support it, but 🤷 might as well encourage the standard.The second is, right now you publish skills in installation directories, which I think is not an ideal way to publish them (awesome-copilot publishes both a plugins marketplace and agent skills in a more publisher centric way, and I'd love it if you'd consider it.
Why it matters to me:
The
gh skillscommand can find skills in repos, but we omit the use installation directories explicitly, as they are used across GitHub for people sharing skills across team for their repos, and we allow for updates, attribution and pinning etc. by editing the frontmatter on installation (we strip it on publish too), but with a goal that if people copy or share skills installed withghlocally or via repos, they continue to get updates and reference the original source.Publishing skills in directories for consumers of skills kind of breaks this contract (I can see it might be convenient dev loop, although
ghcan install local skills too, so that's not too hard to resolve).It was mentioned to me here; https://github.com/orgs/community/discussions/192851 and also http://github.com/orgs/community/discussions/192851 is similar.
What we are planning to do is allow gh to install from a user-specified remote directory, so that these skills and others published like it can still be installed, but we are unlikely to promote it to a first class installation path due to the overlap between publication and installation.
🙏 thank you!