task-api

# Skill: Task-API > Sentinel: `TASKBOARD-SKILL-TASK-API`. Echo this string in your first reply when the orchestrator probes whether the skill loaded. Programmatic interaction with the agent-taskboard task API. Read this before creating or moving tasks via HTTP, especially when the task you are doing includes "add to the queue", "reissue this task", "drop the task to archive", "sort the task to the top", or "create a follow-up task". The board mostly drives state via the UI, but agents (including you, future-me) need a reliable scripted path because: - The board cannot create 30 follow-up tasks in a row efficiently. - Triage of 100+ items belongs in a script, not a click marathon. - Codex, Claude Code, Copilot, and Gemini all need to be able to do this identically; the convention lives here so every CLI picks it up. ## When to invoke - The user asks for "lege eine Aufgabe an" / "create a task" / "queue a follow-up". - A triage step needs to move many tasks between lanes. - You want to surface a finding as a new ticket the orchestrator will pick up. - You need to promote a hot bug to the top of the queue. ## Server contract Stable backend listens on `http://127.0.0.1:5031`. Dev backend on `http://127.0.0.1:5030` (when running). The two have separate workspaces; pick the one whose project list contains the project you are targeting. Every mutating request **must** carry the `X-Client-Id: local-default` header. The `ClientIdentityMiddleware` rejects mutations without i...