clawdbot-monitor

# Clawdbot Monitor

Monitor the [Clawdbot](https://github.com/clawdbot/clawdbot) repository and identify opportunities to improve Geoffrey.

## Clawdbot vs Geoffrey Quick Comparison

| Aspect | Clawdbot | Geoffrey |
|--------|----------|----------|
| **Scope** | Multi-channel messaging hub (WhatsApp, Discord, etc.) | Claude Code plugin for personal AI |
| **Skills** | 60+ (CLI wrappers, platform integrations) | 26 (specialized workflows) |
| **Hooks** | Event-driven TypeScript handlers | hooks.json configuration |
| **Memory** | Hybrid vector + BM25 with SQLite-vec | Obsidian vault + knowledge-manager |
| **Releases** | Weekly (v2026.x.x latest) | Versioned plugin (v0.x.x) |

## Focus Areas

When invoked with an argument, focus analysis on that area:
- **skills** - Skill formats, metadata, categories, CLI patterns
- **hooks** - Event types, handler patterns, automation
- **extensions** - Plugin architecture, provider isolation
- **memory** - Search patterns, embeddings, persistence

Without an argument, perform full analysis across all areas.

---

## Phase 1: Fetch Clawdbot Current State

### 1.1 Core Documentation
Fetch these from `github.com/clawdbot/clawdbot`:
- `README.md` - Overall structure and philosophy
- `CLAUDE.md` - System instructions (if exists)
- Check releases page for version info

### 1.2 Skill Structure
Explore the skills directory:
- List all available skills
- Sample key skills that overlap with Geoffrey's domains
- Note skill metadata patterns (`requires.bins`, `requires.config`, install methods)
- Check for new skills since last analysis

### 1.3 Hook System
Examine hook architecture:
- Event types (session, command, boot)
- Handler patterns (TypeScript)
- Compare to Geoffrey's hooks.json approach

### 1.4 Recent Changes
- Check recent commits for significant updates
- Look for new patterns or breaking changes
- Note any announcements or migration guides

---

## Phase 2: Analyze Geoffrey Current State

### 2.1 Core Architecture
Read these Geo