clawdbot-workspace-template-review
Compare a Clawdbot workspace against the official templates installed with Clawdbot (npm or source) and list missing sections to pull in, especially after upgrades.
Best use case
clawdbot-workspace-template-review is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Compare a Clawdbot workspace against the official templates installed with Clawdbot (npm or source) and list missing sections to pull in, especially after upgrades.
Teams using clawdbot-workspace-template-review should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/clawdbot-workspace-template-review/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clawdbot-workspace-template-review Compares
| Feature / Agent | clawdbot-workspace-template-review | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Compare a Clawdbot workspace against the official templates installed with Clawdbot (npm or source) and list missing sections to pull in, especially after upgrades.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# 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
Related Skills
perry-workspaces
Create and manage isolated Docker workspaces on your tailnet with Claude Code and OpenCode pre-installed. Use when working with Perry workspaces, connecting to coding agents, or managing remote development environments.
literature-review
Assistance with writing literature reviews by searching for academic sources via Semantic Scholar, OpenAlex, Crossref and PubMed APIs. Use when the user needs to find papers on a topic, get details for specific DOIs, or draft sections of a literature review with proper citations.
google-workspace
Gmail, Calendar, Drive, Docs, Sheets — NO Google Cloud Console required. Just OAuth sign-in. Zero setup complexity vs traditional Google API integrations.
daily-review
Comprehensive daily performance review with communication tracking, meeting analysis, output metrics, and focus time monitoring. Your AI performance coach.
daily-review-2
End-of-day review to capture progress, insights, and plan tomorrow
code-reviewer
No description provided.
clawdbot-skill-update
Comprehensive backup, update, and restore workflow with dynamic workspace detection
clawdbot-self-security-audit
Perform a comprehensive read-only security audit of Clawdbot's own configuration. This is a knowledge-based skill that teaches Clawdbot to identify hardening opportunities across the system. Use when user asks to "run security check", "audit clawdbot", "check security hardening", or "what vulnerabilities does my Clawdbot have". This skill uses Clawdbot's internal capabilities and file system access to inspect configuration, detect misconfigurations, and recommend remediations. It is designed to be extensible - new checks can be added by updating this skill's knowledge.
clawdbot-security
Security audit and hardening for Clawdbot/Moltbot installations. Detects exposed gateways, fixes permissions, enables authentication, and guides firewall/Tailscale setup.
clawdbot-release-check
Check for new clawdbot releases and notify once per new version.
clawdbot-logs
Analyze Clawdbot logs and diagnostics. Use when the user asks about bot performance, response times, errors, session stats, token usage, API costs, or wants to debug slow responses.
clawdbot-documentation-expert
No description provided.