openclaw-migration

Guides the renaming of the Clawd project to OpenClaw by detailing file moves, updates, testing, and documentation steps for consistent migration.

Security Scan

This instruction-only skill is internally consistent: it documents a repository rename/migration playbook and does not request credentials, installs, or other unrelated privileges.

Purpose & Capability

The skill name and SKILL.md describe a repo migration (Clawd → OpenClaw) and the instructions match that purpose. Minor mismatch: the README tells the agent to run pnpm scripts (tests, lint, build) but the skill metadata lists no required binaries—pnpm should be available in the environment for the steps to work.

Instruction Scope

Instructions stay within the stated scope: inventorying repo layout, renaming/copying directories, updating references, verifying tests/CI, and documenting changes. They explicitly reference repository files (AGENTS.md, SOUL.md, skills.json, etc.), which is appropriate for a migration but means the agent will read and modify repo metadata/persona files as part of the workflow.

Install Mechanism

No install spec or code files are present; this is instruction-only, so nothing is downloaded or written to disk by an installer. Low install risk.

Credentials

The skill requests no environment variables, credentials, or config paths. That's proportionate for a documented migration checklist. (It does refer to CI/CD providers and local tooling but does not request tokens or secrets.)

Persistence & Privilege

The skill is not marked 'always' and is user-invocable; it does not request persistent presence or system-wide config changes beyond the repository-level edits implied by the migration.

Assessment

This is a straightforward repo migration playbook; it does not ask for credentials or install code. Before using it: ensure pnpm (and other local tooling) is available if you plan to run the commands; run the migration in a feature branch and open a PR so changes can be reviewed; make backups or archive the old directory as recommended; double-check CI/CD and secret references after renaming (CI secrets are not requested by this skill but workflows may need manual updates). If you want the agent to perform automated renames, restrict its write permissions and review diffs manually before merging.

SKILL.md - OpenClaw Migration

Purpose

When the workspace is in the middle of renaming the Clawd project to OpenClaw, this skill lives in the repo so everyone—human or helper—can follow the same migration playbook. It outlines what gets moved, renamed, and tested as we align the codebase, docs, and tooling with the new brand.

When to use

• The human asks for a migration status, plan, or checklist (e.g., “How do we move Clawd to OpenClaw?”).
• You are about to rename directories, update config files, or explain where the old artifacts live.
• A new contributor needs consistent steps so renaming doesn’t break builds or automation.

Migration playbook

1. Inventory current layout: clawdbot/ is the existing application root, containing src/, apps/, docs/, skills/, package.json, tests, and tooling. The repo root also hosts the agent metadata (AGENTS.md), personality files (SOUL.md, MEMORY.md, etc.), and artifacts like skills.json.
2. Create the OpenClaw root: either rename clawdbot/ → openclaw/ or copy its contents into a new openclaw/ branch. Preserve hidden files (.github, .agent, .ox configs, etc.) and ensure package.json, pnpm-workspace.yaml, and lockfile stay in sync.
3. Update references: search for “Clawd” (case-sensitive) inside docs, READMEs, skill definitions, config files, CI workflows, and rename it to “OpenClaw.”
   • Pay special attention to README-header.png, docs/*.md, AGENTS.md, and SOUL.md (the persona description may mention Clawd by name).
   • Update any CLI/npm run scripts that reference clawdbot paths.
4. Move common metadata: decide where AGENTS.md, SOUL.md, MEMORY.md, skills.json, skills/ should live relative to the new app root. Keep human-facing files at the repo root if they drive onboarding (the main persona, heartbeat, identity, etc.).
5. Verify tooling: rerun pnpm test, pnpm lint, and any docs building scripts from within openclaw/ so the new layout works with existing CI.
6. Update documentation: mention the migration in README.md (root and inside the app) so contributors know the repo now houses OpenClaw. Document how to run the app from the new directory.
7. Clean up artifacts: remove or archive the old clawdbot/ directory once the new structure is stable, or keep a reference README explaining the archive for traceability.

Validation

• package.json scripts (dev, build, bootstrap) still resolve to the right folders.
• pnpm workspace references and tsconfig paths point to openclaw/ (if renamed).
• skills.json still lists the correct skill directories and versions.
• CI/CD workflows (GitHub Actions, Fly, Render) use the new name in their config.

Communication

• Share this SKILL.md with reviewers during the migration review, so they can confirm each step.
• When sending summaries to Ivan, include a list of moved files and new openclaw/ entrypoints.

Triggers

• Any “migration”, “rename”, or “Clawd → OpenClaw” question from Ivan.
• When prepping a release that should ship under the OpenClaw brand.