sui-move-project

Configure Sui Move projects with Move.toml editions and environments.

10|5|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/MystenLabs/skills --skill sui-move-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sui-move-project
Source: https://github.com/MystenLabs/skills/tree/main/sui-move-project
Command: npx skills add https://github.com/MystenLabs/skills --skill sui-move-project

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps you create, configure, and troubleshoot a Sui Move project when you hit common setup, dependency, publishing, upgrade, and edition/format errors.

Core Features & Use Cases

  • Move project bootstrapping: Choose the correct Sui Stack hello-world layout or create a new standalone Move package when explicitly requested.
  • Move.toml configuration & migrations: Apply the current Sui CLI v1.63+ format by removing legacy [addresses] and using [environments], while ensuring edition = "2024" and correct module declaration style.
  • Dependency, publishing, and upgrade troubleshooting: Resolve errors related to legacy Sui dependency declarations, missing/incorrect Published.toml, Move.lock stale state, and MVR dependency setup.
  • When to use: Use this when users ask about Move.toml/Published.toml/Move.lock, encounter edition mismatches, or see errors like “legacy system name”, “old dependencies”, “Cannot upgrade package without having a published id”, or environment-related build failures.

Quick Start

Ask the AI to explain what changed in your Sui Move project configuration and provide the exact Move.toml and environment adjustments needed to fix your specific build or upgrade error.

Frequently Asked Questions about sui-move-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a legacy system name error in my Sui Move.toml configuration?

To fix a legacy system name error in your Sui Move.toml, remove legacy `[addresses]` declarations and adopt the current Sui CLI v1.63+ format using `[environments]` with `edition = "2024"`.

Why does my Sui Move package fail to upgrade without a published id?

A Sui Move package upgrade fails without a published id when the `Published.toml` file is missing or incorrectly configured. Ensure this file is present and correctly generated to enable safe upgrades.

What is the correct Move.toml format for setting up a new Sui Move project?

The correct Move.toml format for a new Sui Move project uses `[environments]` instead of legacy `[addresses]`, sets `edition = "2024"`, and applies the current Sui CLI v1.63+ module declaration style.

How do I resolve stale Move.lock state and legacy Sui git dependency errors?

Resolve stale Move.lock state and legacy Sui git dependency errors by removing old Sui git dependency declarations from Move.toml and regenerating your dependencies to refresh the lock file.

Can I use MVR dependencies with my existing Sui Move package?

Yes, you can use MVR dependencies with your Sui Move package by applying the correct Move.toml configuration and resolving any legacy Sui dependency declarations that conflict with the MVR setup.

When do I need to migrate my Sui Move project to edition 2024?

You need to migrate your Sui Move project to edition 2024 when adopting the current Sui CLI v1.63+ format, which requires updating Move.toml environments and correcting module declaration syntax to resolve build failures.