@openparachute/agent 0.1.2 → 0.2.2

package/.claude/skills/add-emacs/SKILL.md

@@ -1,296 +0,0 @@
----
-name: add-emacs
-description: Add Emacs as a channel. Opens an interactive chat buffer and org-mode integration so you can talk to NanoClaw from within Emacs (Doom, Spacemacs, or vanilla). Local HTTP bridge — no bot token or external service needed.
----
-
-# Add Emacs Channel
-
-Adds Emacs support via a local HTTP bridge. Works with Doom Emacs, Spacemacs, and vanilla Emacs 27.1+.
-
-## What you can do with this
-
-- **Ask while coding** — open the chat buffer (`C-c n c` / `SPC N c`), ask about a function or error without leaving Emacs
-- **Code review** — select a region and send it with `nanoclaw-org-send`; the response appears as a child heading inline in your org file
-- **Meeting notes** — send an org agenda entry; get a summary or action item list back as a child node
-- **Draft writing** — send org prose; receive revisions or continuations in place
-- **Research capture** — ask a question directly in your org notes; the answer lands exactly where you need it
-
-## Install
-
-NanoClaw doesn't ship channels in trunk. This skill copies the Emacs adapter and the Lisp client in from the `channels` branch. Native HTTP bridge — no Chat SDK, no adapter package.
-
-### Pre-flight (idempotent)
-
-Skip to **Enable** if all of these are already in place:
-
-- `src/channels/emacs.ts` exists
-- `emacs/nanoclaw.el` exists
-- `src/channels/index.ts` contains `import './emacs.js';`
-
-Otherwise continue. Every step below is safe to re-run.
-
-### 1. Fetch the channels branch
-
-```bash
-git fetch origin channels
-```
-
-### 2. Copy the adapter and Lisp client
-
-```bash
-mkdir -p emacs
-git show origin/channels:src/channels/emacs.ts      > src/channels/emacs.ts
-git show origin/channels:src/channels/emacs.test.ts > src/channels/emacs.test.ts
-git show origin/channels:emacs/nanoclaw.el          > emacs/nanoclaw.el
-```
-
-### 3. Append the self-registration import
-
-Append to `src/channels/index.ts` (skip if the line is already present):
-
-```typescript
-import './emacs.js';
-```
-
-### 4. Build
-
-```bash
-pnpm run build
-```
-
-No npm package to install — the adapter uses only Node builtins (`http`).
-
-## Enable
-
-The adapter is gated by `EMACS_ENABLED` so the HTTP port isn't opened on hosts that aren't running Emacs. Add to `.env`:
-
-```bash
-EMACS_ENABLED=true
-EMACS_CHANNEL_PORT=8766       # optional — change only if 8766 is taken
-EMACS_AUTH_TOKEN=             # optional — set to a random string to lock the endpoint
-EMACS_PLATFORM_ID=default     # optional — only change if you want a non-default chat id
-```
-
-Generate an auth token (recommended even on single-user machines — prevents other local processes from poking the endpoint):
-
-```bash
-node -e "console.log(require('crypto').randomBytes(16).toString('hex'))"
-```
-
-## Wire the channel
-
-Emacs is a single-user, single-chat channel. One host = one messaging group with `platform_id = "default"`.
-
-### If this is your first agent group
-
-Run `/init-first-agent` — pick **Emacs** as the channel, use any short handle as the "user id" (e.g. your OS username), and the skill will create the agent group, wire the channel, and write a welcome message that the agent delivers back to your Emacs buffer.
-
-### Otherwise — wire to an existing agent group
-
-Run the `register` step directly. The `EMACS_PLATFORM_ID` (default `default`) becomes the messaging group's platform id:
-
-```bash
-pnpm exec tsx setup/index.ts --step register -- \
-  --platform-id "default" --name "Emacs" \
-  --folder "<existing-folder>" --channel "emacs" \
-  --session-mode "agent-shared" \
-  --assistant-name "<existing-assistant-name>"
-```
-
-`agent-shared` puts Emacs messages in the same session as any other channel wired to the same agent group — so a conversation you started in Telegram continues in Emacs. Use `shared` to keep an independent Emacs thread with the same workspace, or a new `--folder` for a dedicated Emacs-only agent.
-
-## Configure Emacs
-
-`nanoclaw.el` needs only Emacs 27.1+ builtins (`url`, `json`, `org`) — no package manager.
-
-AskUserQuestion: Which Emacs distribution are you using?
-- **Doom Emacs** — `config.el` with `map!` keybindings
-- **Spacemacs** — `dotspacemacs/user-config` in `~/.spacemacs`
-- **Vanilla Emacs / other** — `init.el` with `global-set-key`
-
-**Doom Emacs** — add to `~/.config/doom/config.el` (or `~/.doom.d/config.el`):
-
-```elisp
-;; NanoClaw — personal AI assistant channel
-(load (expand-file-name "~/src/nanoclaw/emacs/nanoclaw.el"))
-
-(map! :leader
-      :prefix ("N" . "NanoClaw")
-      :desc "Chat buffer"  "c" #'nanoclaw-chat
-      :desc "Send org"     "o" #'nanoclaw-org-send)
-```
-
-Reload: `M-x doom/reload`
-
-**Spacemacs** — add to `dotspacemacs/user-config` in `~/.spacemacs`:
-
-```elisp
-;; NanoClaw — personal AI assistant channel
-(load-file "~/src/nanoclaw/emacs/nanoclaw.el")
-
-(spacemacs/set-leader-keys "aNc" #'nanoclaw-chat)
-(spacemacs/set-leader-keys "aNo" #'nanoclaw-org-send)
-```
-
-Reload: `M-x dotspacemacs/sync-configuration-layers` or restart Emacs.
-
-**Vanilla Emacs** — add to `~/.emacs.d/init.el`:
-
-```elisp
-;; NanoClaw — personal AI assistant channel
-(load-file "~/src/nanoclaw/emacs/nanoclaw.el")
-
-(global-set-key (kbd "C-c n c") #'nanoclaw-chat)
-(global-set-key (kbd "C-c n o") #'nanoclaw-org-send)
-```
-
-Reload: `M-x eval-buffer` or restart Emacs.
-
-Replace `~/src/nanoclaw/emacs/nanoclaw.el` with your actual NanoClaw checkout path.
-
-If `EMACS_AUTH_TOKEN` is set, also add (any distribution):
-
-```elisp
-(setq nanoclaw-auth-token "<your-token>")
-```
-
-If you changed `EMACS_CHANNEL_PORT` from the default:
-
-```elisp
-(setq nanoclaw-port <your-port>)
-```
-
-## Restart NanoClaw
-
-```bash
-pnpm run build
-launchctl kickstart -k gui/$(id -u)/com.nanoclaw   # macOS
-# systemctl --user restart nanoclaw                # Linux
-```
-
-## Verify
-
-### HTTP endpoint
-
-```bash
-curl -s http://localhost:8766/api/messages?since=0
-```
-
-Expected: `{"messages":[]}`. With an auth token:
-
-```bash
-curl -s -H "Authorization: Bearer <token>" http://localhost:8766/api/messages?since=0
-```
-
-### From Emacs
-
-Tell the user:
-
-> 1. Open the chat buffer with your keybinding (`SPC N c`, `SPC a N c`, or `C-c n c`)
-> 2. Type a message and press `C-c C-c` to send (RET inserts newlines)
-> 3. A response should appear within a few seconds
->
-> For org-mode: open any `.org` file, position the cursor on a heading, and use `SPC N o` / `SPC a N o` / `C-c n o`
-
-### Log line
-
-`tail -f logs/nanoclaw.log` should show `Emacs channel listening` at startup.
-
-## Channel Info
-
-- **type**: `emacs`
-- **terminology**: Single local buffer. There are no "groups" or separate chats — one host = one chat, addressed by a `platform_id` string (default `default`).
-- **how-to-find-id**: The platform id is whatever you set in `EMACS_PLATFORM_ID` (default `default`). User handles are arbitrary; your OS username or first name is fine (e.g. `emacs:<username>`).
-- **supports-threads**: no
-- **typical-use**: Single developer talking to the assistant from within Emacs, alongside whatever other channel they use (Slack, Telegram, Discord).
-- **default-isolation**: Same agent group as the primary DM, with `session-mode = agent-shared` so a conversation started elsewhere continues in Emacs. Pick a separate folder only if you specifically want an Emacs-only persona.
-
-### Features
-
-- Interactive chat buffer (`nanoclaw-chat`) with markdown → org-mode rendering
-- Org integration (`nanoclaw-org-send`) — sends the current subtree or region; reply lands as a child heading
-- Optional bearer-token auth for the local endpoint
-- Single-user: the adapter exposes exactly one messaging group per host
-
-Not applicable (design): multi-user channels, threads, cold DM initiation, typing indicators, attachments.
-
-## Troubleshooting
-
-### Port already in use
-
-```
-Error: listen EADDRINUSE: address already in use :::8766
-```
-
-Either a stale NanoClaw is running or another app has the port. Kill stale process or change port:
-
-```bash
-lsof -ti :8766 | xargs kill -9
-# or set EMACS_CHANNEL_PORT in .env and mirror in Emacs config (nanoclaw-port)
-```
-
-### Adapter not starting
-
-If `grep "Emacs channel listening" logs/nanoclaw.log` returns nothing, check that `EMACS_ENABLED=true` is in `.env` and that the adapter import is present:
-
-```bash
-grep -q '^EMACS_ENABLED=true' .env && echo "enabled" || echo "not enabled"
-grep -q "import './emacs.js'" src/channels/index.ts && echo "imported" || echo "not imported"
-```
-
-### No response from agent
-
-1. NanoClaw running: `launchctl list | grep nanoclaw` (macOS) / `systemctl --user status nanoclaw` (Linux)
-2. Messaging group wired: `sqlite3 data/v2.db "SELECT mg.platform_id, ag.folder FROM messaging_groups mg JOIN messaging_group_agents mga ON mg.id = mga.messaging_group_id JOIN agent_groups ag ON ag.id = mga.agent_group_id WHERE mg.channel_type = 'emacs'"`
-3. Logs show inbound: `grep 'channel_type=emacs\|Emacs' logs/nanoclaw.log | tail -20`
-
-If no messaging group row exists, run the `register` command above.
-
-### Auth token mismatch (401 Unauthorized)
-
-```elisp
-M-x describe-variable RET nanoclaw-auth-token RET
-```
-
-Must match `EMACS_AUTH_TOKEN` in `.env`. If you didn't set one server-side, clear it in Emacs too:
-
-```elisp
-(setq nanoclaw-auth-token nil)
-```
-
-### nanoclaw.el not loading
-
-```bash
-ls ~/src/nanoclaw/emacs/nanoclaw.el
-```
-
-If NanoClaw is cloned elsewhere, update the `load`/`load-file` path in your Emacs config.
-
-## Agent Formatting
-
-The Emacs bridge converts markdown → org-mode automatically. Agents should output standard markdown, **not** org-mode syntax:
-
-| Markdown | Org-mode |
-|----------|----------|
-| `**bold**` | `*bold*` |
-| `*italic*` | `/italic/` |
-| `~~text~~` | `+text+` |
-| `` `code` `` | `~code~` |
-| ` ```lang ` | `#+begin_src lang` |
-
-If an agent outputs org-mode directly, markers get double-converted and render incorrectly.
-
-## Removal
-
-```bash
-rm src/channels/emacs.ts src/channels/emacs.test.ts emacs/nanoclaw.el
-# Remove the `import './emacs.js';` line from src/channels/index.ts
-# Remove EMACS_* lines from .env
-pnpm run build
-launchctl kickstart -k gui/$(id -u)/com.nanoclaw   # macOS
-# systemctl --user restart nanoclaw                # Linux
-
-# Remove the NanoClaw block from your Emacs config
-# Optionally clean up the messaging group:
-sqlite3 data/v2.db "DELETE FROM messaging_group_agents WHERE messaging_group_id IN (SELECT id FROM messaging_groups WHERE channel_type='emacs'); DELETE FROM messaging_groups WHERE channel_type='emacs';"
-```

package/.claude/skills/add-gcal-tool/SKILL.md

@@ -1,210 +0,0 @@
----
-name: add-gcal-tool
-description: Add Google Calendar as an MCP tool (list calendars, list/search/create events, free/busy queries) using OneCLI-managed OAuth. Multi-calendar and multi-account supported. Mirrors /add-gmail-tool's stub pattern — no raw credentials ever reach the container; OneCLI injects real tokens at request time.
----
-
-# Add Google Calendar Tool (OneCLI-native)
-
-This skill wires [`@cocal/google-calendar-mcp`](https://github.com/cocal-com/google-calendar-mcp) into selected agent groups. The MCP server reads stub credentials containing the `onecli-managed` placeholder; the OneCLI gateway intercepts outbound calls to `calendar.googleapis.com` / `oauth2.googleapis.com` and swaps the bearer for the real OAuth token from its vault.
-
-**Why this package (and not gongrzhe's):** `@gongrzhe/server-calendar-autoauth-mcp` only supports the `primary` calendar and exposes 5 tools (no `list_calendars`). `@cocal/google-calendar-mcp` explicitly supports multi-calendar and multi-account, and is actively maintained.
-
-Tools exposed (surfaced as `mcp__calendar__<name>`, exact set depends on version — run `tools/list` against the MCP server to enumerate): `list-calendars`, `list-events`, `search-events`, `create-event`, `update-event`, `delete-event`, `get-event`, `list-colors`, `get-freebusy`, `get-current-time`, plus multi-account management tools.
-
-**Why this pattern:** v2's invariant is that containers never receive raw API keys (CHANGELOG 2.0.0). Same stub pattern `/add-gmail-tool` uses. This skill is deliberately a sibling, not a combined "Google Workspace" skill — installs independently and removes cleanly.
-
-## Phase 1: Pre-flight
-
-### Verify OneCLI has Google Calendar connected
-
-```bash
-onecli apps get --provider google-calendar
-```
-
-Expected: `"connection": { "status": "connected" }` with scopes including `calendar.readonly` and `calendar.events`.
-
-If not connected, tell the user:
-
-> Open the OneCLI web UI at http://127.0.0.1:10254, go to Apps → Google Calendar, and click Connect. Sign in with the Google account the agent should act as. `calendar.readonly` + `calendar.events` are the minimum useful scopes.
-
-### Verify stub credentials exist
-
-The stub lives at `~/.calendar-mcp/` by convention (shared with `/add-gmail-tool`'s sibling). cocal doesn't default to this path (it uses `~/.config/google-calendar-mcp/tokens.json`) — we override via env vars below so it reads our stubs instead.
-
-```bash
-ls -la ~/.calendar-mcp/gcp-oauth.keys.json ~/.calendar-mcp/credentials.json 2>&1
-```
-
-If both exist with `onecli-managed`:
-
-```bash
-grep -l onecli-managed ~/.calendar-mcp/gcp-oauth.keys.json ~/.calendar-mcp/credentials.json
-```
-
-...skip to Phase 2. If either file has real credentials (no `onecli-managed`), **STOP** — back up and delete before proceeding.
-
-If absent, write them:
-
-```bash
-mkdir -p ~/.calendar-mcp
-cat > ~/.calendar-mcp/gcp-oauth.keys.json <<'EOF'
-{
-  "installed": {
-    "client_id": "onecli-managed.apps.googleusercontent.com",
-    "client_secret": "onecli-managed",
-    "redirect_uris": ["http://localhost:3000/oauth2callback"]
-  }
-}
-EOF
-cat > ~/.calendar-mcp/credentials.json <<'EOF'
-{
-  "access_token": "onecli-managed",
-  "refresh_token": "onecli-managed",
-  "token_type": "Bearer",
-  "expiry_date": 99999999999999,
-  "scope": "https://www.googleapis.com/auth/calendar.readonly https://www.googleapis.com/auth/calendar.events"
-}
-EOF
-chmod 600 ~/.calendar-mcp/*.json
-```
-
-### Verify mount allowlist covers the path
-
-```bash
-cat ~/.config/nanoclaw/mount-allowlist.json
-```
-
-`~/.calendar-mcp` must sit under an `allowedRoots` entry.
-
-### Check agent secret-mode
-
-For each target agent group, confirm OneCLI will inject the Google Calendar token:
-
-```bash
-onecli agents list
-```
-
-`secretMode: all` is sufficient. If `selective`, explicitly assign the Calendar secret.
-
-## Phase 2: Apply Code Changes
-
-### Check if already applied
-
-```bash
-grep -q 'CALENDAR_MCP_VERSION' container/Dockerfile && \
-grep -q "mcp__calendar__\*" container/agent-runner/src/providers/claude.ts && \
-echo "ALREADY APPLIED — skip to Phase 3"
-```
-
-### Add MCP server to Dockerfile
-
-Edit `container/Dockerfile`. Find the pinned-version ARG block and add:
-
-```dockerfile
-ARG CALENDAR_MCP_VERSION=2.6.1
-```
-
-If `/add-gmail-tool` has already been applied, the pnpm global-install block already exists with its `zod-to-json-schema@3.22.5` pin. Just append the calendar package — **the calendar-mcp uses `zod@4.x` and does NOT need that pin**, but it's harmless to share the block:
-
-```dockerfile
-RUN --mount=type=cache,target=/root/.cache/pnpm \
-    pnpm install -g \
-        "@gongrzhe/server-gmail-autoauth-mcp@${GMAIL_MCP_VERSION}" \
-        "@cocal/google-calendar-mcp@${CALENDAR_MCP_VERSION}" \
-        "zod-to-json-schema@3.22.5"
-```
-
-If `/add-gmail-tool` hasn't been applied, install Calendar standalone:
-
-```dockerfile
-RUN --mount=type=cache,target=/root/.cache/pnpm \
-    pnpm install -g "@cocal/google-calendar-mcp@${CALENDAR_MCP_VERSION}"
-```
-
-### Add tools to allowlist
-
-Edit `container/agent-runner/src/providers/claude.ts`. Add `'mcp__calendar__*'` to `TOOL_ALLOWLIST` after `'mcp__nanoclaw__*'` (or after `'mcp__gmail__*'` if present).
-
-### Rebuild the container image
-
-```bash
-./container/build.sh
-```
-
-## Phase 3: Wire Per-Agent-Group
-
-For each agent group, merge into `groups/<folder>/container.json`:
-
-```jsonc
-{
-  "mcpServers": {
-    "calendar": {
-      "command": "google-calendar-mcp",
-      "args": [],
-      "env": {
-        "GOOGLE_OAUTH_CREDENTIALS": "/workspace/extra/.calendar-mcp/gcp-oauth.keys.json",
-        "GOOGLE_CALENDAR_MCP_TOKEN_PATH": "/workspace/extra/.calendar-mcp/credentials.json"
-      }
-    }
-  },
-  "additionalMounts": [
-    {
-      "hostPath": "/home/<user>/.calendar-mcp",
-      "containerPath": ".calendar-mcp",
-      "readonly": false
-    }
-  ]
-}
-```
-
-Substitute `<user>` with `echo $HOME`. `containerPath` is relative (mount-security rejects absolute paths — additional mounts land at `/workspace/extra/<relative>`).
-
-**Same-group-as-gmail tip:** if this group already has the gmail MCP + `.gmail-mcp` mount, **merge, don't replace** — both entries coexist in `mcpServers` and `additionalMounts`.
-
-## Phase 4: Build and Restart
-
-```bash
-pnpm run build
-systemctl --user restart nanoclaw   # Linux
-# launchctl kickstart -k gui/$(id -u)/com.nanoclaw   # macOS
-```
-
-Kill any existing agent containers so they respawn with the new mcpServers config:
-
-```bash
-docker ps -q --filter 'name=nanoclaw-v2-' | xargs -r docker kill
-```
-
-## Phase 5: Verify
-
-### Test from a wired agent
-
-> Send: **"list my calendars"** or **"what's on my work calendar next Monday?"**.
->
-> First call takes 2–3s while the MCP server starts and OneCLI does the token exchange.
-
-### Check logs if the tool isn't working
-
-```bash
-tail -100 logs/nanoclaw.log | grep -iE 'calendar|mcp'
-```
-
-Common signals:
-- `command not found: google-calendar-mcp` → image not rebuilt.
-- `ENOENT ...credentials.json` → mount missing. Check the mount allowlist.
-- `401 Unauthorized` from `*.googleapis.com` → OneCLI isn't injecting; verify agent's secret mode and that Google Calendar is connected.
-- Agent says "I don't have calendar tools" → `mcp__calendar__*` missing from `TOOL_ALLOWLIST`, or image cache stale (`./container/build.sh` again).
-
-## Removal
-
-1. Delete `"calendar"` from `mcpServers` and the `.calendar-mcp` mount from `additionalMounts` in each group's `container.json`.
-2. Remove `'mcp__calendar__*'` from `TOOL_ALLOWLIST`.
-3. Remove `CALENDAR_MCP_VERSION` ARG and the calendar package from the Dockerfile install block.
-4. `pnpm run build && ./container/build.sh && systemctl --user restart nanoclaw`.
-5. Optional: `rm -rf ~/.calendar-mcp/` and `onecli apps disconnect --provider google-calendar`.
-
-## Credits & references
-
-- **MCP server:** [`@cocal/google-calendar-mcp`](https://github.com/cocal-com/google-calendar-mcp) — MIT-licensed, actively maintained, multi-account and multi-calendar.
-- **Why not gongrzhe:** earlier versions of this skill used `@gongrzhe/server-calendar-autoauth-mcp@1.0.2` which only supports the primary calendar with 5 event-level tools. The cocal server supersedes it.
-- **Skill pattern:** direct sibling of [`/add-gmail-tool`](../add-gmail-tool/SKILL.md); same OneCLI stub mechanism.

package/.claude/skills/add-gchat/REMOVE.md

@@ -1,6 +0,0 @@
-# Remove Google Chat Channel
-
-1. Comment out `import './gchat.js'` in `src/channels/index.ts`
-2. Remove `GCHAT_CREDENTIALS` from `.env`
-3. `pnpm uninstall @chat-adapter/gchat`
-4. Rebuild and restart

package/.claude/skills/add-gchat/SKILL.md

@@ -1,92 +0,0 @@
----
-name: add-gchat
-description: Add Google Chat channel integration via Chat SDK.
----
-
-# Add Google Chat Channel
-
-Adds Google Chat support via the Chat SDK bridge.
-
-## Install
-
-NanoClaw doesn't ship channels in trunk. This skill copies the Google Chat adapter in from the `channels` branch.
-
-### Pre-flight (idempotent)
-
-Skip to **Credentials** if all of these are already in place:
-
-- `src/channels/gchat.ts` exists
-- `src/channels/index.ts` contains `import './gchat.js';`
-- `@chat-adapter/gchat` is listed in `package.json` dependencies
-
-Otherwise continue. Every step below is safe to re-run.
-
-### 1. Fetch the channels branch
-
-```bash
-git fetch origin channels
-```
-
-### 2. Copy the adapter
-
-```bash
-git show origin/channels:src/channels/gchat.ts > src/channels/gchat.ts
-```
-
-### 3. Append the self-registration import
-
-Append to `src/channels/index.ts` (skip if the line is already present):
-
-```typescript
-import './gchat.js';
-```
-
-### 4. Install the adapter package (pinned)
-
-```bash
-pnpm install @chat-adapter/gchat@4.26.0
-```
-
-### 5. Build
-
-```bash
-pnpm run build
-```
-
-## Credentials
-
-> 1. Go to [Google Cloud Console](https://console.cloud.google.com)
-> 2. Create or select a project
-> 3. Enable the **Google Chat API**
-> 4. Go to **Google Chat API** > **Configuration**:
->    - App name and description
->    - Connection settings: select **HTTP endpoint URL** and set to `https://your-domain/webhook/gchat`
-> 5. Create a **Service Account**:
->    - Go to **IAM & Admin** > **Service Accounts** > **Create Service Account**
->    - Grant the Chat Bot role
->    - Create a JSON key and download it
-
-### Configure environment
-
-Add the service account JSON as a single-line string to `.env`:
-
-```bash
-GCHAT_CREDENTIALS={"type":"service_account","project_id":"...","private_key":"...","client_email":"..."}
-```
-
-Sync to container: `mkdir -p data/env && cp .env data/env/env`
-
-## Next Steps
-
-If you're in the middle of `/setup`, return to the setup flow now.
-
-Otherwise, run `/manage-channels` to wire this channel to an agent group.
-
-## Channel Info
-
-- **type**: `gchat`
-- **terminology**: Google Chat has "spaces." A space can be a group conversation or a direct message with the bot.
-- **how-to-find-id**: Open the space in Google Chat, look at the URL — the space ID is the segment after `/space/` (e.g. `spaces/AAAA...`). Or use the Google Chat API to list spaces.
-- **supports-threads**: yes
-- **typical-use**: Interactive chat — team spaces or direct messages
-- **default-isolation**: Same agent group for spaces where you're the primary user. Separate agent group for spaces with different teams or sensitive contexts.

package/.claude/skills/add-gchat/VERIFY.md

@@ -1,3 +0,0 @@
-# Verify Google Chat Channel
-
-Add the bot to a Google Chat space, then send a message or @mention the bot. The bot should respond within a few seconds.

package/.claude/skills/add-github/REMOVE.md

@@ -1,6 +0,0 @@
-# Remove GitHub Channel
-
-1. Comment out `import './github.js'` in `src/channels/index.ts`
-2. Remove `GITHUB_TOKEN` and `GITHUB_WEBHOOK_SECRET` from `.env`
-3. `pnpm uninstall @chat-adapter/github`
-4. Rebuild and restart