← 返回 Skills 市场

EasyClaw Config Migration

Name: EasyClaw Config Migration
Author: sjingh

作者 sjinopenclaw · GitHub ↗ · v0.1.0 · MIT-0

cross-platform ✓ 安全检测通过

237

总下载

当前安装

版本数

在 OpenClaw 中安装

/install 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...

使用说明 (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.json unless 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.json and ~/.openclaw/openclaw.json exist, prefer a selective merge over wholesale overwrite.
Never overwrite ~/.openclaw/openclaw.json without creating a backup first.

安全使用建议

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.

功能分析

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.

能力评估

✓ 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.

如何使用

确保已安装 OpenClaw（本地或 Docker 部署）
在对话框中输入安装命令：/install easyclaw-config-migration
安装完成后，直接呼叫该 Skill 的名称或使用 /easyclaw-config-migration 触发
根据 Skill 的参数说明提供必要输入，即可获得结构化输出

版本历史

v0.1.0

Initial release: inspect and selectively migrate EasyClaw runtime config into OpenClaw with backup-aware merge helpers.

元数据

Slug easyclaw-config-migration

版本 0.1.0

许可证 MIT-0

累计安装 0

当前安装数 0

历史版本数 1

常见问题