Data Move
v1.0.0Deep data migration workflow—scope, mapping, validation, batching and ordering, dual-write and cutover, rollback, and reconciliation. Use when moving tenants...
⭐ 0· 76·0 current·0 all-time
by@clawkk
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (deep data migration) matches the SKILL.md content: stages, invariants, batching, cutover, rollback, and reconciliation are all appropriate for migrations.
Instruction Scope
The instructions are high-level runbook guidance and stay on-topic; however they explicitly assume performing privileged operations (DB writes, DNS/config flips, feature-flag toggles). The skill does not instruct the agent to read unrelated system files or secrets, but following the workflow in practice requires access to production infrastructure and human coordination.
Install Mechanism
Instruction-only skill with no install steps and no code files — lowest risk from installation. It mentions pairing with external tools (e.g., db-migrate) but does not pull or install them itself.
Credentials
No environment variables or credentials are declared, which is consistent for an instruction-only guide. Practically, executing the workflow requires database and infrastructure credentials; those are not requested or managed by the skill itself and must be provided separately with least privilege.
Persistence & Privilege
The skill is not always-on and is user-invocable. It does not request persistent presence or modify other skills/configurations.
Assessment
This SKILL.md is a sensible checklist and runbook for migrations, but it is guidance only — it does not execute anything or declare credentials. Before using it: (1) ensure any agent, human, or automation you run against production has least-privilege DB and infra credentials and that those credentials are stored and audited securely; (2) practice the full runbook (including rollback) in staging with realistic volumes; (3) require human sign-off before any cutover or DNS/feature-flag flips; (4) schedule reconciliation and monitoring as described and verify checksum/aggregate checks rather than trusting batch completion; and (5) if you plan to pair this guidance with automation (db-migrate or custom scripts), vet those tools' install sources and code separately. If you want the agent to perform actions automatically, treat granting DB/infra access as a high-risk decision and restrict autonomous invocation until you’ve tested controls.Like a lobster shell, security has layers — review code before you run it.
latestvk977gc746zmc6ck8j7r7ds707s83px6q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.