Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Developer Tools
openclaw-migration
Guides the renaming of the Clawd project to OpenClaw by detailing file moves, updates, testing, and documentation steps for consistent migration.
skill openclawclawhub Free
Guides the renaming of the Clawd project to OpenClaw by detailing file moves, updates, testing, and documentation steps for consistent migration.
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- chenyuan99
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
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
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. 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. 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. 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.). Verify tooling: rerun pnpm test, pnpm lint, and any docs building scripts from within openclaw/ so the new layout works with existing CI. 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. 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.
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md