Problem
The Critical Requirements section says:
mo:base library — deprecated; use mo:core
But there is no link to the migration guide that documents the module and function mapping — which modules were renamed, which functions were renamed or removed, and what the mo:core equivalents are.
Without this link, agents must guess which mo:core module and function replaces each mo:base call. Common mistakes include using mo:base/HashMap after switching to mo:core (should be mo:core/Map), and calling removed functions by their old names.
Proposed Change
Extend the Critical Requirements entry to include the migration guide link:
Before:
mo:base library — deprecated; use mo:core
After:
mo:base library — deprecated; use mo:core (see the base→core module and function mapping guide)
The guide documents the complete module and function mapping — both renamed modules and renamed/removed functions.
Context
Identified during eval runs for icskills PR dfinity/icskills#194. Agents consistently use correct module names when the skill explicitly lists them, but when relying on training knowledge alone they often keep mo:base import paths or use non-existent mo:core APIs.
Related icskills issues: #6155, #6156, #6157, #6158, #6159.
Problem
The Critical Requirements section says:
But there is no link to the migration guide that documents the module and function mapping — which modules were renamed, which functions were renamed or removed, and what the mo:core equivalents are.
Without this link, agents must guess which mo:core module and function replaces each mo:base call. Common mistakes include using
mo:base/HashMapafter switching to mo:core (should bemo:core/Map), and calling removed functions by their old names.Proposed Change
Extend the Critical Requirements entry to include the migration guide link:
Before:
After:
The guide documents the complete module and function mapping — both renamed modules and renamed/removed functions.
Context
Identified during eval runs for icskills PR dfinity/icskills#194. Agents consistently use correct module names when the skill explicitly lists them, but when relying on training knowledge alone they often keep
mo:baseimport paths or use non-existentmo:coreAPIs.Related icskills issues: #6155, #6156, #6157, #6158, #6159.