All 11 bundled skill packs (skills/wigolo*/SKILL.md) still carry metadata.version: 0.1.43-beta.2 in their YAML frontmatter — verified in the npm wigolo@0.2.1 tarball (package/skills/) and on main.
Users see the stale version in skill listings/agent UIs even though the server itself correctly runs 0.2.1. Functionally cosmetic: the CLI tracks skill currency by content hashes (assets/legacy-skill-hashes.json), not this field — but it is confusing ("skill reports old version after update").
Suggestion: derive the frontmatter version from the release tag at build/publish time (e.g. alongside scripts/gen-legacy-skill-hashes.mjs or in the release workflow) instead of hand-maintaining the string, so it can never drift from the actual release again.
All 11 bundled skill packs (
skills/wigolo*/SKILL.md) still carrymetadata.version: 0.1.43-beta.2in their YAML frontmatter — verified in the npmwigolo@0.2.1tarball (package/skills/) and onmain.Users see the stale version in skill listings/agent UIs even though the server itself correctly runs 0.2.1. Functionally cosmetic: the CLI tracks skill currency by content hashes (
assets/legacy-skill-hashes.json), not this field — but it is confusing ("skill reports old version after update").Suggestion: derive the frontmatter
versionfrom the release tag at build/publish time (e.g. alongsidescripts/gen-legacy-skill-hashes.mjsor in the release workflow) instead of hand-maintaining the string, so it can never drift from the actual release again.