What problem does it solve? Motoko developers on the Internet Computer need consistent toolchain versions, dependency management, and reliable canister builds without relying on dfx. This Skill provides an opinionated workflow for configuring mops.toml, pinning moc and lintoko versions, managing packages, and running checks and builds. ## Core Features & Use Cases - Toolchain Pinning: Pin moc, lintoko, and pocket-ic versions in mops.toml so every build uses the same compiler. - Dependency Management: Add, remove, update, and sync Motoko packages with mops.lock tracking, using mo:core instead of the deprecated mo:base. - Canister Checks and Builds: Run mops check with stable-variable compatibility verification against deployed .most baselines, lint with lintoko, and build wasm, .did, and .most artifacts. - Use Case: After cloning a Motoko canister project, run mops install, pin the latest moc toolchain, add the core package, then run mops check to verify types, stable compatibility, and lint before building deployable wasm. ## Quick Start Ask the assistant to set up a new Motoko project with mops, pin the latest moc toolchain, add the core dependency, and run mops check on the backend canister.
