Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Compare a Clawdbot workspace against the official templates installed with Clawdbot (npm or source) and list missing sections to pull in, especially after upgrades.
Compare a Clawdbot workspace against the official templates installed with Clawdbot (npm or source) and list missing sections to pull in, especially after upgrades.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
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.
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.
Use this skill when the user wants to compare their workspace .md files (AGENTS, SOUL, USER, IDENTITY, TOOLS, HEARTBEAT, etc.) against the official Clawdbot templates, then review missing sections and decide what to add.
Find the installed Clawdbot source root: If clawdbot is installed via npm/pnpm globally: command -v clawdbot If it points into .../node_modules/.bin/, resolve to the sibling node_modules/clawdbot Or use npm root -g / pnpm root -g and look for clawdbot/ If Clawdbot runs from source, use that checkout root (must contain package.json). Templates live at: <clawdbot-root>/docs/reference/templates/ If you can’t find the source root, ask the user where their Clawdbot is installed.
Identify the workspace root (the user’s “our version” directory). For each template file in docs/reference/templates (skip *.dev.md): Open the official template and the workspace file with the same name. Ignore template frontmatter (--- block) and any “First Run”/“Bootstrap” sections. Compare the remaining sections and list any missing blocks. Helpful commands (use ad‑hoc CLI tools like diff): ls <clawdbot-root>/docs/reference/templates sed -n '1,200p' <clawdbot-root>/docs/reference/templates/AGENTS.md sed -n '1,200p' <workspace>/AGENTS.md diff -u <clawdbot-root>/docs/reference/templates/AGENTS.md <workspace>/AGENTS.md When reporting diffs: Show the missing sections verbatim from the official template. Explain briefly why they matter, then ask whether to add them. Move file by file; skip files that only differ by frontmatter or bootstrap content.
Use the “missing section” format we used previously: File path Missing block(s) Suggestion + question to proceed
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.