data-migration-and-platform-cutover — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited data-migration-and-platform-cutover (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when the system is changing platforms or major architectural boundaries. It helps agents plan parallel runs, compatibility layers, validation, and safe cutover rather than treating migration as a one-day switch.
Do not start cutover work without a rollback and validation path.
Include:
Common patterns:
Typical gates:
Rollback should be executable, not a sentence in a plan.
| Rationalization | Reality |
|---|---|
| "We can switch everything at once during a quiet window." | Hidden downstream dependencies often make big-bang cutovers fragile. |
| "If the data matches once, we are done." | Cutovers also need sustained operational parity and recovery confidence. |
| "We can keep the old path around indefinitely just in case." | Zombie dual paths create confusion and extra risk unless retired deliberately. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.