openclaw-migrationGuides the renaming of the Clawd project to OpenClaw by detailing file moves, updates, testing, and documentation steps for consistent migration.
Install via ClawdBot CLI:
clawdbot install chenyuan99/openclaw-migrationWhen 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.
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.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.README-header.png, docs/*.md, AGENTS.md, and SOUL.md (the persona description may mention Clawd by name).npm run scripts that reference clawdbot paths.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.).pnpm test, pnpm lint, and any docs building scripts from within openclaw/ so the new layout works with existing CI.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.clawdbot/ directory once the new structure is stable, or keep a reference README explaining the archive for traceability.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.openclaw/ entrypoints.Generated Mar 1, 2026
A software development team is renaming an internal tool from 'Clawd' to 'OpenClaw' to align with a new open-source initiative. They need a structured migration plan to update code, documentation, and configurations without disrupting ongoing development or CI/CD pipelines. This ensures consistency across the codebase and prevents build failures during the transition.
A new engineer joins a project mid-migration and needs clear steps to understand the renamed directories and updated references. The skill provides a checklist for navigating the codebase, running tests, and contributing effectively, reducing confusion and onboarding time while maintaining code quality.
An organization is updating its continuous integration and deployment workflows to reflect the new 'OpenClaw' brand. The skill guides the team in modifying GitHub Actions, Fly, and Render configurations, verifying that scripts and paths point correctly to the renamed structure to ensure seamless deployments.
A technical writer is tasked with updating all project documentation, including READMEs, AGENTS.md, and SOUL.md, to reflect the 'OpenClaw' name. The skill outlines steps to search for and replace references, ensuring documentation accuracy and consistency for users and contributors.
Organizations adopt this skill to manage rebranding efforts for open-source tools, offering consulting or premium support services. Revenue is generated through subscription-based access to migration tools, documentation templates, and expert guidance, helping clients avoid downtime and errors.
IT consulting firms use this skill to provide structured migration services for large enterprises renaming internal software projects. Revenue comes from fixed-price contracts or hourly billing for planning, execution, and validation, ensuring compliance and minimal disruption to business operations.
Companies integrate this skill into their developer platforms or IDEs as a feature for automated code refactoring and migration. Revenue is generated through licensing fees for the tool, with additional income from premium analytics and support for complex migration scenarios in team environments.
đź’¬ Integration Tip
Integrate this skill with version control systems like Git to track changes during migration, and use automated testing tools to validate updates before deployment, reducing manual errors.
Transform AI agents from task-followers into proactive partners that anticipate needs and continuously improve. Now with WAL Protocol, Working Buffer, Autonomous Crons, and battle-tested patterns. Part of the Hal Stack 🦞
Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawdhub CLI.
Clawdbot documentation expert with decision tree navigation, search scripts, doc fetching, version tracking, and config snippets for all Clawdbot features
Interact with Moltbook social network for AI agents. Post, reply, browse, and analyze engagement. Use when the user wants to engage with Moltbook, check their feed, reply to posts, or track their activity on the agent social network.
OpenClaw CLI wrapper — gateway, channels, models, agents, nodes, browser, memory, security, automation.
MoltGuard — runtime security plugin for OpenClaw agents by OpenGuardrails. Helps users install, register, activate, and check the status of MoltGuard. Use wh...