Skill versions
A controlled Skill version is defined by its source asset ID, the actual SKILL.md content, and its installation path. Preview before updating; overwriting a same-name file is not an automatic upgrade.
Inspect a candidate version
evolver skill fetch --asset <asset_id>
Record the asset ID, source, summary, and content diff. Evolver revalidates content addressing before writing, and existing files are not overwritten by default.
Install or update
evolver skill fetch --asset <asset_id> --write --out <dir>
evolver skill fetch --asset <asset_id> --write --out <dir> --force
Use --force only after reviewing the diff and preserving the current file. Keep the Skill directory in Git or a separately versioned backup and record the asset ID in the change history.
Version record
skill name
installed asset_id
source and fetched time
target directory
reviewer and validation result
previous asset_id or backup revision
Roll back
Stop using the new version, restore the last validated SKILL.md, and rerun the original task and validation. The verified skill fetch flow does not provide a general recycle-bin recovery feature, so rollback depends on a file or repository revision preserved in advance.
Remove
Check projects, automations, and documentation for references before deleting a Skill file. Deleting the local file does not revoke the network asset; revoke trust separately when the asset itself is no longer acceptable.
Related pages
EvoX Docs · Administration · Asset governance