Skill Version Manager

This skill is conceptually coherent for managing semver and changelogs, but there are important mismatches and operational risks to address before installing: - Clarify required tools and permissions: SKILL.md uses git and clawhub (network publishing). The registry metadata currently declares no required binaries and no network permission — confirm that git and clawhub are available in the runtime and that network/publish permissions are intended. - Credential handling: Publishing normally needs authenticated credentials (git credentials, clawhub token). The skill lists no env vars; ensure any tokens used are scoped and stored securely, and that you know which account will be used to publish. - Review scope of file access: The skill can modify SKILL.md and other files under skills/. Make sure the agent's file permissions are limited to the intended repository/path and that backups or CI gates exist before pushing. - Audit publish workflow: The SKILL.md describes automated packaging and publish steps. Require manual review/explicit approval or enforce CISO gating in your process if you cannot fully trust autonomous publishes. - Minimal recommended changes before use: update metadata to list required binaries (git, clawhub), set network permission if publishing is needed, and document the exact authentication mechanism and the network endpoints used by clawhub. If these clarifications are provided and safeguards (credential scoping, manual approval gates) are in place, the skill can be used; until then treat it with caution.