Modernize Move

Detects and modernizes outdated Move V1 syntax, patterns, and APIs to Move V2+. Use when upgrading legacy contracts, migrating to modern syntax, or convertin...

This skill appears to be a genuine Move modernization guide, but there are practical mismatches you should address before running it: - Missing runtime dependency: SKILL.md assumes the aptos/Move CLI (`aptos move test`) is available, but the skill metadata does not declare that binary. Ensure the aptos CLI (or equivalent move test runner) is installed and at the expected PATH before invoking the skill. - Undeclared skill dependency: The workflow will call a `generate-tests` skill if no tests exist; confirm that your agent has that skill available or provide tests yourself. The skill does not declare or bundle that dependency. - Powerful permissions: The skill requests Bash and file Write/Edit capabilities and will modify source files. Although it promises an analysis report and explicit user confirmation gates, you should: - Run it in a sandbox or feature branch, not directly on production code. - Back up the repository (or ensure version control) before applying changes. - Start with `syntax-only` (Tier 1) scope to see automated edits and test impact before permitting Tier 2/3. - Manually verify that `aptos move test` passes locally and inspect diffs after each tier. - Verify no unexpected config access: the skill may read project config files (Move.toml, test manifests). If you have secrets or CI credentials in the repo, review what the aptos CLI will access. If you cannot confirm the aptos CLI or the generate-tests skill availability, treat the omission as a blocker and request an updated skill manifest that lists those runtime dependencies explicitly.

Type: OpenClaw Skill Name: modernize-move Version: 1.0.0 The modernize-move skill is a legitimate utility designed to automate the refactoring of Move V1 smart contracts to Move V2+ syntax. It incorporates robust safety protocols, including mandatory test verification using 'aptos move test' (SKILL.md), a tiered transformation workflow to minimize risk, and explicit user confirmation gates (Gate 1) before any code modifications occur. The instructions in SKILL.md and the transformation logic in the reference files are strictly aligned with the stated purpose of structural modernization without introducing functional changes or malicious behavior.