Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

multitask-orchestrator

Étoiles2

Forks1

Mis à jour6 avril 2026 à 12:07

Split multi-lane requests into deterministic parallel workstreams and merge them with explicit evidence checks. Use when a request has 2+ independent objectives that can run concurrently.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

grtninja

grtninja/skill-arbiter

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

3 fichiers

SKILL.md

readonly

name	multitask-orchestrator
description	Split multi-lane requests into deterministic parallel workstreams and merge them with explicit evidence checks. Use when a request has 2+ independent objectives that can run concurrently.

Multitask Orchestrator

Use this skill when one request contains multiple independent lanes that should run in parallel.

Trigger Conditions

Use multitask-orchestrator when all are true:

At least two lanes can proceed without blocking each other.
Each lane has a clear success artifact or pass/fail signal.
The final response must merge outcomes from all lanes.

Do not use this skill for single-lane work or tightly coupled sequential changes.

Workflow

Define lanes with stable IDs (lane-a, lane-b, ...), owners, and expected outputs.
Assign each lane a minimal chain (skill-hub routed) and explicit guardrails.
Run lanes in parallel.
Capture per-lane evidence (artifacts, checks, unresolved risks).
Merge lanes only after all required gates pass.
If any lane blocks, route that lane through request-loopback-resume and continue non-blocked lanes.

Lane Contract

Each lane must provide:

objective: one sentence scope
inputs: files/repos/skills used
checks: commands or validation gates
artifacts: JSON/log/doc paths
status: pass, fail, or blocked
next_action: deterministic follow-up

Merge Rules

Merge only pass lanes.
blocked lanes require loopback state before completion.
fail lanes must include root cause and remediation lane.
Final response includes:
- lane summary table
- unresolved risks
- exact artifact references

Guardrails

Keep lane scope minimal; avoid cross-lane file overlap when possible.
Prefer deterministic scripts/evidence over free-form narrative.
Healthy local OpenClaw-compatible subagents are preferred when a lane needs bounded sidecar analysis.
If cloud sidecars are required, keep them lower-reasoning and low-cost.
Do not suppress failing lane results to unblock completion.

References

references/lane-contract.md

Plus depuis ce dépôt

même dépôt

skill-arbiter

grtninja/skill-arbiter

Run the local NullClaw host security app for skill governance, curated-source discovery, guarded threat suppression, and self-governance on Windows hosts.

2026-05-152

code-gap-sweeping

grtninja/skill-arbiter

Sweep one or more local repositories for implementation gaps and produce deterministic, evidence-backed remediation lanes. Use when you need cross-repo detection of missing tests, docs lockstep drift, risky TODO/FIXME additions, and release-hygiene misses.

2026-05-152

safe-mass-index-core

grtninja/skill-arbiter

Build and query bounded metadata-only repository indexes without rg process churn. Use when working in very large repos and you need deterministic file discovery by path, extension, language, scope, or freshness.

2026-05-152

skills-cross-repo-radar

grtninja/skill-arbiter

Detect recent cross-repo work and produce deterministic JSON evidence for skill curation and routing decisions. Use when workflows span multiple repos and you need a bounded view of recent commits, touched files, and policy/contract-sensitive changes.

2026-05-152

repo-b-hardware-first

grtninja/skill-arbiter

Enforce hardware-first diagnosis and fixes in <PRIVATE_REPO_B>. Use for runtime probe, telemetry, inference, and integration failures where strict real-hardware behavior, no new stubs, deterministic diagnostics, and no unrequested driver/runtime mutation are required.

2026-04-212

white-hat

grtninja/skill-arbiter

Run a defender-first security sweep on code, configs, prompts, model/tooling surfaces, or third-party contribution lanes. Use when a request involves safe bug, leak, zero-day-class, exploit, or hack hunting for protection, when contributing to outside repositories and you want a focused security pass, or when touching auth, secrets, permissions, network exposure, prompt/tool boundaries, data flow, or update/build surfaces. This skill is defensive only and must never be used for weaponization or unauthorized access.

2026-04-212

name	multitask-orchestrator
description	Split multi-lane requests into deterministic parallel workstreams and merge them with explicit evidence checks. Use when a request has 2+ independent objectives that can run concurrently.

Multitask Orchestrator

Use this skill when one request contains multiple independent lanes that should run in parallel.

Trigger Conditions

Use multitask-orchestrator when all are true:

At least two lanes can proceed without blocking each other.
Each lane has a clear success artifact or pass/fail signal.
The final response must merge outcomes from all lanes.

Do not use this skill for single-lane work or tightly coupled sequential changes.

Workflow

Define lanes with stable IDs (lane-a, lane-b, ...), owners, and expected outputs.
Assign each lane a minimal chain (skill-hub routed) and explicit guardrails.
Run lanes in parallel.
Capture per-lane evidence (artifacts, checks, unresolved risks).
Merge lanes only after all required gates pass.
If any lane blocks, route that lane through request-loopback-resume and continue non-blocked lanes.

Lane Contract

Each lane must provide:

objective: one sentence scope
inputs: files/repos/skills used
checks: commands or validation gates
artifacts: JSON/log/doc paths
status: pass, fail, or blocked
next_action: deterministic follow-up

Merge Rules

Merge only pass lanes.
blocked lanes require loopback state before completion.
fail lanes must include root cause and remediation lane.
Final response includes:
- lane summary table
- unresolved risks
- exact artifact references

Guardrails

Keep lane scope minimal; avoid cross-lane file overlap when possible.
Prefer deterministic scripts/evidence over free-form narrative.
Healthy local OpenClaw-compatible subagents are preferred when a lane needs bounded sidecar analysis.
If cloud sidecars are required, keep them lower-reasoning and low-cost.
Do not suppress failing lane results to unblock completion.

References

references/lane-contract.md