Skip to content
Back to skills

Clawdbot Workspace Template Review

ASecurity

Compare a Clawdbot workspace against the official templates installed with Clawdbot (npm or source) and list missing sections to pull in, especially after upgrades.

  • 651 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added February 10, 2026
toolsnode

Works with

  • cli

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add sundial-org/awesome-openclaw-skills --skill clawdbot-workspace-template-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Clawdbot Workspace Template Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Clawdbot Workspace Template Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sundial-org-clawdbot-workspace-template-review/badge)](https://www.skillsdirectory.com/skills/sundial-org-clawdbot-workspace-template-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: clawdbot-workspace-template-review
description: Compare a Clawdbot workspace against the official templates installed with Clawdbot (npm or source) and list missing sections to pull in, especially after upgrades.
---

# Workspace Template Diff

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.

## Locate the official templates

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.

## Comparison workflow

1. Identify the workspace root (the user’s “our version” directory).
2. 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.

## Output format

Use the “missing section” format we used previously:
- File path
- Missing block(s)
- Suggestion + question to proceed

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…