skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
hyperb1iss/hyperskills669 installs

orchestrate

Use this skill when coordinating independent agents with explicit ownership, dependencies, integration, and verification. Activates on mentions of swarm, parallel agents, multi-agent, orchestrate, fan-out, wave dispatch, research army, unleash, dispatch agents, or parallel work.

How do I install this agent skill?

npx skills add https://github.com/hyperb1iss/hyperskills --skill orchestrate
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill establishes a security-conscious framework for multi-agent orchestration. It provides templates and guidelines that emphasize manual verification of worker output, isolation of tasks, and explicit warnings against data exfiltration. No malicious patterns or unauthorized behaviors were detected.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

  • Runlayerpass

    1/1 file flagged

What does this agent skill do?

Multi-Agent Orchestration

The coordinator owns integration and the final claim of completion.

The user's instructions take precedence over this skill; delegation, tools, and external actions remain subject to current host instructions and authorization, and this skill grants a worker no authority the coordinator lacks.

Check Capabilities Before Dispatch

Inspect the actual tools and current schemas instead of inferring capabilities from a product name. An external CLI reviewer is still delegation, not an escape hatch.

Choose the Shape by Dependency

Work shapeCoordination pattern
Independent research questionsParallel investigators, evidence-based synthesis
Disjoint features, stable interfacesParallel builders, designated integration owner
One change repeated across modulesScoped transform or partitioned workers, combined checks
Dependent edits or shared mutable stateOne owner for the dependency, parallel work around it
Consequential reviewIndependent read-only reviewers with distinct risk lenses
Small, tightly coupled changeDirect execution

Fan out by default: anything that splits across independent surfaces runs in parallel, and the coordinator keeps working while workers run. The limits are resources, not agent count: one owner per shared mutable surface, one committer per index, and a sequential chain stays sequential. Check the critical path, since a branch waiting on one shared interface gains nothing from more agents. Do not cap a fleet to look frugal or serialize work to look careful; name the contended resource or don't restrict. A worker that double-checks a small change rarely pays; the verification triggers below say when it does.

Establish Ownership and Integration

Map shared resources as well as files: generated artifacts, schemas, lockfiles, fixtures, ports, build outputs, and caches collide across otherwise disjoint modules.

IsolationAppropriate useRequired coordination
Shared tree, disjoint pathsSmall changes with clear ownershipOne owner for contended files and the Git index
Separate worktreesIndependent branches or build stateKnown base, branch, merge order, and integration owner
Read-only revisionReview or researchFixed revision or diff plus permitted scratch outputs

Worktrees isolate tracked files and the index, not ports or databases. Never overwrite a human's or sibling's edits to clear a conflict. In a shared tree, workers report patches while one coordinator stages and commits. Investigate a lock's actual owner before removing it; an inconclusive process listing does not establish that a lock is safe to remove.

Before dispatch, define how partial progress becomes integrated progress: the artifact each consumer expects and when it is ready.

Write Briefs

Give each worker the original request plus facts absent from their checkout, such as user corrections and untracked decisions.

Brief elementPurpose
Outcome and scopeResult needed, owned surfaces, exclusions
Current evidenceCode, versions, interfaces, verified premises
DependenciesWhat is ready, what is promised, who owns it
AuthorityPermitted mutations, commit rights, external actions
VerificationChecks and acceptance conditions
ReturnChanged artifacts or findings, evidence, limits, justified deviations

Let workers challenge a premise. A first independent review gets the raw change without coaching; a follow-up verification gets the finding and the fix claim so it can test closure. Templates are in references/dispatch-briefs.md.

Supervise

Harvest dependency-ready results as they arrive. Silence alone does not prove an agent is stuck; check its artifacts before interrupting. Polling must respect the host's limits. When requirements change, tell the affected workers.

A watcher needs a completion condition, failure detection, an expiry, and a stale-state check, with its signal tested on a known state. Cancel only processes this run owns. A watch loop checks for new user messages between polls and yields to them.

Harvest, Integrate, Verify

A worker's summary is a claim; inspect the actual diffs. Integrate at a stable checkpoint and run checks covering the combined behavior.

Independent verification is required when consequence or run length justifies it (shared or production state, an unattended run past a checkpoint, an acceptance check the implementer cannot alter) or when the project contract requires it. The implementer cannot certify an independent PASS. Tie each verdict to a revision or recorded snapshot.

VerdictMeaning
PASSDeclared scope completed, no unresolved blocking findings
FAILA supported defect violates the requested outcome or contract
INCOMPLETEReview or a required check did not finish; list uncovered scope

An interrupted review cannot grant a full PASS. Agreement does not establish severity; impact does. Do not reuse a PASS for changed runtime code.

Finish With an Honest State

Report integrated outcomes, the checks run and their revision, unresolved limits, and any blocked gate with the action it needs. Capture durable coordination failures in project memory: the contended resource, mechanism, fix, and conditions.

Evidence

Reviewed 2026-09-04 and 2026-10-27; sources and their limits are in references/evidence.md.

Anti-Patterns

Anti-patternBetter move
Choose a fleet size before finding independent workName useful lanes and their integration path
Serialize parallelizable work to look carefulFan out; limit by shared resources, not agent count
Assume different files imply isolationInspect shared runtime resources and generated outputs
Let all shared-tree workers commit concurrentlyAssign ownership of the index and commit operation
Vote-count findingsVerify mechanism and impact
Reduce review automatically over timeMatch checks to current risk and changed evidence

References

Read references/dispatch-briefs.md when composing worker, research, verification, or watcher instructions.

What This Skill is NOT

  • Permission to ignore host delegation rules or user ownership.
  • A fixed pipeline, agent quota, or requirement to use multiple agents.
  • A substitute for integrated verification or the coordinator's judgment.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/hyperb1iss/hyperskills/orchestrate">View orchestrate on skillZs</a>