Kanbanflow Skill

**Quick judgment:** A focused, task-centric KanbanFlow integration that is well-suited as an automation primitive for managing work items across a board. It exposes the key CRUD-like operations on tasks and columns, but remains fairly low-level and ID-driven, so it’s best used by automations and power users rather than end users expecting a rich UX. **What it’s good for:** - Integrating KanbanFlow task management into broader OpenClaw workflows (e.g., create or move tasks based on external events). - Lightweight automation of routine board maintenance: adding tasks to specific columns, moving them as their status changes, and visually categorizing with colors. - Programmatic board inspection via `board`, `columns`, and `tasks` for reporting or decision-making in other skills. **Key risks / limitations:** - **Destructive operations:** `delete` and `move` can lose or displace tasks if used incorrectly and there’s no mention of confirmation, undo, or soft-delete; calling agents should validate task/column IDs and apply strong preconditions. - **Low-level interface:** The command set is basic and ID-based (`columnId`, `taskId`), which can be error-prone if IDs are not resolved carefully; it does not provide higher-level abstractions like searching by name or filtering by status. - **Domain-specific:** Only useful in environments where KanbanFlow is already adopted and properly configured; it does not manage permissions or access control itself. **Recommended scenarios:** - Building automations that keep KanbanFlow in sync with other systems (issue trackers, CI/CD, CRM) by creating and moving tasks. - Implementing agent workflows that periodically review columns, color-code tasks, or clean up old items. - Using it as a backend utility in more user-friendly skills or UIs that handle ID resolution, confirmation prompts, and safety checks on top of this core command set.