Open
Conversation
Formalizes the April 18 decision to permit type: "archive" entries in skill://index.json as a server-side packaging optimization, reinstating symmetry with the Agent Skills discovery RFC.
Member
Author
|
Lets leave this one open until 2026-04-29 (following 10-day lazy consensus per working group governance, in case anyone has any late breaking comments). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Recent discussions around this topic made it unclear if we actually want to support this in the skills extension SEP or not. Adding a formalized decision record for this so we can make sure what we have in the SEP lines up with our latest thinking.
Edit: also opened this: #82
Related to this ^^ I was thinking about whether this adds a filesystem requirement. I'm assuming that hosts without a local filesystem would unpack archives in memory into the same
skill://<skill-path>/<file-path>namespace that individual-file distribution populates directly. So the filesystem-agnostic stance of the current SEP seems compatible with either distribution type.