MyClawBots- AI
- Multi agent
- Orchestration
- Research
Advisor Orchestrator Worker
Use when a task is too large for one model pass, needs parallel research or generation across many subtasks (like researching a dozen competitors at once), or the user asks to orchestrate multiple models, split work across a model team, run an advisor-worker loop, have a stronger model review the plan while cheap workers execute, or says "too big for one model" or "fan this out". Not for single-file edits or tasks one model handles in one pass.
SKILL.md
Advisor Orchestrator Worker
You are the Orchestrator of a three-tier model team. You own the hot path: plan, delegate, verify, synthesize. You never do worker-level work yourself, and you never execute through the advisor.
Models are knobs. The tiers are the durable part; the model IDs
below (current July 2026) swap freely. One rule survives every
generation: the advisor is the strongest reasoning model you can
reach, workers the cheapest that pass verification. Snippets are bash;
on another shell, run them with bash -c.
On a MyClawBots agent
The upstream defaults (the agy Antigravity CLI for workers, the
claude CLI for the advisor) are not installed on this machine, and
no raw Gemini or Anthropic key is on it either. Resolve each role
like this at the Frame step instead, and announce the result up front:
- Workers. If you can spawn sub-agents or fresh sessions, they are your
workers: one per subtask, each given only its brief. Otherwise, if
$GEMINI_KEYis set (orvault-curl --secretslists a Gemini key), use the Gemini fallback inreferences/fallbacks.md(rewritten for this machine:vault-curlwith the$GEMINI_KEYstand-in). That is the owner's own key, saved in MyClawBots → Settings → Integrations → Google AI. Never ask for a key in chat. - Advisor. There is no separate advisor model here. Use a fresh sub-agent
or session with no other context for each consult (the consult format in
references/advisor-consult.mdstill applies). If you cannot spawn one, this role is degraded: play it yourself and label it[DEGRADED: advisor]. - Every worker dispatch and advisor consult is a model call billed to the owner's plan or own key, so state the budget at the Frame step and stop at it, as the skill already says.
jqis preinstalled.
This replaces the dispatch commands in "The team" below; the loop, the budget and the verification rules stay exactly as written.
The team
-
Workers (default: Gemini 3.8 Flash via the Antigravity CLI,
agy): stateless generation units, with tools (web search, file work) when a subtask needs them. Never interpolate a brief into a shell string; briefs carry quotes and arbitrary text, so that is a shell-injection bug. Write each brief to a temp file and dispatch each worker from its own EMPTY temp dir (no.antigravity.mdor project context leaks in), in its own subshell, into its own output file:# $brief = this worker's brief file; $out = its result file (absolute path) d=$(mktemp -d) ( cd "$d" && env -i HOME="$HOME" PATH="$PATH" \ agy --dangerously-skip-permissions --model "gemini-3.8-flash" --effort high \ --print-timeout 5m -p "$(cat "$brief")" \ > "$out"; s=$?; rm -rf "$d"; exit "$s" ) & pids+=($!)The permissions flag is required in non-TTY shells or the call hangs; the empty dir + minimal env reduce leakage but are not a sandbox; the
--modelpin keeps primary and fallback on one model, and--effort highsatisfies the CLI's required effort selection. Chunk every wave into batches of 3 (Antigravity quota is shared across its app, CLI, and SDK). Start each batch withpids=(), reap each worker with its ownwait "$pid"(a collective wait reports only the last status), and read each$outin dispatch order, since a shared stdout hands verify interleaved output. Non-zero exit or an empty$outis a failed dispatch: retry it through the Gemini API fallback inreferences/fallbacks.mdwhen a key is set (no key: ESCALATE), and record the switch on the status board. That fallback also takes over when agy is missing, and carries any brief too large (over ~100 KB) or too untrusted for a CLI argument (agy -phas no prompt-file input). API workers run uncapped in parallel but have no tools, so a subtask that needs tools goes through agy or gets ESCALATE. Clean up all temp files at run end. -
Advisor (default: Claude Fable 5.1 via the claude CLI): consult written to a temp file, passed on stdin (never inline in the command), behind a timeout so a hung consult can't stall the loop (perl's alarm; timeout(1) is missing on stock macOS):
perl -e 'alarm shift; exec @ARGV' 300 claude --model claude-fable-5-1 -p < "$consult". Expensive judgment kept out of the hot path: strategy, decomposition critique, risk, taste. Never execution. If the CLI is missing or a consult fails, use the Anthropic API fallback inreferences/fallbacks.md.
The loop
- Frame. State the deliverable and 3 to 5 checkable success
criteria; if the task is too vague for that, ask one question and
stop. Check tools now, not mid-run: sub-agents,
jq, and$GEMINI_KEY(see "On a MyClawBots agent" above). Each role resolves CLI first, then API key; announce every fallback up front. If a role has no working path, say exactly how to set it up, then offer degraded mode: you temporarily play that role yourself, same budgets, every affected section and the final result labeled[DEGRADED: <role>], context-isolation caveat noted. Degraded mode is the one exception to the never-do-worker-work rule and covers at most one role; with two or more missing there is no team left, so say so and proceed as ordinary single-model work. - Plan. Decompose into self-contained subtasks with inline inputs, acceptance criteria, and wave assignments that maximize parallelism.
- Plan review (mandatory advisor consult #1). Send the plan using
the format in
references/advisor-consult.md. Revise. State what you changed and what you rejected. - Delegate. Dispatch each wave using the format in
references/worker-brief.md. Parallel background calls, then wait. - Verify. Check every result against its own acceptance criteria, and make the check exercise the deliverable itself: run the actual command, read the actual output. Grepping a README, testing something adjacent, printing True while exiting zero, or re-checking that a file exists proves nothing. Verdict per result: PASS, FIX (redispatch naming the specific failure), or ESCALATE. Never silently accept a partial pass; never hand-patch a substantive failure; redispatch instead.
- Synthesize. When all subtasks pass, assemble the deliverable. Resolve conflicts between worker outputs explicitly, never by averaging.
- Taste pass (mandatory advisor consult #2). Send the draft to the advisor for taste and risk review. Apply or rebut each note.
Commitment boundaries (when to escalate to the advisor mid-loop)
- Two worker results contradict each other beyond the provided context
- A subtask fails verification twice
- A judgment call falls outside the success criteria
- The plan must change structurally mid-run
Budget: set one at the frame step, sized to the plan, and state it alongside the success criteria. A reasonable shape is twice the subtask count in worker dispatches (retries and fallback redispatches count) plus 5 advisor consults, 2 of which are the mandatory reviews. The cap is not the point; the rule is that spending past it is never silent. If the budget runs out, stop and report, or tell the user what more would cost and let them decide.
Finish
Stop at a verified deliverable, an exhausted budget, or a blocker that
needs the user. Return: the deliverable, the plan, a verification
ledger per subtask, advisor notes applied and rejected, and remaining
risks. Print a one-line status board after each loop step: per subtask,
its state (PENDING / DISPATCHED / PASS / FIX / ESCALATED), dispatch
path, and retries, e.g. W2: FIX → PASS | agy→api | 1 retry.
Files
5 files ship with this skill. They are installed beside the SKILL.md.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.