feat: add OpenClaw skill for Kanbu

Ships a ready-made OpenClaw skill that gives any OpenClaw agent full
read/write access to Kanbu via the tRPC API.

- SKILL.md with triggers for project management, tasks, kanban, etc.
- Universal kanbu.sh wrapper script (auto-detects GET/POST)
- Full API reference (100+ tRPC procedures documented)
- Setup guide: docs/OPENCLAW-SKILL.md
- README updated with OpenClaw Skill section

Install: cp -r packages/openclaw-skill ~/.openclaw/workspace/skills/kanbu
Pair: run MCP server pairing flow or set token manually
Restart: openclaw gateway restart

Author: hydro13

README.md

@@ -114,6 +114,22 @@ When not configured, the Agent tab shows a friendly "not configured" state inste
 
 ---
 
+### 🐾 OpenClaw Skill
+
+Kanbu ships with a ready-made [OpenClaw](https://github.com/OpenClaw-AI/openclaw) skill. Install it once, and your OpenClaw agent knows how to manage projects, tasks, wikis, and teams — no manual configuration needed.
+
+```bash
+# Copy the skill into your OpenClaw workspace
+cp -r packages/openclaw-skill ~/.openclaw/workspace/skills/kanbu
+
+# Restart your gateway
+openclaw gateway restart
+```
+
+That's it. Your agent can now create tasks, move cards, add comments, search across projects, run analytics, and manage your entire board — all through natural language.
+
+**[Full setup guide →](docs/OPENCLAW-SKILL.md)**
+
 ### 🔌 AI Agent Integration (MCP)
 
 Connect any MCP-compatible AI agent to manage your Kanbu projects with **154 available tools**.

docs/OPENCLAW-SKILL.md

@@ -0,0 +1,173 @@
+# Kanbu OpenClaw Skill — Setup Guide
+
+Give your OpenClaw agent full access to Kanbu. Create tasks, move cards, add comments, search, run analytics, manage wikis — all through natural conversation.
+
+## Prerequisites
+
+- A running [Kanbu](https://github.com/hydro13/kanbu) instance (local or remote)
+- [OpenClaw](https://github.com/OpenClaw-AI/openclaw) installed and running
+- `curl` and `jq` available on your system
+
+## Step 1: Install the Skill
+
+```bash
+# From the Kanbu repo root
+cp -r packages/openclaw-skill ~/.openclaw/workspace/skills/kanbu
+
+# Make the wrapper script executable
+chmod +x ~/.openclaw/workspace/skills/kanbu/scripts/kanbu.sh
+```
+
+## Step 2: Pair with your Kanbu instance
+
+The skill needs an API token to authenticate. Kanbu uses a secure pairing flow — similar to pairing a Bluetooth device.
+
+### Option A: Use the MCP server pairing (recommended)
+
+```bash
+# Set your Kanbu URL
+export KANBU_URL=https://localhost:3001  # or https://your-kanbu-domain.com
+
+# For self-signed certs (local dev)
+export NODE_TLS_REJECT_UNAUTHORIZED=0
+
+# Run the MCP server — it will start the pairing flow
+node packages/mcp-server/dist/index.js
+```
+
+The server displays a **6-character setup code**. Enter it in Kanbu:
+
+1. Open your Kanbu instance in a browser
+2. Go to **Settings → AI Assistants**
+3. Click **"Pair New Assistant"**
+4. Enter the setup code
+
+The token is saved to `~/.config/kanbu/mcp.json`. The skill reads this file automatically.
+
+### Option B: Use an existing API token
+
+If you already have a Kanbu API token (from Settings → API Tokens), set it directly:
+
+```bash
+mkdir -p ~/.config/kanbu
+cat > ~/.config/kanbu/mcp.json << 'EOF'
+{
+  "kanbuUrl": "https://your-kanbu-url",
+  "token": "your-api-token-here"
+}
+EOF
+```
+
+## Step 3: Restart OpenClaw
+
+```bash
+openclaw gateway restart
+```
+
+## Step 4: Verify
+
+Talk to your OpenClaw agent:
+
+> "List my Kanbu workspaces"
+
+or
+
+> "Show me all tasks in the Kanbu project"
+
+Your agent will use the Kanbu skill automatically when it recognizes project management requests.
+
+## What Your Agent Can Do
+
+Once connected, your OpenClaw agent has access to **100+ Kanbu API procedures**:
+
+| Category | Examples |
+|----------|---------|
+| **Projects** | List, create, get project details |
+| **Tasks** | Create, update, move, assign, search, get my tasks |
+| **Subtasks** | Create, update, toggle, delete |
+| **Comments** | Add, edit, delete comments on tasks |
+| **Search** | Search tasks, global search across all entities |
+| **Analytics** | Project stats, velocity, cycle time, team workload |
+| **Wiki** | Create/edit/delete project and workspace wiki pages |
+| **GitHub** | List commits, PRs, create branches, link PRs to tasks |
+| **ACL** | Grant/revoke permissions, check access, permission matrix |
+| **Admin** | User management, backups, system settings |
+| **Audit** | View audit logs, export, statistics |
+
+## How It Works
+
+The skill uses a lightweight bash wrapper (`scripts/kanbu.sh`) that calls Kanbu's tRPC API directly:
+
+```
+Your message → OpenClaw agent → reads SKILL.md → runs kanbu.sh → Kanbu API → result
+```
+
+- **No separate server** to run — it's just curl calls
+- **Auth** is read from `~/.config/kanbu/mcp.json`
+- **Queries** (list, get, search) use GET
+- **Mutations** (create, update, delete) use POST
+- Auto-detected by the script based on procedure name
+
+## Configuration
+
+### Environment variables (optional)
+
+Override the config file with environment variables:
+
+```bash
+export KANBU_URL=https://your-kanbu-url
+export KANBU_TOKEN=your-token
+```
+
+### Custom config path
+
+```bash
+export KANBU_CONFIG=/path/to/your/config.json
+```
+
+### Multiple instances
+
+To connect to multiple Kanbu instances, use environment variables per call or maintain separate config files.
+
+## Troubleshooting
+
+### "No config found"
+
+Run the pairing flow (Step 2) or create `~/.config/kanbu/mcp.json` manually.
+
+### Connection refused
+
+Check that your Kanbu instance is running:
+
+```bash
+curl -sk https://localhost:3001/api/health
+```
+
+### Self-signed certificate errors
+
+For local development with self-signed certs, the script uses `curl -k` by default.
+
+### Permission denied
+
+Your paired token inherits the permissions of the Kanbu user who approved the pairing. Make sure that user has the necessary project access.
+
+## Upgrading
+
+When Kanbu releases a new version with skill updates:
+
+```bash
+cd /path/to/kanbu && git pull
+cp -r packages/openclaw-skill ~/.openclaw/workspace/skills/kanbu
+openclaw gateway restart
+```
+
+## Uninstall
+
+```bash
+rm -rf ~/.openclaw/workspace/skills/kanbu
+openclaw gateway restart
+```
+
+---
+
+**Questions?** Open an [issue](https://github.com/hydro13/kanbu/issues) or join our [Discord](https://discord.gg/cCpHUvX4CF).

packages/openclaw-skill/SKILL.md

@@ -0,0 +1,120 @@
+---
+name: kanbu
+description: Manage projects, tasks, wikis, and teams in Kanbu — a self-hosted project management platform built for AI agents. Use when the user asks about project management, task tracking, kanban boards, sprints, wikis, team workload, or anything related to Kanbu. Also triggers on task creation, updates, comments, subtasks, search, analytics, GitHub integration, permissions (ACL), and audit logs.
+---
+
+# Kanbu Skill for OpenClaw
+
+Kanbu is a self-hosted, agent-native project management platform. This skill gives you full read/write access to Kanbu via its tRPC API.
+
+## Setup
+
+### 1. Install Kanbu MCP server (includes pairing CLI)
+
+```bash
+cd /path/to/kanbu && pnpm install
+```
+
+### 2. Pair with your Kanbu instance
+
+```bash
+node packages/mcp-server/dist/index.js
+```
+
+On first run, the MCP server starts the pairing flow:
+1. It displays a **setup code** (6 characters)
+2. Go to your Kanbu instance → Settings → AI Assistants → Enter the code
+3. The server exchanges the code for a permanent token stored in `~/.config/kanbu/mcp.json`
+
+### 3. Verify
+
+```bash
+scripts/kanbu.sh workspace.list
+```
+
+## Usage
+
+All Kanbu operations go through the `kanbu.sh` wrapper script:
+
+```bash
+scripts/kanbu.sh <procedure> '<json-input>'
+```
+
+The script auto-detects GET (queries) vs POST (mutations) and handles auth from `~/.config/kanbu/mcp.json`.
+
+### Common operations
+
+**List projects:**
+```bash
+scripts/kanbu.sh project.list '{"workspaceId": 534}'
+```
+
+**List tasks in a project:**
+```bash
+scripts/kanbu.sh task.list '{"projectId": 314, "workspaceId": 534}'
+```
+
+**Get task details:**
+```bash
+scripts/kanbu.sh task.get '{"taskId": 307, "workspaceId": 534}'
+```
+
+**Create a task:**
+```bash
+scripts/kanbu.sh task.create '{"projectId": 314, "title": "Implement feature X", "description": "Details here", "priority": 2, "workspaceId": 534}'
+```
+
+**Update a task:**
+```bash
+scripts/kanbu.sh task.update '{"taskId": 307, "title": "Updated title", "workspaceId": 534}'
+```
+
+**Move task to a column:**
+```bash
+scripts/kanbu.sh task.move '{"taskId": 307, "columnId": 68, "workspaceId": 534}'
+```
+
+**Add a comment:**
+```bash
+scripts/kanbu.sh comment.create '{"taskId": 307, "content": "Work done.", "workspaceId": 534}'
+```
+
+**Search tasks:**
+```bash
+scripts/kanbu.sh search.tasks '{"query": "bug", "projectId": 314, "workspaceId": 534}'
+```
+
+**My assigned tasks:**
+```bash
+scripts/kanbu.sh task.getAssignedToMe '{"workspaceId": 534}'
+```
+
+### Discovering workspaceId and projectId
+
+Always start by listing workspaces, then projects:
+
+```bash
+scripts/kanbu.sh workspace.list
+scripts/kanbu.sh project.list '{"workspaceId": <id>}'
+```
+
+Use the returned IDs in all subsequent calls. Most procedures require `workspaceId`.
+
+### Priority values
+- 0 = None
+- 1 = Low
+- 2 = Medium
+- 3 = High
+- 4 = Urgent
+
+## Full API Reference
+
+For all 100+ procedures (wiki, analytics, ACL, GitHub, admin, audit, groups, etc.), read [references/api-reference.md](references/api-reference.md).
+
+## Tips
+
+- **workspaceId is required** on almost every call
+- Task identifiers (e.g., `PROJTEMP-34`) are for display; use numeric `taskId` for API calls
+- The script outputs `result.data` directly as JSON — pipe to `jq` for filtering
+- Errors are printed with full detail for debugging
+- For self-signed certs (local dev), the script uses `curl -k`