Use when the user needs a coding task done - code written, changed, fixed, tested or reviewed - through its follow-ups, and when a coding agent reports its quota or usage limit used up.
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./raven/memory_engine/skills/multi-agent-coding/SKILL.mdCoding work goes to a coding agent on the roster: the one the user named, otherwise one
the ## Delegation section says owns coding, otherwise one whose description says it
writes or edits code. When a Worker Table is bound, subagent takes worker labels
instead: pick the worker whose brief covers the coding work. When none does, tell the user
and ask how to go on rather than writing the code yourself or sending it to an agent
outside the enum.
An instance is one conversation with one agent, named by the instance handle.
subagent, same instance, a new node_id. The
agent keeps its context, so the prompt carries the new request in the user's words.When a task needs what another produced, put that task's output file in its prompt -
{{ <node_id>.output_path }} of its last dispatch - instead of retelling the result. The
file is the agent's report, not the code, so also say where the code is (section 4).
Local sub-agents share this session's working directory, where nothing locks a file, and
giving each agent its own files there does not isolate them: tests run against the other's
half-made edits, and one agent's git stash or checkout wipes the other's work. So when
a coding task will run beside another in the same project - dispatched together, or while
the other is running or unfinished - its prompt tells the agent to make its own worktree,
on a branch you name for the task (fix/login-session-expiry), so the work can be found
even if the agent stops before reporting:
Create a git worktree of your own for this task on a new branch
<branch>, outside the project or in a directory git ignores. Work only there, and end your report with its path and branch. If the project is not a git repository, do not make it one: work in place on only this task's files, and say so.
When a coding agent's result says its usage limit, quota, credits or balance is used up - often with a 402 or 429 status or a reset time, in whatever words or language - send the task to another coding agent right away.
node_id and a new instance. The old instance's context does not carry
over, so the prompt carries what the task needs: the user's requests on it, the worktree's
branch and any path a report gave (the worktree may hold the first agent's unfinished
changes), and the output files of the task's finished dispatches. From then on, the new
instance is the task's instance.replan, putting its work on another coding
agent under a new id. continue would send it back to the agent that ran out, and the
user need not be asked.Raven's own limits refuse every agent alike, so follow the refusal instead of switching
agents: a spawn or graph refused because this session hit its spawn rate limit or its
dispatch rate limit, because delegation is paused, or because the host is shutting down.
EverMind-AI/Raven
dc35a05
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.