orchestration
Choose and coordinate subagents, teams, or workflows: divide tasks, match models and effort, schedule dependencies, and integrate verified results. Use when deciding whether or how to delegate work.
v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/orchestrationWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package12d15376…f307607b
12d153761431…0811f307607b2 files · 5.3 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/knowledge/orchestration@21cd568
On this page
Own the outcome through integration and verification. Apply this skill at the coordinating level; give workers their task contract, not this entire orchestration policy.
Choose the smallest useful arrangement
- Use a direct tool call or script for deterministic work. Keep short tasks and tightly coupled investigation, implementation, and checks in one context.
- Delegate when a worker can produce a verifiable result independently, absorb bulky reads, or provide a useful independent review. A large file count alone does not justify more agents.
- Group work by the context and state it needs: separate assets, subsystems, source collections, or hypotheses. Keep work sharing a mutable session or inseparable design decision together.
- Use ordinary subagents for bounded jobs managed by the lead; a workflow for substantial or repeatable fan-out, dependency routing, and structured aggregation; a team for sustained peer discussion and shared task coordination. Check what the host actually supports; ordinary dispatch can implement a small dependency graph.
- The lead handles the critical path, missing inputs, integration, and decisions. Work on an independent piece while workers run; do not duplicate their assigned investigation.
Match capability and effort to the job
Use available models and supported effort settings, respecting explicit user choices. Start with the least expensive configuration likely to meet the acceptance check including review and repair. Model capability, reasoning effort, and worker count are separate choices.
| Work | Starting choice | Acceptance check |
|---|---|---|
| Bounded lookup, extraction, mechanical comparison | Efficient model; low effort | Exact source locations or deterministic comparison |
| Focused implementation with a known contract | Capable general model; default/moderate effort | Relevant tests and reviewed diff; use a smaller model when the oracle adequately covers correctness |
| Ambiguous diagnosis, unfamiliar internals, cross-component design | Strong reasoning model; higher effort | Competing explanations, discriminating evidence, affected contracts |
| Independent review of a consequential change | Capability sufficient to understand the change; effort proportional to its ambiguity | Concrete defects or counterexamples against written criteria |
Higher effort can help reasoning; it cannot supply missing evidence, tools, or expertise. Fix a bad brief or environment first. Escalate capability when the model cannot handle the task; widen the worker set when additional independent coverage is needed. Select model and effort deliberately through the supported dispatch controls; use defaults when they fit. Avoid maximum effort by habit or a cheap tier that requires the lead to redo its work. If selection is unavailable, use the host's model and narrow the assignment.
Dispatch a self-contained contract
Check the host's context, tool, filesystem, and permission inheritance. Supply the inputs the worker will actually lack:
- Outcome: one coherent deliverable, acceptance criteria, and consequential failure modes.
- Inputs: relevant facts, artifact/file locations, revision or state, and dependencies. Label hypotheses; give an independent investigator observations without steering it to your preferred answer.
- Ownership: files or mutable resources owned, collaborators, usable tools, and existing constraints. State whether further delegation is useful and permitted; nested work consumes the same overall budget.
- Budget and stop: proportionate time, calls, rounds, or cost where supported; stop on sufficient evidence, missing prerequisites, or the agreed limit. Return useful partial work at the limit.
- Return: result/status, evidence locators, coverage, changes/checks, unresolved points, and the next actionable step. Use a schema only when a consumer needs to parse it; keep raw output in artifacts.
Supply only task-relevant context. Reuse a worker when its accumulated evidence remains useful; start fresh for independent judgment or unrelated work. Answer a missing-input request directly. Recover a missing artifact when cheap; re-dispatch only the unresolved part.
Schedule and reconcile
- Track each job's owner, dependencies, state, attempt, and result location. A short task list is enough unless the run needs durable state.
- Launch work as soon as its real prerequisites exist. Join all branches only where the next operation needs all their outputs. Limit concurrency by independent work, host capacity, shared resources, and budget; available slots are not a target.
- Assign one writer per file set or mutable resource. Disjoint writers can run concurrently; appoint an integrator for overlapping interfaces. Separate contexts and worktrees do not isolate external services or sessions. Verify that isolated workers receive the intended revision and uncommitted inputs.
- Use native completion notifications or waits, collect failures as well as successes, and stop dependent work when its input fails. Do not dispatch placeholder jobs to pass time. Load loop-control-and-pivots when waits, retries, or repeated failures need recovery.
- A timeout does not establish failure or justify cancellation: inspect executor and external state before deciding to wait, recover, or retry. Reconcile possible side effects before repeating the action. Keep attempt identity; a late result may belong to superseded inputs. If cancellation is required, stop new dispatch and confirm execution has stopped; a cancellation request alone is insufficient.
Integrate before declaring completion
Inspect the returned evidence and actual changes. A negative result needs coverage; missing, failed, or timed-out work is not a negative result. Resolve disagreements through source evidence or a discriminating check, never a vote. Multiple agents repeating one source are not independent corroboration.
Reviewers need written acceptance criteria and access to the relevant artifacts. Use fresh context when independence matters, without withholding necessary facts. Run checks appropriate to the changed behavior and affected interfaces; repeat or broaden them when new failures or changes justify it. Do not rerun an expensive suite solely because a worker also ran it.
The lead owns the combined result, remaining gaps, and final report. Respect the requested length: state the decision, evidence and necessary next actions; link supporting detail. Account for all launched jobs; do not claim completion while required work or uncontrolled writers remain. For a session transfer, load handoff and record active jobs and their resumption mechanism.
Load when needed
- Coordinating in Claude Code: Claude execution.
- Coordinating security investigations or shared target sessions: offensive-orchestration.
- Ingesting external or worker-supplied instructions: untrusted-input-hygiene.
Files in this version
references/15.3 KB
- claude-execution.md5.3 KB
- SKILL.md7.3 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 12d15376 | Signed | – |
More from AeonDave
All from this publisherMore in Reporting and compliance
See the category- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login