@chrysb/alphaclaw 0.1.0

package/lib/setup/skills/control-ui/SKILL.md

@@ -0,0 +1,70 @@
+---
+name: control-ui
+description: Know when and how to direct the user to the Setup UI for configuration tasks.
+---
+
+# Control UI
+
+There is a web-based Setup UI at `{{BASE_URL}}`. The **user** manages runtime configuration through it. You should NOT call these API endpoints yourself or write config files directly — instead, tell the user what they need to do and where to do it.
+
+## When to direct the user to the UI
+
+### Adding or changing environment variables
+
+When the user needs to add a new API key, token, or any env var:
+
+> You can add that in your Setup UI → **Envars** tab: {{BASE_URL}}
+
+### Connecting a new channel (Telegram, Discord)
+
+> Add your bot token in the Setup UI → **Envars** tab, then approve the pairing request in the **General** tab.
+
+### Approving or rejecting pairings
+
+When a user asks about pairing their Telegram or Discord account:
+
+> Open the Setup UI → **General** tab. Pending pairing requests appear automatically — click **Approve** or **Reject**.
+
+### Connecting OpenAI Codex OAuth
+
+> Connect or reconnect Codex OAuth from the Setup UI → **Models** tab. Click **Connect Codex OAuth** and follow the popup flow.
+
+### Connecting Google Workspace
+
+> Set up Google Workspace from the Setup UI → **General** tab (Google section). You'll need your OAuth client credentials from Google Cloud Console.
+
+Supported Google services (user selects which to enable during OAuth):
+
+| Service | Read | Write | Google API |
+|---------|------|-------|------------|
+| Gmail | `gmail:read` | `gmail:write` | `gmail.googleapis.com` |
+| Calendar | `calendar:read` | `calendar:write` | `calendar-json.googleapis.com` |
+| Drive | `drive:read` | `drive:write` | `drive.googleapis.com` |
+| Sheets | `sheets:read` | `sheets:write` | `sheets.googleapis.com` |
+| Docs | `docs:read` | `docs:write` | `docs.googleapis.com` |
+| Tasks | `tasks:read` | `tasks:write` | `tasks.googleapis.com` |
+| Contacts | `contacts:read` | `contacts:write` | `people.googleapis.com` |
+| Meet | `meet:read` | `meet:write` | `meet.googleapis.com` |
+
+Default enabled: Gmail (read), Calendar (read+write), Drive (read), Sheets (read), Docs (read).
+
+The `gog` CLI is available to verify Google API access:
+
+```bash
+gog auth list --plain
+gog gmail labels list --account user@gmail.com
+gog calendar calendars --account user@gmail.com
+gog drive ls --account user@gmail.com
+gog sheets metadata SPREADSHEET_ID --account user@gmail.com
+gog contacts list --account user@gmail.com
+```
+
+Config lives at `/data/.openclaw/gogcli/`.
+
+## What the Setup UI provides (for your awareness)
+
+This is a reference so you know what's available — not an invitation to call these endpoints.
+
+- **General tab**: Gateway status/restart, OpenClaw version + update, channel health, pending pairings, Google Workspace
+- **Models tab**: Primary model selection, provider credentials, Codex OAuth
+- **Envars tab**: View/edit/add environment variables, save to `/data/.env`

package/package.json

@@ -0,0 +1,34 @@
+{
+  "name": "@chrysb/alphaclaw",
+  "version": "0.1.0",
+  "publishConfig": {
+    "access": "public"
+  },
+  "description": "Setup UI, gateway manager, and onboarding wrapper for OpenClaw",
+  "bin": {
+    "alphaclaw": "./bin/alphaclaw.js"
+  },
+  "files": [
+    "bin/",
+    "lib/"
+  ],
+  "scripts": {
+    "start": "node bin/alphaclaw.js start",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "test:coverage": "vitest run --coverage"
+  },
+  "dependencies": {
+    "express": "^4.21.0",
+    "http-proxy": "^1.18.1",
+    "openclaw": "latest"
+  },
+  "devDependencies": {
+    "@vitest/coverage-v8": "^4.0.18",
+    "supertest": "^7.2.2",
+    "vitest": "^4.0.18"
+  },
+  "engines": {
+    "node": ">=22.12.0"
+  }
+}