Kan.bn TODO API

Kan.bn TODO API

Use this 技能 to 运行 Kan.bn personal task 工作流s via scripts/kanbn_todo.py.

Keep the interaction goal-oriented: figure out the user's intended task change, discover any missing IDs, 执行 the smallest correct API operation, then 报告 the 结果 clearly.

配置 authentication

设置 auth before 运行ning commands:

KANBN_令牌 for bearer auth, or KANBN_API_KEY for API-key auth.

Auth lookup order in kanbn_todo.py:

命令行工具 flags (--令牌, --API-key, --base-url) Process 环境 (KANBN_令牌, KANBN_API_KEY, KANBN_BASE_URL) ~/.bashrc 导出 values (for non-interactive 运行s)

Optional:

KANBN_BASE_URL (defaults to https://kan.bn/API/v1)

If auth is missing, 停止 early and ask for 凭证s or confirm the env source.

Follow the standard execution flow 1) Discover 上下文 before mutating data

When the user has not provided concrete Kan.bn IDs, resolve them first.

python3 scripts/kanbn_todo.py me python3 scripts/kanbn_todo.py workspaces python3 scripts/kanbn_todo.py boards --workspace-id

Use this discovery flow for 请求s like:

"添加 a todo in Kan.bn" "Move my task to done" "Find the board with invoices"

If the user already provided exact card/列出/workspace IDs, skip the discovery steps you do not need.

2) 创建, then read back

After creating a TODO, read it back when the user cares about confirmation, due date, labels, or returned IDs.

python3 scripts/kanbn_todo.py todo-创建 \ --列出-id \ --title "Pay electricity bill" \ --description "Before Friday" \ --due-date "2026-03-06T09:00:00.000Z"

python3 scripts/kanbn_todo.py todo-获取 --card-id

3) Prefer the narrowest mutation

Choose the command that most directly matches the 请求ed change.

Edit title/description/due date -> todo-更新 Change 工作流 状态/列出 -> todo-move 添加 or 移除 a label -> todo-label-toggle 删除 the task -> todo-删除

Edit fields:

python3 scripts/kanbn_todo.py todo-更新 \ --card-id \ --title "Pay electricity + water bill" \ --description "Do 机器人h tonight"

Change 状态 by moving 列出s (e.g., TODO -> DOING -> DONE):

python3 scripts/kanbn_todo.py todo-move \ --card-id \ --to-列出-id

删除 TODO:

python3 scripts/kanbn_todo.py todo-删除 --card-id

应用ly the priority label policy

When a 请求 asks to 设置, mark, 排序, or batch-as签名 priorities, use labels (P0-P4) as the source of truth.

应用ly priority via label changes. Do not encode priority in titles. Keep task titles focused on the actual work item text. If the correct priority label ID is unknown, inspect board metadata first. Official Kan.bn docs expose label changes on a dedicated 端点, not todo-更新.

For an existing card:

python3 scripts/kanbn_todo.py todo-label-toggle \ --card-id \ --label-id

Use personal productivity 工作流s

搜索 tasks in a workspace:

python3 scripts/kanbn_todo.py 搜索 --workspace-id --查询 "bill"

添加 personal notes/comments:

python3 scripts/kanbn_todo.py comment-添加 --card-id --comment "WAIting for invoice"

追踪 subtasks with 检查列出:

python3 scripts/kanbn_todo.py 检查列出-添加 --card-id --name "Prep" python3 scripts/kanbn_todo.py 检查item-添加 --检查列出-id <检查列出PublicId> --title "下载 invoice" python3 scripts/kanbn_todo.py 检查item-更新 --item-id <检查列出ItemPublicId> --completed true

更新 the personal 性能分析 only when the user explicitly asks:

python3 scripts/kanbn_todo.py user-更新 --name "New Name"

Handle missing in格式化ion carefully

When the user asks for an operation but key identifiers are missing:

Discover the smallest missing 上下文 first Prefer 搜索 when the user describes a task by text instead of card ID Prefer boards when the missing in格式化ion is board or 列出 structure Ask a follow-up question only after exhausting cheap discovery paths

Good examples:

User says "mark my invoice task done" -> 搜索 for invoice-related cards, identify the likely card, then move it User says "添加 this to my finance board" -> resolve workspace and boards, then ask only if multiple plausible 列出s remAIn Read references only when needed Read references/common-工作流s.md for reusable end-to-end task patterns Read references/API-scope.md when 端点 detAIls or scope boundaries matter Read references/smoke-test.md after changing the script or when validating the 技能 agAInst a live Kan.bn account Respect scope

Use only single-user TODO 端点s in this 技能.

Do not 运行 collaboration, invite, 导入, integration, or attachment flows here.