Publish, upgrade, and deploy Sui Move packages with UpgradeCap governance.
npx skills add https://github.com/MystenLabs/skills --skill sui-publish
Please help me install this Agent Skill. Skill: sui-publish Source: https://github.com/MystenLabs/skills/tree/main/sui-publish Command: npx skills add https://github.com/MystenLabs/skills --skill sui-publish
Publishing, upgrading, and deploying Sui Move packages is error-prone because you must coordinate the right CLI commands, environment/network selection, UpgradeCap handling, and dry-run debugging so changes are compatible and production-safe.
sui move build before running sui client publish.sui client upgrade using the correct UpgradeCap, select the appropriate upgrade policy (compatible/additive/dependency-only), and optionally restrict or destroy the cap for immutability.test-publish for upgrades/testing, and use localnet for fast iteration.--dry-run for gas estimation and devInspectTransactionBlock to diagnose dry-run failures before signing or executing.Ask the skill to publish your Move package by first verifying your active environment and build, then running sui client publish and returning the package ID, UpgradeCap, and any init-created object IDs.
High-intent search queries and answers about installing and using this skill.
To publish a Sui Move package, verify your active environment and SUI balance, run `sui move build`, then execute `sui client publish` to deploy and retrieve your package ID, UpgradeCap, and init-created object IDs.
UpgradeCap governance authorizes `sui client upgrade` operations, requiring you to select an upgrade policy (compatible, additive, or dependency-only) and optionally restrict or destroy the cap to enforce immutability.
The best way to estimate gas for a Sui Move deployment is using the `--dry-run` flag with your publish or upgrade command to preview transaction costs without signing or executing.
Yes, you can use localnet for fast iteration when testing Sui Move package upgrades, and you can also use ephemeral `test-publish` workflows to validate changes before committing to a network deployment.
Your Sui Move dry-run fails due to incompatible upgrade changes or build errors, which you can diagnose using `devInspectTransactionBlock` to inspect the transaction block before signing or executing.
To re-publish a Sui Move package to a new network, switch your active CLI environment and run `sui client publish` again, ensuring you handle the new `Published.toml` behavior and retrieve the new package ID and UpgradeCap.
first-mover-twOrchestrate staged SUI Move package deployments across devnet, testnet, and mainnet.
SeventhOdyssey71Guide Sui developers through mainnet deployment with pre-flight checks and UpgradeCap policy selection.
readtheskillManage Solana multisig wallets via Squads Protocol with configurable approval thresholds.
GabeujinAnalyze .NET projects and plan upgrades to modern .NET versions.