I've been testing runx as a governed runtime for agent skills, and one gap I keep hitting is verifying that a published skill package hasn't drifted from the SKILL.md contract it declares.
It would be useful to have a first-class verification workflow that:
- Derives a stable package digest from the checked-in skill folder
- Validates frontmatter fields (name, version, license, runner) at publish time
- Optionally signs or pins that digest in the registry entry
This would give consumers a reproducible way to with confidence that the skill they installed matches what was reviewed.
Happy to turn this into a proper RFC if helpful.
I've been testing runx as a governed runtime for agent skills, and one gap I keep hitting is verifying that a published skill package hasn't drifted from the SKILL.md contract it declares.
It would be useful to have a first-class verification workflow that:
This would give consumers a reproducible way to with confidence that the skill they installed matches what was reviewed.
Happy to turn this into a proper RFC if helpful.