Skill review
Skill fetch previews by default and does not write into the project. Use that boundary to inspect content, provenance, and effects before placing a SKILL.md in a selected directory.
Preview first
evolver skill fetch --asset <asset_id>
evolver skill fetch --query "release verification"
evolver skill fetch --signals validation,release
Evolver verifies the content-addressed asset_id again before writing. Stop if the received content does not match the ID; do not bypass verification through renaming or manual copying.
Review checklist
- The Skill addresses the current task rather than a loosely similar one.
- Instructions do not request unrelated directories, credentials, or personal data.
- Publishing, deletion, credit use, long-running processes, and external writes are disclosed.
- Commands, dependencies, and scripts have fixed sources without hidden downloads or obfuscation.
- Validation proves the requested outcome rather than command completion alone.
Write explicitly
evolver skill fetch --asset <asset_id> --write --out <dir>
The file is written to <dir>/skills/<name>/SKILL.md. Existing files are not overwritten by default. Use --force only after reviewing the diff and preserving the old version.
Validate after writing
Enable the Skill on a low-impact task first and inspect the actual read scope, commands, and output. On boundary violations, remove the new file or restore the previous version and record the failure in review and reuse evidence.
Related pages
EvoX Docs · Security · Asset trust