orchestrator
PassAudited by ClawScan on May 4, 2026.
Overview
This is an instruction-only project orchestration skill with no install code or credentials, but users should review its multi-agent delegation and checkpoint behavior before relying on it.
This skill appears coherent and benign as an instruction-only orchestrator. Before installing, understand that it may propose multiple specialist agents, fallback agents, parallel sessions, and checkpointing. Approve plans before downstream agents act, review combined outputs carefully, and avoid putting secrets into shared task context or checkpoints.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A task may be handed to different specialist agents than the user initially expected.
The skill can route work through fallback agents, which is core to an orchestrator but means task authority may broaden if a primary agent fails.
Primary Agent (95%+) ↓ if unavailable or fails Secondary Agent (70%+) ↓ if unavailable or fails Generalist Fallback (/fullstack-engineer) ↓ if still fails Multi-Agent Coordinator (/multi-agent-coordinator)
Review the proposed agent plan and fallback chain before allowing downstream agents to make changes.
Outputs from one agent session could influence another phase of work, including mistakes or unsafe assumptions.
The skill encourages parallel work across multiple agent sessions and later result aggregation. This is consistent with its purpose, but cross-session context and outputs should be reviewed before being combined.
For User: Open multiple Claude Code sessions to run these in parallel: Session 1: /backend-architect Design the API; Session 2: /ux-designer Create user flows; Session 3: /data-engineer Plan data pipeline
Treat each agent’s output as untrusted until reviewed, and avoid sharing secrets or unnecessary private project data across parallel sessions.
Stale or sensitive checkpoint content could be reused later if the agent stores or summarizes project state.
Checkpointing can create persistent summaries or saved state. The behavior is disclosed and purpose-aligned, but the visible artifacts do not specify storage location, retention, or reuse boundaries.
Automatic Checkpoints (V4) Auto-save progress at key milestones for disaster recovery.
Confirm where checkpoints are saved, avoid including secrets in checkpoints, and periodically review or clear saved project context.
Users may overestimate the reliability or safety of the orchestration plans.
The description uses strong authority and quality claims that are not substantiated by the provided artifacts.
powered by proven agentic design patterns from 1K+ real-world AI projects, enhanced with industry-leading multi-agent coordination
Treat generated plans as recommendations, not verified guarantees, and require explicit review before implementation.