Maintain Agent Kanban boards and their linked repositories as an autonomous open-source project maintainer.
SkillScore82Maintained
Automatic
◆Project Management pack
Last verified 9/17/2026
What it changes
Passed 14 of 17 test cases with the skill, and 6 of 17 without it.
Without skill36%
With skill82%
Checks it passed that the model alone missed
Includes parameter --wait-seconds 25.
Sets status field to done in the patch payload.
Executes GET request against agent-kanban/boards.
and 14 more in the full report
11 fixed7 passed either way3 still failing1 broke
Pass-rate lift
+45 pp
Tokens
+30%
Agent turns
0%
Response time
-25%
Model gemini-3.6-flashMeasured 9/17/2026v218 of 22 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
Task 'task-305' has submitted valid benchmark logs meeting all acceptance criteria. Provide the CLI command to approve this task.
What was checked, without and with the skill
Checked
Without skill
With skill
Uses realmroot toolbox patch on endpoint agent-kanban/tasks/task-305.
Missed
Passed
Sets status field to done in the patch payload.
Missed
Passed
case-09 · gemini-3.6-flash · 9/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md136 linessingle file
AK Maintainer
Invocation and scope
Select this skill proactively when coordinating an authorized project through
AK; the user does not need to name it. Typical entry points are Sessions
started by a scheduled task or heartbeat to maintain an existing project or
Board. Stay within the trigger's project objective and existing authorization.
Act as the manager: inspect, prioritize, decompose, assign, monitor, and review.
Use AK Tasks to drive other Agents to perform the work. Do not claim or assign
implementation Tasks to yourself, edit the target repository to implement them,
or take over a worker's corrections. Repository inspection and acceptance
verification are part of management; implementation belongs to the assigned
worker using ak-worker. If no suitable worker is available, record the blocker
instead of doing the work yourself.
Recommended scheduled or heartbeat workflow
Read the trigger's objective and the current Board, Tasks, Notes, dependencies,
and relevant repository state. Determine what needs doing now: missing work,
ready unassigned Tasks, blocked dependencies, or submissions awaiting review.
Use current AK resources as the source of truth across Sessions.
Review pending submissions and resolve actionable coordination issues. Reuse
or update existing Tasks before creating new ones; repeated wakeups must not
duplicate work that is already planned, assigned, or completed. A Task that
has not changed since the previous heartbeat is not by itself a reason to
reassign it or create replacement work.
Turn uncovered work into independently reviewable Tasks with clear goals,
repositories, dependencies, and acceptance checks. Assign execution to other
schedulable Agents through AK. Order overlapping work and let independent
Tasks progress in parallel.
Inspect meaningful progress and review completed submissions. Return required
corrections to the assigned worker with a concrete reason; complete a Task
only when its acceptance evidence is sufficient. Reassess dependent work
after each completion.
Respect the current Session's run budget. Record useful decisions, blockers,
and next actions in the affected Task Notes so the next scheduled or heartbeat
Session can resume from AK state. If nothing is actionable, finish quietly.
Follow the trigger's reporting policy; normally notify only on meaningful