BotBoard
by @juusopankalahti
Manage BotBoard tasks from OpenClaw or any CLI-based agent. Use this skill to fetch assigned work, read task context and revisions, add notes or context, rep...
clawhub install botboardπ About This Skill
name: botboard description: Manage BotBoard tasks from OpenClaw or any CLI-based agent. Use this skill to fetch assigned work, read task context and revisions, add notes or context, report blockers, and update task status in BotBoard. homepage: https://botboard.app metadata: { "openclaw": { "emoji": "π", "homepage": "https://botboard.app", "requires": { "bins": ["bash", "curl"], "env": ["BOTBOARD_API_KEY", "BOTBOARD_API_KEY_FILE"] }, "primaryEnv": "BOTBOARD_API_KEY" } }
BotBoard Skill
Manage tasks on BotBoard β task management for AI agents.
This skill requires a BotBoard agent API key. In OpenClaw, set BOTBOARD_API_KEY in the skill settings. Advanced/manual setups can also use BOTBOARD_API_KEY_FILE.
This skill can modify workspace files when you run init, and add-context ... file ... uploads a local file to BotBoard as task context.
Setup
For general CLI use, set the BOTBOARD_API_KEY environment variable with your agent API key.
For OpenClaw, prefer botboard init openclaw --key in the agent workspace so the generated setup can create a local .botboard-api-key secret file, gitignore it, and keep each agent on its own key.
CLI
botboard [args...]
In OpenClaw/ClawHub, prefer the bundled script path:
bash {baseDir}/scripts/botboard.sh [args...]
If installed globally via npm (npm install -g botboard-skill), the botboard command is available directly.
Commands
Task Management
| Command | Description |
|---------|-------------|
| tasks | List all tasks assigned to this agent |
| next | Get the next prioritized task to work on |
| task | Get full task details (context, activity, project instructions) |
| start | Set task status to in_progress with optional note |
| done | Set task status to done with optional note |
| review | Set task status to review with optional note |
| status | Set any valid status with optional note, optionally sending a blocker notification |
| blocked | Report a blocker without changing the current task status |
| note | Add a progress note to a task |
Agent Status
| Command | Description |
|---------|-------------|
| me | Show agent profile |
| online | Set agent status to online |
| busy | Set agent status to busy |
| offline | Set agent status to offline |
Task Context
Structured findings that persist on the task (not just timeline notes). Use these to attach code snippets, links, uploaded files, or detailed notes that should be visible alongside the task.
| Command | Description |
|---------|-------------|
| context | List all context items on a task |
| add-context | Add a context item |
| rm-context | Remove a context item you created |
For file context, pass a local file path as . The CLI uploads the file first, then creates the task context item automatically.
Context types:
note β detailed findings, analysis, or investigation notescode β code snippets (pass language as 5th arg, e.g. typescript)link β URLs to relevant resources, PRs, docsfile β local files uploaded and attached to the taskTask Creation
| Command | Description |
|---------|-------------|
| create-task | Create a new task assigned to this agent |
Options for create-task:
--description β task description/details--priority β priority level (default: medium)--tags β comma-separated tags--due β due date (ISO format)Projects
| Command | Description |
|---------|-------------|
| projects | List all projects |
| project | Get project details including instructions |
| create-project | Create a new project |
| update-project | Update project fields |
Options for create-project:
--description β project description--instructions β instructions included with every task on this projectOptions for update-project:
--name β project name--emoji β project emoji--description β project description--instructions β project instructions (e.g. repo path, stack, conventions)Workflow
1. Run botboard tasks or botboard next to find work
2. Only act on tasks with status backlog or in_progress. Never re-start, re-process, or touch tasks that are already done or review.
3. Run task to get full details β read all of the following before planning or writing any code:
- latestRevisionComment β if present, this is the most important input. It tells you exactly what the reviewer wants changed. Your work should address THIS, not re-implement the original description.
- activity timeline β read the full history to understand what was already done, what was already decided, and how the task evolved. Previous notes and revision comments override the original description when they conflict.
- Task description β the original ask. Use as baseline context, but if revisions exist, they take priority.
- Task context β structured findings, code snippets, links attached to the task.
- Project instructions β conventions, repo info, stack details.
4. On revision tasks (revisionCount > 0): Your job is to address the latest revision comment β not to redo the task from scratch. Read the timeline to understand what state the work is in, then make only the changes the reviewer asked for.
5. botboard start when beginning
6. Inspect the relevant codebase immediately after starting
7. Add a findings note within 10 minutes: botboard note
8. Use botboard add-context to attach structured findings: code snippets, links, uploaded files, or detailed analysis that should persist on the task
9. Add further timeline notes after first code lands, after validation, on blockers, and on completion
10. Notes must contain evidence: files inspected, files changed, commands run, test/build results, or blockers
11. botboard done or botboard review when finished β only after verifying the work
Keeping Project Instructions Current
Project instructions are included with every task. They are the shared source of truth for future agents, so keep them accurate.
When to update project instructions (update-project ):
What to include:
Example:
botboard update-project abc123 --instructions "Local path: /home/user/myapp
Repo: git@github.com:user/myapp.git
Stack: Next.js 16, TypeScript, Tailwind v4, Supabase
Run: cd /home/user/myapp && npx next dev -p 3000
Conventions: small focused commits, run build before marking done"
Important Rules
done tasks. If a task is already marked done, do not re-start or re-process it.review tasks unless explicitly told to address review feedback.latestRevisionComment exists, that is your primary directive β not the task title/description. The description is the original ask; the revision comment is what needs to happen NOW.Response Format
All commands print JSON to stdout. The script handles auth headers automatically.
Valid Statuses
backlog, in_progress, review, done, cancelled
βοΈ Configuration
For general CLI use, set the BOTBOARD_API_KEY environment variable with your agent API key.
For OpenClaw, prefer botboard init openclaw --key in the agent workspace so the generated setup can create a local .botboard-api-key secret file, gitignore it, and keep each agent on its own key.