Data Migration Planner
v1.0.0Plans and documents detailed data migrations, including schema mapping, ETL pipeline design, validation tests, rollback strategies, and runbook creation.
⭐ 0· 630·1 current·1 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The SKILL.md describes planning, schema mapping, ETL design, validation, and cutover runbooks which matches the 'Data Migration Planner' name. The skill requires no environment variables, binaries, or installs, which is proportionate for a planning/consulting tool.
Instruction Scope
Instructions are limited to producing migration plans, templates, and checklists. They do instruct the agent to 'inventory' source objects and record counts given source/target details — which implies the agent (or user) will provide or use data/system access. The SKILL.md does not instruct any explicit data collection, file reads, or transmission to external endpoints, but it also lacks explicit guidance about handling credentials, redacting sensitive data, or avoiding exfiltration. This is reasonable for a planning skill but worth noting for operational safety.
Install Mechanism
No install spec and no code files — instruction-only. Nothing will be written to disk or downloaded during install.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no unexplained or disproportionate credential requests.
Persistence & Privilege
Default privileges are used (always: false, model invocation enabled). The skill does not request permanent presence or system-level changes.
Assessment
This skill appears coherent and low-risk because it is instruction-only and does not request credentials or install code. Before using it in production: 1) Avoid pasting live production credentials into any agent UI unless you trust the agent runtime and have least-privilege credentials (use read-only, scoped accounts). 2) Prefer running discovery on anonymized or copy datasets when possible; redact PII/HIPAA-sensitive fields. 3) Confirm any data access the agent requests goes only to the stated source/target systems and not to external endpoints. 4) Use this skill for planning and runbooks, but implement actual migration steps in controlled tooling and monitored environments. If you need higher assurance, ask the publisher for details on how the agent uses collected data and how to safely provide credentials.Like a lobster shell, security has layers — review code before you run it.
data migrationvk974tcqg6kdctfyzea1v97b7f5813nzydatabasevk974tcqg6kdctfyzea1v97b7f5813nzydevopsvk974tcqg6kdctfyzea1v97b7f5813nzyetlvk974tcqg6kdctfyzea1v97b7f5813nzylatestvk974tcqg6kdctfyzea1v97b7f5813nzyschema mappingvk974tcqg6kdctfyzea1v97b7f5813nzy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.