← Back to Skills Marketplace
EasyClaw Config Migration
by
sjinopenclaw
· GitHub ↗
· v0.1.0
· MIT-0
237
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install easyclaw-config-migration
Description
Migrate settings from EasyClaw into OpenClaw by locating EasyClaw desktop/runtime config files, comparing them with ~/.openclaw/openclaw.json, and safely gen...
README (SKILL.md)
EasyClaw Config Migration
Locate three config sources before making changes:
~/Library/Application Support/@cfmind/easyclaw/easyclaw.json— EasyClaw desktop UI settings~/.openclaw/easyclaw.json— EasyClaw/OpenClaw bridge config with reusable runtime settings~/.openclaw/openclaw.json— active OpenClaw config
Most directly reusable settings live in ~/.openclaw/easyclaw.json. The desktop easyclaw.json is mostly UI state and usually does not map cleanly into OpenClaw.
Workflow
1. Inspect and compare
Run:
python3 scripts/report_easyclaw_config.py
This prints:
- which files exist
- redacted summaries
- fields that can be migrated automatically
- fields that are desktop-only / no direct OpenClaw equivalent
If you only need a report, stop here and summarize the findings.
2. Review the migration map
Read references/mapping.md when deciding what should be copied automatically versus left for manual review.
Default stance:
- copy only fields with clear semantic equivalents
- do not invent mappings for desktop-only UX settings
- preserve user changes already present in
~/.openclaw/openclaw.jsonunless the migration is explicitly requested
3. Apply a selective merge
Run:
python3 scripts/merge_easyclaw_config.py --apply
Behavior:
- create a timestamped backup of
~/.openclaw/openclaw.json - merge only supported fields from
~/.openclaw/easyclaw.json - print changed paths
Dry run first when practical:
python3 scripts/merge_easyclaw_config.py
4. Validate and summarize
After applying, read ~/.openclaw/openclaw.json or use normal OpenClaw validation/status commands if needed. Summarize:
- what was migrated
- what was intentionally skipped
- where the backup was written
Notes
- Treat tokens, secrets, and auth blobs as sensitive. Redact them in chat unless the user explicitly wants raw values.
- If only the desktop EasyClaw file exists, explain that most of it is app/window preference state and not the main OpenClaw runtime config.
- If both
~/.openclaw/easyclaw.jsonand~/.openclaw/openclaw.jsonexist, prefer a selective merge over wholesale overwrite. - Never overwrite
~/.openclaw/openclaw.jsonwithout creating a backup first.
Usage Guidance
This skill appears to do exactly what it says: inspect EasyClaw/OpenClaw config files and optionally apply a conservative merge. Before running --apply: 1) run the report script first (python3 scripts/report_easyclaw_config.py) and review its output; 2) confirm you want any auth token fields migrated (gateway.auth.token is in the auto-mappings); 3) keep the generated timestamped backup (the merge script creates one automatically); 4) if you have concerns, review the two included Python scripts yourself — they only read/write files under your home directory and do not contact external services. If you do not want tokens moved, do not run with --apply or edit the mapping in scripts/merge_easyclaw_config.py to remove token entries.
Capability Analysis
Type: OpenClaw Skill
Name: easyclaw-config-migration
Version: 0.1.0
The skill bundle is a legitimate utility for migrating configuration settings from EasyClaw to OpenClaw. It includes scripts (report_easyclaw_config.py and merge_easyclaw_config.py) that read local JSON configuration files, provide redacted reports of sensitive fields like tokens and secrets, and perform selective merges with automated backups. There is no evidence of data exfiltration, unauthorized network access, or malicious execution logic.
Capability Assessment
Purpose & Capability
Name/description, SKILL.md, mapping reference, and the two included scripts all focus on locating EasyClaw and OpenClaw config files in the user's home directory and performing a conservative selective merge. Required binaries/env/configs are none, which is consistent with a local file-merge tool.
Instruction Scope
Runtime instructions only tell the agent/operator to run the included report and merge scripts which: read specific files under the user's home directory, print redacted summaries, and optionally write a backup and updated ~/.openclaw/openclaw.json when --apply is used. The SKILL.md explicitly warns to redact secrets and to prefer dry runs. There are no instructions to read unrelated system files, contact external endpoints, or collect broad system context.
Install Mechanism
This is an instruction-only skill with included scripts and no install spec or remote downloads. Nothing is written to disk by an installer; the only writes happen when the user runs the provided merge script with --apply (explicit and documented).
Credentials
The skill requests no environment variables or credentials. It will read and (when applied) write config files under the user's home directory and may copy tokens present in those files (gateway.auth.token is included in the auto-mappings). Copying tokens is coherent with migration purpose but is sensitive behavior — the SKILL.md and scripts do redact output for reporting, which is appropriate. Users should verify they want auth tokens migrated before applying.
Persistence & Privilege
The skill is not always-enabled and is user-invocable only. It does not change other skills or global agent settings. The only persistent side-effects are backup creation and writing to ~/.openclaw/openclaw.json when the operator explicitly runs the script with --apply.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install easyclaw-config-migration - After installation, invoke the skill by name or use
/easyclaw-config-migration - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release: inspect and selectively migrate EasyClaw runtime config into OpenClaw with backup-aware merge helpers.
Metadata
Frequently Asked Questions
What is EasyClaw Config Migration?
Migrate settings from EasyClaw into OpenClaw by locating EasyClaw desktop/runtime config files, comparing them with ~/.openclaw/openclaw.json, and safely gen... It is an AI Agent Skill for Claude Code / OpenClaw, with 237 downloads so far.
How do I install EasyClaw Config Migration?
Run "/install easyclaw-config-migration" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is EasyClaw Config Migration free?
Yes, EasyClaw Config Migration is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does EasyClaw Config Migration support?
EasyClaw Config Migration is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created EasyClaw Config Migration?
It is built and maintained by sjinopenclaw (@sjingh); the current version is v0.1.0.
More Skills