Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Interact with PikaBoard task management API. Use when creating, updating, listing, or managing tasks. Agent-first kanban for AI teams. Triggers on: tasks, kanban, board, todo, backlog, sprint.
Interact with PikaBoard task management API. Use when creating, updating, listing, or managing tasks. Agent-first kanban for AI teams. Triggers on: tasks, kanban, board, todo, backlog, sprint.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Agent-first task/kanban dashboard. PikaBoard is the source of truth for tasks.
After install, start the server: cd pikaboard/backend && npm start Access dashboard at http://localhost:3001
Reference tasks by ID: task 12 or #12 โ view task move #12 to done โ status change create task "Fix bug" โ new task
See backend/API.md for full endpoint documentation (single canonical doc).
List tasks: curl -H "Authorization: Bearer $PIKABOARD_TOKEN" "$PIKABOARD_API/tasks" Create task: curl -X POST -H "Authorization: Bearer $PIKABOARD_TOKEN" \ -H "Content-Type: application/json" \ -d '{"name":"Fix bug","status":"inbox","priority":"high","tags":["bug","backend"]}' \ "$PIKABOARD_API/tasks" Update status: curl -X PATCH -H "Authorization: Bearer $PIKABOARD_TOKEN" \ -H "Content-Type: application/json" \ -d '{"status":"done"}' \ "$PIKABOARD_API/tasks/123"
FieldValuesstatusinbox, up_next, in_progress, testing, in_review, done, rejectedprioritylow, medium, high, urgent
Use the helper to map each agent to a board automatically: cd pikaboard MY_BOARD_ID="$( ./skills/pikaboard/scripts/setup-agent-board.sh | sed -n 's/^MY_BOARD_ID=//p' | tail -n1 )" export MY_BOARD_ID What it does: Reads PIKABOARD_API, PIKABOARD_TOKEN, AGENT_NAME Finds board by BOARD_NAME (default: AGENT_NAME) Creates board if missing Prints MY_BOARD_ID=<id> Verifies GET /api/tasks?board_id=<id>&status=up_next Optional: export BOARD_NAME="Bulbi" export BOARD_ENV_FILE="$HOME/.openclaw/agents/bulbi/.pikaboard.env" ./skills/pikaboard/scripts/setup-agent-board.sh
Each agent can have their own board. Use board_id parameter: curl "$PIKABOARD_API/tasks?board_id=6" -H "Authorization: Bearer $PIKABOARD_TOKEN" Board assignments: Board 1: Pika (main) Board 2: Tortoise (personal) Board 3: Sala (work) Board 4: Evoli (VirtualPyTest) Board 5: Psykokwak (EZPlanning) Board 6: Bulbi (PikaBoard) Board 7: Mew (Ideas)
Run after setup: # 1) API reachable curl -s http://localhost:3001/health # 2) Auth works curl -s -H "Authorization: Bearer $PIKABOARD_TOKEN" "$PIKABOARD_API/boards" # 3) Board mapping works echo "$MY_BOARD_ID" # 4) Agent can read own queue curl -s -H "Authorization: Bearer $PIKABOARD_TOKEN" \ "$PIKABOARD_API/tasks?board_id=$MY_BOARD_ID&status=up_next"
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.