How do I install the Kanbu skill?

Run npx skillmds@latest add hydro13/kanbu in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kanbu safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kanbu?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kanbu free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

hydro13 (@hydro13) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kanbu by hydro13 — Agent Skill

Name: Kanbu
Author: hydro13

Kanbu

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.

hydro13 9fb5494 3 files · 21.8 KB Updated Sep 17, 2026

File contents

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)

cd /path/to/kanbu && pnpm install

2. Pair with your Kanbu instance

node packages/mcp-server/dist/index.js

On first run, the MCP server starts the pairing flow:

It displays a setup code (6 characters)
Go to your Kanbu instance → Settings → AI Assistants → Enter the code
The server exchanges the code for a permanent token stored in ~/.config/kanbu/mcp.json

3. Verify

scripts/kanbu.sh workspace.list

Usage

All Kanbu operations go through the kanbu.sh wrapper script:

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:

scripts/kanbu.sh project.list '{"workspaceId": 534}'

List tasks in a project:

scripts/kanbu.sh task.list '{"projectId": 314, "workspaceId": 534}'

Get task details:

scripts/kanbu.sh task.get '{"taskId": 307, "workspaceId": 534}'

Create a task:

scripts/kanbu.sh task.create '{"projectId": 314, "title": "Implement feature X", "description": "Details here", "priority": 2, "workspaceId": 534}'

Update a task:

scripts/kanbu.sh task.update '{"taskId": 307, "title": "Updated title", "workspaceId": 534}'

Move task to a column:

scripts/kanbu.sh task.move '{"taskId": 307, "columnId": 68, "workspaceId": 534}'

Add a comment:

scripts/kanbu.sh comment.create '{"taskId": 307, "content": "Work done.", "workspaceId": 534}'

Search tasks:

scripts/kanbu.sh search.tasks '{"query": "bug", "projectId": 314, "workspaceId": 534}'

My assigned tasks:

scripts/kanbu.sh task.getAssignedToMe '{"workspaceId": 534}'

Discovering workspaceId and projectId

Always start by listing workspaces, then projects:

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.

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

---name: kanbudescription: 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 OpenClawKanbu 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)```bashcd /path/to/kanbu && pnpm install```### 2. Pair with your Kanbu instance```bashnode 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 code3. The server exchanges the code for a permanent token stored in `~/.config/kanbu/mcp.json`### 3. Verify```bashscripts/kanbu.sh workspace.list```## UsageAll Kanbu operations go through the `kanbu.sh` wrapper script:```bashscripts/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:**```bashscripts/kanbu.sh project.list '{"workspaceId": 534}'```**List tasks in a project:**```bashscripts/kanbu.sh task.list '{"projectId": 314, "workspaceId": 534}'```**Get task details:**```bashscripts/kanbu.sh task.get '{"taskId": 307, "workspaceId": 534}'```**Create a task:**```bashscripts/kanbu.sh task.create '{"projectId": 314, "title": "Implement feature X", "description": "Details here", "priority": 2, "workspaceId": 534}'```**Update a task:**```bashscripts/kanbu.sh task.update '{"taskId": 307, "title": "Updated title", "workspaceId": 534}'```**Move task to a column:**```bashscripts/kanbu.sh task.move '{"taskId": 307, "columnId": 68, "workspaceId": 534}'```**Add a comment:**```bashscripts/kanbu.sh comment.create '{"taskId": 307, "content": "Work done.", "workspaceId": 534}'```**Search tasks:**```bashscripts/kanbu.sh search.tasks '{"query": "bug", "projectId": 314, "workspaceId": 534}'```**My assigned tasks:**```bashscripts/kanbu.sh task.getAssignedToMe '{"workspaceId": 534}'```### Discovering workspaceId and projectIdAlways start by listing workspaces, then projects:```bashscripts/kanbu.sh workspace.listscripts/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 ReferenceFor 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`

Frequently asked questions